Updating 3.1 to 3.2; any known issues? (5 posts)

  1. JoePUK
    Posted 3 years ago #

    Hi all!

    I was wondering if I could pick everyone's brains about an issue I'm dealing with.

    Recently started a new job and inherited a badly maintained set of WP installs, the most significant of which are running WP 3.1. I want to start updating them as soon as possible, but I wanted to ask if there are any known issues with this update path that I might run into? Anything you can think of that might save me time?

    Also, should I follow the longer legacy update path (3.1 > 3.1.1 > ... > 3.2 > 3.2.1) or simply lump for a full version jump (directly from 3.1 to 3.2.1)? Any advice about which way I'll run into least problems?

    Thanks for your help, I really appreciate it.



  2. esmi
    Forum Moderator
    Posted 3 years ago #

    A jump straight to 3.2.1 should be OK. Just make sure that you backup the database, deactivate all plugins and switch to the Twenty Ten theme before starting the upgrade process.

  3. JoePUK
    Posted 3 years ago #

    Thanks Esmi! I really appreciate it.

    They're all using custom themes actually, do you know if there's been any depreciated template tags since 3.1?

  4. esmi
    Forum Moderator
    Posted 3 years ago #

    Off the top of my head, nothing major in the way of deprecations. I think the worst you would get is some warnings being displayed if your server is configured to show warnings. What you could do is install the Theme Check plugin before you upgrade and run it on these custom themes. That should highlight any potential issues.

  5. The JSON issue was resolved in 3.2.1 so there shouldn't be anything.

    Read http://codex.wordpress.org/Version_3.2 and http://codex.wordpress.org/Version_3.2.1 to get more details if you want on what changed.

Topic Closed

This topic has been closed to new replies.

About this Topic