This is a follow up on the various SiteGround threads like this and this one.
While working on the CP docs I reached out to SiteGround to inform about the status of their auto updater. In the past SiteGround updated a new CP-install to the current WP version. This is partly fixed, their response:
After a thorough review and consultation with our technical team, I want to assure you of the following:
1. Our auto-update system is designed to enhance security by keeping sites up to date. However, we have confirmed that our auto-update feature should not cause any issues with ClassicPress installations. While there are script similarities with WordPress, these should not interfere with the functionality of your ClassicPress sites.
2. If any users prefer to have manual control over updates, they can reach out to us to request that the auto-update feature be disabled for their account. This is entirely optional and available for those who want an added layer of control.
3. Although our system currently does not automatically detect WordPress installations that have migrated to ClassicPress, we are considering enhancements to improve this capability in the future.
So it seems that the problem may still exist for sites that are migrated from WP to CP.
Because I’m not a SiteGround customer, I was not able to test this myself.
Guido, SiteGround is an excellent hosting platform - but like many of the larger hosting companies, they do auto-update wp core.
I’ve seen others in the past forum posts, have their CP sites auto-updated. Even when they asked SiteGround to switch it off. So, if you have a CP site, then it may be better to avoid SiteGround, or any host that auto-updates wp core.
I guess you don’t run into this if your host offers tools such as Installatron or Softaculous to install CP. I’m pretty certain their update system supports CP in that case.
We do have Softaculous on our server, but don’t force WP core updates. And clients have control over those updates if they want them or not.
Companies like SiteGround have their own scripts and cPanel integrations that force these updates. It’s an all or nothing approach with them. Bluehost even force installs their own mu-plugins into WordPress you can’t remove.
To be clear, Site ground has agreements in place with Automattic.
That is why they have their own scripts that install WP.
That is also why they switch CP sites to WP even when asked not to.
They promote WP and don’t care to respect users’ wishes.
So the issue is NOT solved (with them and all other hosts doing the same). It is better to avoid Site ground, and consider that on this forum it’s possible to find companies that not only host CP sites but offer CP support as a complimentary service.
Elisabetta, completely agree. There are other reasons as well.
Apologies to hijack Guido’s post, but if anyone wants to move from Site Ground or similar for their CP sites, we are already hosting CP sites and happy to help.