The Danger of Upgrading WordPress

I upgrade to WordPress version 2.6.1, and now all of my posts have stray “�” symbols in them.� Please bear with me while I try to get this fixed. :(

Update: (10 minutes later)  Hey, its fixed.  Just had to comment out a few new lines of code, and we’re back to normal.  Ah, the joys of being your own tech guy. ;)

6 Responses to The Danger of Upgrading WordPress

  1. George says:

    I ran into the same problem when I upgraded my site last week. I’m glad to see you found a solution as quick as I did. I wonder why the WordPress folks added those problematic lines of code in the first place.

    If you run into any WordPress problems in the future, feel free to bounce them off of me. I might not have the answer, but I’m probably experiencing the same problem.

  2. apextrading says:

    What was the code you had to comment out.

    Thanks

    Apextrading
    Http://www.apextrading.webs.com

  3. David Merkel says:

    These two lines in wp-config.php
    // define(‘DB_CHARSET’, ‘utf8′);
    // define(‘DB_COLLATE’, ”);

  4. Thank you for this information. :)

  5. David Merkel says:

    As of version 2.7.1, those lines should not be commented out. Go figure.

  6. Kenneth Lee says:

    I hate upgrading work. I always end up having some kind of errors. What to do, we need to curb vulnerabilities.

 Subscribe in a reader

 Subscribe in a reader (comments)

Subscribe to RSS Feed

Enter your Email


Preview | Powered by FeedBlitz

Seeking Alpha Certified

Featured blogger at Wealth Managers League

Top markets blogs award

The Aleph Blog

Top markets blogs

InstantBull.com: Bull, Boards & Blogs

Blog Directory - Blogged

IStockAnalyst

Business Finance Blogs
OnToplist is optimized by SEO
Add blog to our blog directory.