Migrating from WordPress (legacy) cpAddon

EdP

Member
Dec 19, 2006
14
0
151
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
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,884
2,250
463
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.
 

EdP

Member
Dec 19, 2006
14
0
151
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.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,884
2,250
463
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.
 

EdP

Member
Dec 19, 2006
14
0
151
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:

Warning: The system could not load some of this WordPress installation’s data. Certain sections of this interface may not function correctly.
(XID f49ug5) The system failed to run the wp-cli batch commands with the following issues: Warning: Missing argument 2 for Jetpack_Autoupdate::autoupdate_core() in /home/accountname/public_html/wp-content/plugins/jetpack/class.jetpack-autoupdate.php on line 98
Both the Current Version and Automatic Updates fields show their status as 'Unknown'.

I hope this is helpful.
 

EdP

Member
Dec 19, 2006
14
0
151
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:
Warning: This installation uses WordPress provided by the legacy cPaddon distribution system. We plan to remove the legacy distribution system soon. After we remove this legacy system, you will no longer receive updates for this installation. To resolve this problem, you must install a new instance of WordPress with the non-legacy WordPress cPaddon from cPanel’s Site Software interface. After you complete the new WordPress installation, you can manually migrate your WordPress site content and configuration to the new installation.
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?
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,884
2,250
463
Thanks. I've checked, and she originally installed WordPress via the (legacy) cPAddon. Subsequent upgrades have been via the WordPress interface.
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.
 

MACscr

Well-Known Member
Sep 30, 2003
198
5
168
cPanel Access Level
Root Administrator
Am I reading this right? If a wordpress is is updated through wordpress's own auto upgrade feature, the cpanel wordpress manager will no longer be able to manage it? If thats the case, the wordpress manager is worthless and your team wasted time developing it. Simply unrealistic.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,884
2,250
463
Am I reading this right? If a wordpress is is updated through wordpress's own auto upgrade feature, the cpanel wordpress manager will no longer be able to manage it? If thats the case, the wordpress manager is worthless and your team wasted time developing it. Simply unrealistic.
That's in reference to legacy installations of Wordpress. Installations completed through the new WordPress Manager feature allow for automatic updates. You can read more about it at:

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

Also, check out the comments section of this blog to see some questions/answers regarding it's implementation.

Thank you.