Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Migrating from WordPress (legacy) cpAddon

Discussion in 'General Discussion' started by EdP, Aug 16, 2017.

Tags:
  1. EdP

    EdP Member

    Joined:
    Dec 19, 2006
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    151
    Location:
    Buckinghamshire, UK
    I need to allow my users to use the new WordPress addon running WordPress version 4.8.1 (at the moment most have 4.7.3 via the legacy cpAddon). I am confused about the best way to let cPanel users migrate to the new cpAddon. In the documentation it says:

    Install cPAddons Site Software - Version 64 Documentation - cPanel Documentation

    To update WordPress (legacy) to the new RPM based WordPress cPAddon, you must back up your existing WordPress content and remove the WordPress (legacy) version. After you remove it, you can then reinstall the new WordPress cPAddon and restore your backup.

    I can backup/restore the MySQL database easily enough, but if I remove the legacy version will it delete all files in the users' root folder, including any wp_content?

    Is there any reason why I can't just install the new cpAddon over the top of the legacy one?

    Does cPanel have an approved way of carrying out these migrations?

    Any help/experience much appreciated so I don't disturb users' Wordpress sites (other than upgrading Wordpress).

    Ed
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,220
    Likes Received:
    1,376
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    The new RPM based WordPress cPAddon is not compatible with legacy cPaddon WordPress installations. Thus, you must essentially install a new instance of WordPress, and then restore the database and any non-core files from the manual backup that you generated. The following WordPress document is useful when generating a backup of your existing WordPress installation:

    WordPress Backups « WordPress Codex

    Thank you.
     
  3. EdP

    EdP Member

    Joined:
    Dec 19, 2006
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    151
    Location:
    Buckinghamshire, UK
    Thank you - I suspected that was the route but hoped it was not!
    Interestingly, one of my cPanel account users seems to already be on the non-legacy version. She has no access to cPanel so must have just upgraded her WordPress version to the latest from the WordPress interface. When I looked in WHM > cPanel > Install cPAddons Site Software there was a link by the legacy version saying 'remove completely' or similar, and the new cPAddon (non-legacy) was ticked. Is that possible?
    If so I could just tell my users to do their own WordPress updating.
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,220
    Likes Received:
    1,376
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Hello,

    It's possible the cPanel user installed WordPress manually using the instructions from WordPress's installation document. In such a case, the installation isn't manageable through cPanel. I recommend leaving the new WordPress cPAddon enabled, as cPanel version 66 includes "WordPress Manager" to go along with it. You can read more about the WordPress Manager feature at:

    WordPress Manager | A Better WordPress Experience with cPanel | cPanel Blog

    Thank you.
     
  5. EdP

    EdP Member

    Joined:
    Dec 19, 2006
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    151
    Location:
    Buckinghamshire, UK
    Thanks. I've checked, and she originally installed WordPress via the (legacy) cPAddon. Subsequent upgrades have been via the WordPress interface. In her cPanel WordPress Manager is available, although it gives an error as follows:

    Both the Current Version and Automatic Updates fields show their status as 'Unknown'.

    I hope this is helpful.
     
  6. EdP

    EdP Member

    Joined:
    Dec 19, 2006
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    151
    Location:
    Buckinghamshire, UK
    Michael. I found the statement that originally confused me, which appears when you open WordPress Manager on an account with the legacy cPAddon still active. It says:
    This slightly contradicts the original statement from the documentation that I referred to in my first post because it implies that installation of WordPress via the new cPAddon is possible without first removing the old one. I think the question I would like answered is:

    Does removal of the legacy WordPress cPAddon (via WHM) remove the actual WordPress installation, or not?
     
  7. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    38,220
    Likes Received:
    1,376
    Trophy Points:
    363
    cPanel Access Level:
    Root Administrator
    Once manual updates have occurred, it's no longer manageable as a cPAddon unless you were to reinstall a new instance of WordPress as a cPAddon and restore the existing data from a backup.

    Thank you.
     
Loading...

Share This Page