WordPress 3.2 Upgrade

  • Hi Folks,
    Just updated a couple of my sites to 3.2 and they are pretty messed up.
    My Dashboards are hardly recognizable. There are no longer plug-in areas to undo whatever 3.2 did. The Dashboards are almost useless.

    I’m just letting somebody know there’s a big problem with the 3.2 upgrade.

    Thanks for listening.

Viewing 5 replies - 1 through 5 (of 5 total)

  • smith, people can’t help you without more detail:

    “There are no longer plug-in areas to undo whatever 3.2 did”
    no idea what you mean here

    “The Dashboards are almost useless”
    The dashboard is a hell of a lot faster and has had a UI overhaul, but has stayed essentially the same. please provide more detail.

    Sounds like JSON is not enabled on your web host. Contact your web host and have them enable this on your server.

    This is a server requirement that was not needed for previous versions of WordPress until 3.2 came out.
    https://www.argoworks.com

    Daniel

    (@danieldlaine)

    I also had problems with the 3.2 upgrade. I couldn’t access the dash, getting 2 errors, one warning and one fatal – file not found; class-json.php from /includes, so I just made an empty file from notepad, uploaded it and it worked again. I know this is not the correct fix and would be grateful for any info on why.
    Regards
    Daniel D’Laine

    If you need to roll back to 3.1.4 (or any other version), I used this video here. It’s scary so make sure you backup everything, and do exactly what he tells you. I actually had 2 backups. There’s also an article that the guy links to. It worked 100% for me to roll back.

    3.2 was fine except that one of my plugins Jquery colorbox sort of broke and I couldn’t get it to work with my top gallery. Make sure to notify the authors of whatever plugins you are having trouble with if that’s your issue.

    ——
    https://viewofthedrew.com

    Daniel

    (@danieldlaine)

    Thanks for that. I sorted it in the end. Once I could get back into the dash, I could see it was the WP-to-Twitter plugin that was causing the bother. It obviously didn’t like WP ver 3.2 – or WP 3.2 didn’t like WP to Twitter :0)
    Thanks again
    Daniel D’Laine

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WordPress 3.2 Upgrade’ is closed to new replies.