So for the last few days we’ve been waiting for WordPress to auto update on some work web sites having installed the Auto Updates plug-in and activating it. All it does is enable some built in functions in WordPress using a nice web designer accessible way.
No joy though 🙁
The plug-ins and themes that were waiting to be updated were still waiting.
I was then able to find this plug-in from WordPress – Background Update Tester – via a post by Wendy Cholbi.
It was a bit worrying that it hadn’t been updated for a couple of years but as this is being tested on a staging site I wasn’t overly concerned if the site broke. The fact that it was written by WordPress themselves was an added plus that it was less likely to cause issues.
Installing it added an extra link under the Dashboard option called Update Tester which lead to a status page and that said;
PASS: Your WordPress install can communicate with WordPress.org securely.
PASS: No version control systems were detected.
FAIL: Your installation of WordPress prompts for FTP credentials to perform updates. (Your site is performing updates over FTP due to file ownership. Talk to your hosting company.)
A nice error message that I could resolve 🙂
A quick SSH to the web server to check the user permissions on the files and they were all owned by one of our in-house web developers.
chown apache -R *
chmod -R g+w *
Refresh the page and everything looks good for future auto-updating
Dashboard :: Update Tester page shows;
Automatic background updates require a number of conditions to be met.
PASS: Your WordPress install can communicate with WordPress.org securely.
PASS: No version control systems were detected.
PASS: Your installation of WordPress doesn’t require FTP credentials to perform updates.
PASS: All of your WordPress files are writable.
And the Dashboard :: Updates page says;
You have the latest version of WordPress. Future security updates will be applied automatically.
I don’t like that I have to make the files updatable by the Apache user (and the web server). That to me opens up the possibility of a security issue in the future but on balance waiting on over worked web developers to update the WordPress installation is a bigger issue.