Auto Updates?

Marj Wyatt
(@marjwyatt)

12 years, 3 months ago

I was just alerted that one of my sites updated. I understand I can disable this but, frankly, I’m alarmed that this feature was implemented.

I do not allow any software to update automatically in my home office. I maintain the websites of many clients and I always perform a backup before updating their sites so I have a recovery path if a plugin fails or something else.

Thanks to this new “feature” I now have a lot of unplanned work to do because I have to modify the wp-config file to disallow this function for every site that I maintain.

I understand that old code is high risk, and I have educated my clients to understand this too. But the fact of the matter is that there have been WP upgrades which have NOT gone smoothly and I’ve been very glad that I waited a couple of weeks for the bugs to be worked out.

This, in my professional opinion, is NOT a good idea … not at all a good idea.

I take responsibility for not reading through the 3.8 release notes and taking action then to stop this intrusive functionality.

<end_rant>

Viewing 15 replies - 16 through 30 (of 98 total)

← 1 2 3 … 5 6 7 →

Andrew Nevins
(@anevins)

WCLDN 2018 Contributor | Volunteer support

12 years, 3 months ago

I’m a code person and not concerned about modifying functions.php and/or wp-config.php.

Sorry I misread that as “I’m not a code person and concerned about modifying…”

Thread Starter Marj Wyatt
(@marjwyatt)

12 years, 3 months ago

No problem.

dagreco
(@bball463)

12 years, 3 months ago

Oh I am quite angry that it auto updated. it cost me $180,284.00 I was waiting to update, as I always do for 3 days after a release. I was showing a client the difference in several features. Because of this auto update I lost his contract ($83,644.91 a year for 8 years)And this happened on 3 sites with 3 different clients totaling the $180,284.00.

Andrew Nevins
(@anevins)

WCLDN 2018 Contributor | Volunteer support

12 years, 3 months ago

@bball463, I would seriously consider using another CMS completely.

dagreco
(@bball463)

12 years, 3 months ago

Kind of difficult when my business is WordPress. I have 24 clients all using WP.

dagreco
(@bball463)

12 years, 3 months ago

The Plugin that Andrew is mentioning seems to work great. Thanks for the suggestion.

DFlynn
(@dflynn)

12 years, 3 months ago

Hey Andrew,

Thanks, I am trying to activate that plug in now.

DFlynn
(@dflynn)

12 years, 3 months ago

Andrew,

Can you tell me what is the difference, exactly, between a

minor update
major update
development update

Thanks,
David

Andrew Nevins
(@anevins)

WCLDN 2018 Contributor | Volunteer support

12 years, 3 months ago

I can’t, I’ll wait for someone more knowledgeable to post

Thread Starter Marj Wyatt
(@marjwyatt)

12 years, 3 months ago

This documentation at Codex endeavors to explain the types of updates and also how to fine tune the automatic nature of them:
http://codex.wordpress.org/Configuring_Automatic_Background_Updates

keeperbay
(@keeperbay)

12 years, 3 months ago

Problem #1. Why does WP Core think that posting a link to Codex will help? Most Bloggers Know Nothing About Code!

Problem #2. Auto Updating assumes that all plugins are going to automatically work with the new version of WP – When has that EVER Happened?

Problem #3. When Problem #2 occurs, those bloggers who fall into the category of Problem #1 are stuck paying to have their sites restored, fixed or rebuilt.

DFlynn
(@dflynn)

12 years, 3 months ago

Thanks Andrew and thanks Marj. I am reading the link now.

And I totally concur with Keeper.

Thread Starter Marj Wyatt
(@marjwyatt)

12 years, 3 months ago

I have suggested in other circles (a skype group where a couple core developers are) that, if the assumption is that most won’t upgrade regularly, WP Core could write a “restore point” sort of functionality that gives site owners and their developers a way out of the update if it doesn’t apply smoothly.

I’m not holding my breath…

The first thing that I do when I get a new computer or new software is disable auto updates. I set it to be notified and I make the choice about when to perform that upgrade. It seems to me that this is a much better method than rolling out an update without any means of backing it out, other than whatever processes and procedures have been implemented for that installation for regular backups, etc.

keeperbay
(@keeperbay)

12 years, 3 months ago

Have installed the “Disable Auto Update Patch” on 45 WordPress blogs today.
Have 120 more to go.
More orders rolling in.
Once again WP Core is keeping me gainfully employed.

@dflynn – we need a “Like” option here lol

keeperbay
(@keeperbay)

12 years, 3 months ago

@marj, That’s a great idea, but how would the restore point be accessed? It can’t be from the admin, because that assumes that the admin dashboard is accessible.
It can’t be from the FTP since that assumes that the FTP is accessible, but that depends on hosting and developer.

Like you I understand the importance of updates and I also disable them in everything. I let all the newbie eager beavers crash their sites, let fixes be implemented – THEN I update. This is a lesson I learned from WordPress. Along with BACKUP BACKUP BACKUP! I am speechless by what WP Core has done – well maybe nearly speechless.

Side Note: Another Female Developer! FINALLY!