Moderator
James Huff
(@macmanx)
Volunteer Moderator
A new version did go out today: https://wordpress.org/news/2014/08/wordpress-3-9-2/
Despite modification date, does the about.php file mention 3.9.2 on line 44?
It occurred on 4-5 of my clients sites. All mention 3.9.2 on line 44 except one which updated to 3.8.4. I have never turned on anything to setup auto updating. In fact I no idea how to do such a thing.
Moderator
James Huff
(@macmanx)
Volunteer Moderator
WordPress has supported background auto-updating since 3.7, it’s actually an opt-out feature, not something you have to setup.
Can you please tell me where or how to opt out?
Moderator
James Huff
(@macmanx)
Volunteer Moderator
Sure, just follow this guide: http://codex.wordpress.org/Configuring_Automatic_Background_Updates
As a warning though, please do your best to stay up to date. Once a security vulnerability is plugged via a security release, like WordPress 3.9.2, it essentially becomes public knowledge.
I do try to keep my clients’ sites up to date. However, I always perform the update myself. I have been using WP for several years and I have NEVER had a site auto update itself and send me an email. And the fact that it happened to several of my sites at once is rather suspicious, don’t you think?
Moderator
James Huff
(@macmanx)
Volunteer Moderator
And the fact that it happened to several of my sites at once is rather suspicious, don’t you think?
Not really, no. The auto-update system on this end starts running as soon as the update is released. I’d say that several million sites were probably updated around the same time.
Hmmm. It still seems odd. I’ve built dozens of sites over the years but I have never had one update itself. The sites look OK though. This is just a baffling anomaly to me. Thanks for you help James. I will leave the topic open for another day or two just to see if anyone else wants to comment.
Cheers!
Moderator
James Huff
(@macmanx)
Volunteer Moderator
You’re welcome!
I have had almost exactly what you’re describing happen before. In my case, part of the server configuration (one of the mod_security rules, I think) was blocking the automatic updates. If someone else had updated the server to correct the problem, I probably would have been surprised by the next auto-update too. 🙂
