Problem with slash’s after upgrade to 1.2

  • I have just upgraded to 1.2 and now all my posts that contain the character ‘ in them have suddenly now got a forward slash in front of them. So things like “I’ve” now look like “I\’ve”. This was not the case on 1.02. It has only started on 1.2. I first assumed it was magic_quotes being turned on but I have switched this off and it’s still doing the slash.
    The main index page does not have any slashes, but the rss feed’s do, and so do the comments.
    I have tried removing the slash (whcih is present in the actual database entry) manually but wordpress just reinserts it when editted under wordpress so I am assuming that wordpress is doing an addslash or something when it shouldn’t.
    Any idea?

Viewing 13 replies - 16 through 28 (of 28 total)

  • [bump]
    i have the same problem.
    how do we use the ‘add_filter’ that was suggested earlier?

    Just put it in my-hacks.php. Or in wp-includes/vars.php, along with the other filters.

    nice.
    add_filter('comment_text', 'stripslashes'); worked like a charm.

    I put that in my pop-up comments and it worked great, thanks Matt!

    Worked perfectly in vars. No slashed anywhere now. Thank you all. ??

    Thanks for this fix ??

    I just had an email that the same problem is happening in the RSS files, too. Will those new wp-includes files handle this problem?
    And this is a serious enough problem to think about adding something to the development blog or front page with how-to grab these files and install for the non-techs.
    Not everyone understands what ‘CVS’ means.

    I downloaded and updates the files mentioned earlier — no difference.
    I realize that any release will have problems, but this one is significant enough that I can’t recommend the 1.2 release to anyone until a fix is made. We can’t have non-coders dropping function calls hither and yon–not without probably creating worse problems.

    I’ve seen this problem reappear in the nightly builds…

    How do you apply the add_filter(‘comment_text’, ‘stripslashes’) fix?

    You could add it to my-hacks.php

    Saw this in content in both wp_posts and wp_comments after upgrade from 1.0 to 1.2, and I wasn’t certain the add_filter() fix was working, and also it seemed better to fix the data than filter the rendering (data in db was definitely altered during the upgrade). After running a script to remove the backslashes from the content cols in each table all is fine… -dchud

    Where’s my-hacks.php? I tried adding the filter to vars.php, but I still have slashes–not in comments (I have no comments), and not on my index page–but on all the other pages (archives). https://patrioticearthling.com/blog/index.php

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘Problem with slash’s after upgrade to 1.2’ is closed to new replies.