There has been a lot already posited on this subject, but in my corner of the WP world I figured I’d throw in my $0.02.  As someone who has been involved with IT for some time now, I’m well versed on the double-edged blade that is auto-updates.  On one hand it offers a respite for weary, overworked tech folk, but on the other hand updates are no different from the rest of the software development process – bugs are inevitable and bad things can happen.

A quick Google search will reveal all of the automatic updates that wreaked havoc on systems across the Internet, albeit a small percentage.  But still, I’d rather spend my work day implenting improvements than fixing something that hosed my operating system or website  So, it comes down to a question of the greater good versus individual control.  I tend to lean on the side of individual control, but then I guess I fall on the side of the auditorium of users that is probably more versed in tech than some others that maintain WP sites.  I understand the decision of the WP core devs to initiate auto updates given some of the ugly flaws that have happened over the last few years, but I’ve also been bitten a couple of times where even minor updates have broken a plug-in or two.

But this post sums it up the best, and I think that the user “Central Geek” is right on the money with why auto updates is a bad idea.  I love WP and I think it is a great platform, but I am not happy about the auto update feature, and even less happy that there is no check box for advanced users to disable it.

Just my $0.02…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s