SiteGround Auto-Updater and ClassicPress


I suddenly wondered whether SiteGround’s famously aggressive WordPress auto-updater would see ClassicPress sites as WordPress 4.9.10 sites and promptly update them to the next version of WordPress when it is released. In the past I’ve sent SG tickets to exclude all my sites from the auto-updater, and they have complied, but it’s possible that one or two slipped through the net.

So I’ve sent them a ticket:

“Several sites in my account and my other accounts are now running on ClassicPress, not WordPress. However your WordPress auto-updater will probably detect them as running WordPress 4.9.10 (because ClassicPress is derived from WordPress).
Please can you assure me that no ClassicPress sites will be automatically updated when the WordPress updater updates in the future.
For information about ClassicPress, please see .”

I’ll let you know what they say.


Hosting provider master thread: SiteGround
Should ClassicPress offer hosting recommendations?

They replied quite quickly and requested that I give them a list of all my CP sites so they can ensure these are left alone by the auto-updater. So that’s what I’ve done.
I’ve also told them more sites will be switched in the near future and it would be far better if they could simply turn off the auto-updater per client, not just per site. I suspect they’ll ignore that though.



Good to know about this and that they’ll work with you. Maybe if their updater could just check for the existence of the classicpress_version function, or something…



Well I don’t mind asking. Which core file is the function in?



SiteGround isn’t the only one that does the auto-update thing… I wonder if we should compile a list of hosting companies that do that, so as we grow and more people make the switch, they are armed with information that they can use to protect their site from being “auto-updated” back to WP?



My host (a2hosting) auto updates, but they do recognise that ClassicPress is not WordPress.

I had a false positive when I migrated over and thought it was incorrectly identifying a site as WordPress instead of ClassicPress. They were very nice about not calling me an ass while pointing out it was still running WordPress. I’d forgotten to update that site.



classicpress_version is defined in wp-includes/version.php for ClassicPress sites.



Thanks James. I’ve now asked SG about this.

“It would be useful to the growing number of ClassicPress developers if your autoupdater could recognise and ignore ClassicPress installations.
it’s quite easy: if the file /wp-includes/version.php contains a function called classicpress_version, then the installation is a ClassicPress one, not a WordPress one.
I and other ClassicPress developers would be grateful if the autoupdater could be updated to check for this.
Thanks very much.”



I tested SiteGround—great and helpful support, but for me, the auto-update feature was indeed one reason why I cancelled my plan after less than a month. I hope that they will consider the function allowing to identify a CP site. Beside the practical issue, such moves also contribute to the awareness that CP exists.



The guy on my SiteGround ticket promised to raise the issue in his daily report to his manager.



I had them turn off the auto-update feature and have had no trouble since.



I have also contacted Siteground with regards to autoupdates with a similar message to @zigpress. Their reply -

Unfortunately, it is not possible to disable the Auto-Update tool for future installations and you might have to contact as again via another support ticket for this matter.

However, I am going to pass your recommendation to our developers by leaving this ticket in my daily report. If the implementation of the above mentioned check can be easily made, there is a high percentage that our developers are going to make it in future updates of the tool.

So there’s hope and good reason for creating support tickets :wink:



That’s great, thanks Christine :slight_smile: