9
Quote from the page included in my last post:
And PHP comes with a handy function to help you deal with this: addslashes(). By passing $post through addslashes, before you INSERT / UPDATE MySQL, the apostrophes are escaped for you.
'Easy!' you think, generating yet more apostrophes that need escaping. But not so fast. PHP provides a configuration option "magic_quotes_gpc", which automatically adds slashes to any submitted HTML form data or cookies (gpc = GET/POST/COOKIE), before it gets passed onto your script.
From the PHP manual:
"Sets the magic_quotes state for GPC (Get/Post/Cookie) operations.
When magic_quotes are on, all ' (single-quote), " (double quote), \ (backslash) and NUL's are escaped with a backslash automatically."
magic_quotes once seemed like a good idea but have turned out to be a menace, because if you take code where someone is using addslashes() and run it on a server where magic_quotes_gpc is on, this is what will be inserted into the database; UnQuote
The general opinion is magic quotes are evil..:)
Some of the modules have the coding "addslashes", which is not good if magic_quotes are turned on in the user server.
The only permanent solution is to turn off magic quotes it appears, this can be done on hosted servers with an .htaccess file with something like this in it
php_flag magic_quotes_gpc off
php_flag magic_quotes_runtime off //(if runtime is on)
The coding would otherwise need some functions to cater for both possibilities (off or on)
The above two lines worked for me, but i had to re do the text in the modules concerned, like soapbox for example
