Support » How-To and Troubleshooting » backslash problem is back…

backslash problem is back…

  • ok, ever since I upgraded from 2.1.1 to 2.1.2, the problem of backslashes inserting themselves before apostrophes is back. If we remember, it was an issue with versions 2.0.3 and 2.0.5… I have tried the same plugin, Tuneup, that I used before to correct this issue, but it seems as though it no longer corrects this problem as I am getting new comments with this problem.

    Anyone else getting this now? BTW, I did not do an upgrade, I cleaned up my site with a fresh install. Anyone know how to fix this?

    Thank you in advance…


Viewing 4 replies - 1 through 4 (of 4 total)
  • Is anyone else getting this bug as well?

    I’ve got the same problem. I haven’t found a workaround for it yet either and it’s causing validation errors, which is unacceptable. If anyone finds out how to fix it please let us know. Has this been reported as a bug yet?

    it seems to be random for me. i have no idea what the common factor is for this.

    It’s occurring for me when I output this

    $blogs = "\"#\"";
    wp_list_categories('orderby=name&exclude=2, 4&use_desc_for_title=1&title_li=<a href=' . $blogs . '>blogs</a>');

    I’m using the “pages” and “categories” as the menu system. I also found that if I add another value like ?page_id=18, it adds on the rest of the url before it. I’ve gone through some of the source code, mainly classes.php and post-template.php, to remove other styling and attempt to implement the <a href in the code that’s output for the title, but when I backslash the code there, it too outputs the same garbled garbage. At this point I think I may have to apply another rule to this so it doesn’t look off.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘backslash problem is back…’ is closed to new replies.
Skip to toolbar