magic_quotes_gpc, when on, automatically adds slashes to all GET\/POST\/COOKIE data so that you don\u2019t need to use addslashes() before using GET\/POST\/COOKIE data in MySQL queries, etc. (e.g. with magic_quotes_gpc OR addslashes(), I\u2019m becomes I\\\\\u2019m). Well, magic_quotes_gpc is no convenience and just complicates things!<\/p>\n
Since magic_quotes_gpc can be on or off, you don\u2019t know whether to use addslashes() or not. You don\u2019t want to use addslashes() when magic_quotes_gpc is on because you\u2019ll add too many slashes (e.g. I\u2019m becomes I\\\\\\\\\u2019m), which is bad. Use addslashes() if magic_quotes_gpc is off, and don\u2019t if it\u2019s on (you can find out its setting with get_magic_quotes_gpc()). But you can\u2019t use the same code all the time. One workaround is something such as:<\/p>\n
if (!get_magic_quotes_gpc()) { $txt = addslashes($txt);<\/p>\n
Using magic quotes has always been confusing and in PHP 6 they are apparantly going to remove it.\u00a0 So it is better to program your scripts without using get_magic_quotes_gpc at all.<\/p>\n","protected":false},"excerpt":{"rendered":"
magic_quotes_gpc, when on, automatically adds slashes to all GET\/POST\/COOKIE data so that you don\u2019t need to use addslashes() before using GET\/POST\/COOKIE data in MySQL queries, etc. (e.g. with magic_quotes_gpc OR addslashes(), I\u2019m becomes I\\\\\u2019m). Well, magic_quotes_gpc is no convenience and…<\/span><\/p>\n