The latest version of WordPress has been billed as the ‘No Click’ update: it is designed so that all minor security and maintenance updates are processed automatically, in the background, with no need for a site owner to do anything. This has, of course, raised some ire amongst a few users but, at the same time, brought a small piece of code out which can be used to stop the automatic updates, since there is no stop option and update is by default.
Photo Credit: Peregrino Will Reign – Creative Commons
But, and there always has to be a But: it doesn’t necessarily work with all sites and it isn’t necessarily immediate. That is, when a new security update is issued, it doesn’t hit every single WordPress site all at once, so far as I can see. I suspect this, more than know it, simply because WordPress v3.7.1 was announced as being ready for issue over the weekend. Here we are at Wednesday, and my site hasn’t updated. Instead I got the usual WordPress Update notice on my Dashboard with an Update Now button, just the same as it always was.
But wait: normally I would then have to go to wordpress.org and download the complete package just to perform a few minor updates. This time I thought, well, if it’s supposed to be automatic, let’s try it out. Normally the Update Now button wouldn’t work because I have not defined my FTP access for security reasons. A click on the button would tell me this, and I would have to go to wordpress.org and download the entire package.
One click, rather than no clicks, and the security update was installed with a little message telling me that my site is compatible for automatic updates – which I knew – and we’re done. Perhaps next time I’ll get the much vaunted No Click?
Love & Kisses, Viki.