Search options (Page 60 of 77)

If you look in one of the discussion threads for that mod, there's a multiple question/answer version of it.

That way is even better. Just mentioned it because many people never mention the new window bit anywhere.

Must admit, I am guilty of opening three links on the forum in new pages/tabs. The gallery, for uploading images for posting, and the two links to the articles/downloads sites. I use the JS method. Must admit, I'm not fond of the opening new windows/tabs concept myself, but trying to constantly explain to people that a right click and open in...... was all that was required ended up getting tedious after a while, so I digressed on those three.

If you are going to open links in new tabs/windows however, I would suggest using the title= part to list that fact in the <a tag/link. At least people will be advised when they hover over the link, that way.

Do I feel such a prat now you've explained it. The penny just never dropped before. Cheers for the explanation.

Apologies for keep asking questions, but SQL not being my strongpoint and such. Would that lookup need doing as such, in that case:

$result = $db->query('SELECT username FROM '.$db->prefix.'users WHERE UPPER(username)=UPPER(\''.$db->escape($username).'\') OR UPPER(username)=UPPER(\''.$db->escape(preg_replace('/[^\w]/', '', $username)).'\') OR LOWER(username)=LOWER(\''.$db->escape($username).'\') OR LOWER(username)=LOWER(\''.$db->escape(preg_replace('/[^\w]/', '', $username)).'\')') or error('Unable to fetch user info', __FILE__, __LINE__, $db->error());

or is there a shorthand method, i.e: UPPER/LOWER for that query?

Thanks ever so much once again,

Matt

That, I could live with, if needs be. I'm just unjustifiably pedantic about silly little things like case. On that note about registering, however, another question, if I may? Would replicating the username check in register.php with LOWER as well as UPPER, (running the query twice, as it were), stop that scenario arising? A double lookup there would, I assume, be negligible due to that section not being accessed too frequently?

Thanks again,

Matt

Nice. At least now you know that any viewable browser specific differences aren't caused by code errors. They're just down to quirks or browser specific requirements/interpretations.

Wouldn't worry about it then. There always tends to be one browser cocks it up. (Usually IE, as a rule).

Run it through the validator and start on the uppermost tag eror listed. You'll often find that top error may be causing several phantom erors below it in the validation list. Work on the top error shown each time, revalidate, and see which errors still exist.

$pun_config['o_base_url']

In viewtopic.php, comment out, (as already told you by CodeXP), the first line starting:

$post_actions[] = '<li class="postreport">

Put // in front of the dollar sign.

Remove this portion of the second occurence:

<li class="postreport"><a href="misc.php?report='.$cur_post['id'].'">'.$lang_topic['Report'].'</a>'.$lang_topic['Link separator'].'</li>

Delete the report post section of html at the bottom of misc.php.

Done.

Nope. I class them as a courtesy. Open Source can never be over promoted, and the fact that I use the software deserves some small token in return, in my opinion. They're only shown on the main forum and index page, btw. They're not at the bottom of all pages.

There are a lot of more precise ways of finding out exactly what a webserver is running, without having to look at icons. Security through obscurity is a complete and utter fallacy. Security is gained through security, and nothing more.