P.S. has anyone had any experience with a plug in like: https://ww.wp.xz.cn/plugins/wp-disable-automatic-updates/ Will it make a difference or just it just inject the same code I’ve already tried?
Hi,
I’m afraid you’ll have to contact your host if something is still forcing updates on your site in a scenario like this, the define line in your last bullet point is the “above all else” control for WordPress, with it in place, the update has to be ran through your host in some way.
You did not mention the plugin Classic Editor in your post. Do you have it installed?
Then you can update to 5.0 and still use the old editor, which more or less is 4.9.8 with a new version number.
Could this be some sort of cpanel updater trying to do it automatically (ie Softaculous?)?
Thank you, Marius.
I’m well aware of the classic editor. My site is using an old theme, and old plug-ins and is not ready for the update. I had planned on the extra time due to SiteGround saying they would not be forcing the update. This is a ridiculous time of the year for a major update like this to have been released.
Hristo from SiteGround. We’re not forcing your updates. There’s something else going on with your website. Check if you have any management software that does it to you.
Although I am positive it’s not us, care sharing a server or domain so I can double check?
perspectiveexploration.com I already have an open ticket with you. Everyone at SG has always been very helpful. This problem is particularly vexing though.
tgedge1, No Softalicious or anything of the sort I’ve been able to find. SiteGround has their own updating system that you can place your site under and that’s the only cPanel type thing I’m aware of that would affect this. Continuing to investigate.
Does WP not have a log somewhere that indicates when events happen and how they are triggered?
No, WP doesn’t keep log on updates.
So, at this point, I may be spending the weekend upgrading this site. In order for me to turn off any plug-ins and revert to my previous version, keeping it from upgrading again, I need to do a restore. I have twice now restored both the files and the database. Each time I do, the site IMMEDIATELY upgrades to 5.0. I have no time to place define( ‘WP_AUTO_UPDATE_CORE’, false ); into the config file, nor to remove any suspect plug-ins.
Since this is a shared server host, I can’t disconnect it from the Internet to avoid the immediate update (assuming that would work).
Anyone have any ideas on how to keep it from immediately updating before I resolve to losing my weekend to making things work with 5.0?
FYI, I have updates disabled on my blog with the following in wp-config.php:
define( 'AUTOMATIC_UPDATER_DISABLED', true );
It’s never updated anything automatically since, including to 5.0. I did update my local copy to 5.0 before updating the one at my webhost (which I haven’t done yet).
Is there any way to modify the contents of the wp-config.php within the restore files before doing the restore?
I asked SG about that Mark, and they said there was no way to modify the backup files. I have my own backups. And it might be possible for me to address things from that direction. I gave some thought to how much time/effort that might take only to not find the issue and decided that time/effort would be better spend just plunging ahead into upgrading things for 5.0.
I will say that I highly suspect the issue was caused by one of two plug-ins that another host (BlueHost) installed when I was hosted there (the site was later migrated to SG). Apparently, BlueHost had a habit of installing “must use” plug-ins. From what I’ve read online, it appears they did this without informing users. I certainly don’t recall ever receiving notice about it. Yet, there they are. And again, I have no way to restore and then remove them to test the theory because the update happens immediately after restore, even if I add the updater_disabled code into the config file prior to restoring the database.
I would delete the Bluehost must-use plugin from cPanel -> File Manager, SSH or FTP to stop it from updating your site. Then, you can simply login to your account via SSH and do a ‘wp core update –version=4.9.8 –force’ and WP-CLI will bring you to that version. Of course, if you restore from backup and then rapidly delete the BH plugin, that won’t be necessary.
Unfortunately, I’ve settled on making 5.0 work and won’t be able to try that Hristo.
FWIW, I tried multiple times to rapidly delete the plug-in after a restore and it never worked. The update would happen immediately every time. Before I could even delete the plug-in.
