Quote:
Originally Posted by BirdOPrey5
FYI, the warning message isn't 'bogus' at least not in this case... for various security reasons it's better to always enclose the {param} tags in double quotes rather then single quotes... while I highly doubt anyone will have a problem the following codes will not display the error and is technically a bit safer. (I swapped the single and double quotes):
Also I'm not sure what the purpose of "<!{param}>" is- I don't know what it does and it seems to work fine for me without it. 
|
Thanks very much for the advice and assistance. I've edited in the double quotes where they should have been. The "<!{param}>" was unnecessary and should've been removed after I'd finished testing. That's done now, cheers

.
Quote:
Originally Posted by djbaxter
I meant to come back and comment on this, too. In fact, the errors I was receiving with a couple of other BBCodes were valid errors - some I could fix and some I couldn't.
As Bird of Prey says, don't ignore such errors - they do mean something and may create a vulnerability if ignored.
|
Thanks for that advice. All fixed

.