Upgrade from 2.3.3 to latest version

  • Photorestorationman

    (@photorestorationman)


    15 years ago

    I have WP v 2.3.3 and have read that upgrading needs to be done in a two step approach. My blog is turning into a monster and I am nervous about upgrading. I do not want to have any downtime and want to make sure that all my links remain the same.

    In the past, in the early days I upgraded ok but now I keep reading of possible hurdles and pitfalls of doing so from such an old version. I fear i don’t upgrade soon I will be left in behind permanently.

    Has anyone upgraded from 2.3.3 to latest and how did it go. I am not an expert on this by any means.

    Any help or views would be much appreciated.

    Neil

Viewing 4 replies - 1 through 4 (of 4 total)
  • Roy

    (@gangleri)

    Start with an export and a database backup.
    I wouldn’t try to upgrade in one step, but I do not know which version got major database changes. The safest way would be to go step by step. 2.5, 2.6, 2.7, 2.8 and 2.9, manually of course. You can get all old versions here: https://www.ads-software.com/download/release-archive/

    adiant

    (@adiant)

    There are detailed instructions for upgrading from a very old version here:
    https://codex.www.ads-software.com/Upgrading_WordPress_Extended#Detailed_Upgrade_Instructions_for_1.5.x.2C_and_versions_2.0_-_2.6.5.2C_to_2.9.1

    BUT….

    If you don’t want any downtime, you are going to need to build a “test system” that is as isolated as possible from the “production system”, but is a clone of the production system. Try the upgrade there, and keep working at it until you have it figured out, then make a detailed plan for upgrading your production system.

    It all starts with a Backup of both the database and WordPress files. Not just to do the cloning from, but also to protect you if the cloned test system somehow interferes with the production system. For example, if it is not very well isolated from the production system, you could end up having the test system write to the production system’s database or file system.

    I have a Reseller account with my web host, which gives me separate subaccounts in separate filespaces. If one subaccount tries to access the database of another subaccount, it fails (unless I specifically authorize external access to/from the other subaccount’s database).

    I build my cloned tested systems from the production system by creatively following/modifying these instructions:
    https://codex.www.ads-software.com/Moving_WordPress

    Thread Starter Photorestorationman

    (@photorestorationman)

    Thanks, I have now upgraded to 2.5 so I am getting there

    Thread Starter Photorestorationman

    (@photorestorationman)

    Many thanks to the posters who gave me the confidence to upgrade my phoro restoration blog. It went 2.3.3 to 2.5 to 2.7 to auto upgrade to 2.9, now all I have to do is change to 2 columns to allow my photo restoration video tutorials to fit in. Thanks again.

    Neil

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Upgrade from 2.3.3 to latest version’ is closed to new replies.