Upgraded to version 2.31 and get occasional "Â" letters in my posts

Discussion in 'WordPress' started by kiplarson, Dec 28, 2007.

  1. #1
    Upgraded to version 2.31 and get occasional "Â" letters in my posts. Anyone ever seen anything like this?

    I suppose it could be a wordpress plugin but it's annoying me having to go back and fix the ish lol.
     
    kiplarson, Dec 28, 2007 IP
  2. Woody10

    Woody10 Well-Known Member

    Messages:
    170
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    115
    #2
    Not much help but I ended up downgrading because
    of plugin related problems.
     
    Woody10, Dec 29, 2007 IP
  3. sizzler_chetan

    sizzler_chetan Prominent Member

    Messages:
    7,838
    Likes Received:
    664
    Best Answers:
    0
    Trophy Points:
    390
    #3
    I've got the same problem..
    Not got a fix for that though!
     
    sizzler_chetan, Dec 29, 2007 IP
  4. minstrel

    minstrel Illustrious Member

    Messages:
    15,082
    Likes Received:
    1,243
    Best Answers:
    0
    Trophy Points:
    480
    #4
    It's because 2.3.1 changed the database format to UTF-8.

    There were a few fixes posted at wordpress.org, including two scripts, one of which was a dead link. None of the fixes worked for me, although I did get my tables all upgraded to UTF-8. In the end, I went through the posts manually, category by category, finding those with odd characters and manually editing those posts.

    Downgrading really isn't a solution since all future upgrades are going to be UTF-8 as well so sooner or later you're going to have to bite the bullet. Manual editing was a royal pain but it's done now for me and won't need to be redone.
     
    minstrel, Dec 30, 2007 IP
    bogart likes this.
  5. sizzler_chetan

    sizzler_chetan Prominent Member

    Messages:
    7,838
    Likes Received:
    664
    Best Answers:
    0
    Trophy Points:
    390
    #5
    But for a blog with thousands of posts.. it would just be a pain!!!
     
    sizzler_chetan, Dec 30, 2007 IP
  6. minstrel

    minstrel Illustrious Member

    Messages:
    15,082
    Likes Received:
    1,243
    Best Answers:
    0
    Trophy Points:
    480
    #6
    Yep. I don't have "thousands" but it was still a mighty pain.

    I'm just reporting that I researched this over a few days and if there is a good fix for this I couldn't find it.
     
    minstrel, Dec 30, 2007 IP
    Halobitt likes this.
  7. bogart

    bogart Notable Member

    Messages:
    10,911
    Likes Received:
    509
    Best Answers:
    0
    Trophy Points:
    235
    #7
    I was wondering wht that was happening. I dod the same thing and fixed it manually by downing the sql database and cutting and pasting from notepad.
     
    bogart, Dec 30, 2007 IP
    minstrel likes this.
  8. kiplarson

    kiplarson Peon

    Messages:
    449
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    0
    #8
    I manually changed them as well. Ah well, at least that means we'll be set from this point going forward though.

    Least the content wasn't ruined though eh?
     
    kiplarson, Dec 30, 2007 IP
  9. bogart

    bogart Notable Member

    Messages:
    10,911
    Likes Received:
    509
    Best Answers:
    0
    Trophy Points:
    235
    #9
    Under the Options->Reading menu tab you will see Encoding for pages and feeds: that is set for UTF-8

    I'm wondering if you change the setting to ANSI it solves the problem.
     
    bogart, Dec 31, 2007 IP
  10. giorgioarmani

    giorgioarmani Well-Known Member

    Messages:
    2,634
    Likes Received:
    40
    Best Answers:
    0
    Trophy Points:
    160
    #10
    Had exactly the same problem and because I found nothing online about how to solve it, I ended up going through the posts manually just like you guys... Annoying but I guess it had to be done!
     
    giorgioarmani, Dec 31, 2007 IP
  11. minstrel

    minstrel Illustrious Member

    Messages:
    15,082
    Likes Received:
    1,243
    Best Answers:
    0
    Trophy Points:
    480
    #11
    No. At least it didn't work for me. I think that tells Wordpress what to expect but by bthe time I got to that step the upgrade (seemingly) had already modified the database (although not the database settings) so changing it did nothing.
     
    minstrel, Dec 31, 2007 IP
  12. scot184

    scot184 Member

    Messages:
    2
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    36
    #12
    It's a simple fix as far as I know, and one I did with earlier releases. If you open up wpconfig.php in an ftp program, then change the line below, you're good to go.

    Change: define('DB_CHARSET', 'utf8');

    To: define('DB_CHARSET', '');

    So you just remove the utf8 from the brackets, and touch nothing else. Then all your special characters magically get restored.

    Much easier than manually going through each post. :)
     
    scot184, Jan 7, 2008 IP
  13. zaddy

    zaddy Active Member

    Messages:
    388
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    83
    #13

    This is exactly what I did and it works wonders....
     
    zaddy, Jan 8, 2008 IP
  14. minstrel

    minstrel Illustrious Member

    Messages:
    15,082
    Likes Received:
    1,243
    Best Answers:
    0
    Trophy Points:
    480
    #14
    Yeah, but now you're going to have to do that with every upgrade.
     
    minstrel, Jan 8, 2008 IP
  15. Pixelrage

    Pixelrage Peon

    Messages:
    5,083
    Likes Received:
    128
    Best Answers:
    0
    Trophy Points:
    0
    #15
    I had this problem with a blog site and some 40 pages suffered because of it. However I fixed it the hard way :(
     
    Pixelrage, Jan 8, 2008 IP