WordPress.org

Forums

Who do I write to at WordPress to complain about their auto-update policy? (8 posts)

  1. seosoldier
    Member
    Posted 1 year ago #

    I find that many many people are complaining about the policy WordPress now apparently has of auto-updating our WordPress.org blogs/sites.

    I would like to tell people who to write to, to complain about this, in hopes that if enough people write, WordPress will consider NOT making this the default option.

    Surely they (WP) know that some themes or plug-ins will not readily work with the latest WP update and lately they are updating thing so often that this is causing many people many problems.

    I would like to find out who we as users can address this issue to in hopes of convincing them to make NO auto-updates the default option or at least making it a popup when you first install WordPress: "Do you wish to turn auto-updates on?"

    Thank you.

  2. justatest47
    Member
    Posted 1 year ago #

    Unfortunately you can complain but they won't care, they usually don't care so why would they care now? All they care is when you report bugs but as for functions, if they are convinced that this is the right thing to do, no one else could convince them otherwise.... unfortunately.....

    I agree with you 100% all these updates are irresponsible. I remember 4-5 years ago, an update used to come out every 3-5 months or so, these days they seem to come every 1-2 weeks... UPDATE MANIA! :)))) This makes me wonder, is WordPress a huge giant BUG that endlessly needs fixing and updates??? :)) Really odd....

    Indeed all these updates can destroy compatibly with older themes & plugins, many of which are PREMIUM and people paid with money but no longer have any compatibility updates from their developers.

    When an update comes out, I'm always hesitant to make the update. First I study the changelog to see if it can HARM my site instead of "fixing" it.

    Now, here's a way you can DISABLE all these pesky WordPress updates. Add ONE of the codes from below, minor OR full, not both, lol

    Go go wp-config.php and add this code if you want a FULL DISABLE:
    define( 'WP_AUTO_UPDATE_CORE', false );

    Go go wp-config.php and add this code if you want a MINOR DISABLE:
    define( 'WP_AUTO_UPDATE_CORE', minor );

    Explanation

    Minor Disable is when a new update like WP 3.8.2 or 3.8.3 is live, your WP website will update automatically, but when a new full version like WP 3.9 is released, you will have to install it manually.
    Full Disable disables all WP updates (just WP, plugins not included) from performing automatically.

    If you don't know where to add the code in wp-config.php... just add it below this line: define('WPLANG', '');

    Good Luck

  3. We do care, actually. It's just that we feel that the security for the people who don't upgrade is important.

    Auto-updates for minor releases was introduced in 2013 with WordPress 3.7, and has been applied quite a few times since then.

    The auto updates are only for minor release number updates. So 3.8.1 will update to 3.8.2 but it will not update to 3.9. The major version number release upgrades have to be initiated manually in the WordPress dashboard as always.

    The auto updates can be tuned and that includes disabling update emails. In the majority of cases a minor point release should not break anything. It’s really encouraged that users leave the auto updates in place.

    If you really, truly, feel you need to disable them, you should read this codex document: https://codex.wordpress.org/Configuring_Automatic_Background_Updates

    We really encourage people to read this post about updates, before disabling, to understand the rational behind them. They really are well tested, and if you find that you have to 'fix' your site after every minor update, it's probably time for an extensive audit of your plugins and themes, as these changes are usually 1-4 files only, and maybe 30 lines of code at any time. We really do keep 'em as lean and mean as possible.

  4. seosoldier
    Member
    Posted 1 year ago #

    WP says that these minor updates don't cause problems but just today I was reading on a theme forum for a theme I build most of my sites with, that the newest update BROKE some important functions of his theme. This is not some fly by night theme creator but a real business. The theme creator WILL fix it, yes, but the point is we should be given the CHOICE to update automatically or not, NOT be forced to do it.

    If you guys want to end up like AT&T keep not caring, and keep forcing crap down our throats and you'll get beat out by the first great new platform that comes along because people will be ready and willing to JUMP to a new platform that gives people CHOICE. For example I HATE the way Google forces updates and all kinds of intrusive stuff on me and I jumped over to outlook mail.

    By the way you did not answer my question:
    Who is a person in charge of customer retention or something similar that we can write an official complaint to regarding this issue?

  5. wiresplus
    Member
    Posted 1 year ago #

    seoslider,
    I understand your frustration, and have similar sentiments, but Mika was one of the developers who made 3.9, so you'd do well to listen and not slag off. He said, and I quote:

    The auto updates are only for minor release number updates. So 3.8.1 will update to 3.8.2 but it will not update to 3.9. The major version number release upgrades have to be initiated manually in the WordPress dashboard as always.

    So, if your theme is so archaic that a security update will break it... JUST DON'T HIT UPDATE!!!

    It will NOT update automatically unless your hosting has scripts like softaculous that auto-update.

    Yes it's annoying. No it's not fair to say they don't care. And go to wordpress.com for contact details.

    And I have no affiliation with WP, I do not know Mika or any other developer, and I've only been using WP since 2011 - so I'm nobody special. I just hate this 'backlash posting'

  6. Point of clarification: Mika's a "she" not a "he". ;)

    But yes, the auto updates will only update minor version such as 3.8.2 to 3.8.3. Themes, plugins and major version updates to WordPress will not be updated automatically.

    If a 3.8.3 broke your theme then the theme is at fault. If you updated to 3.9, well that didn't happen automatically.

    Who is a person in charge of customer retention or something similar that we can write an official complaint to regarding this issue?

    That one is easy to answer: No such person or organization exists.

    There's a really basic misunderstanding there in your question. WordPress is a community driven open source project. It's free software. You didn't pay for it, you don't have to use it and there is no warranty. There is no customer relationship here and you are not required or obligated to use WordPress. Support is 100% volunteer driven and free.

    That all said: no one wants you to be unhappy and the community here does care. Please review the link that Mika provided.

    https://codex.wordpress.org/Configuring_Automatic_Background_Updates

    That really does provide you with all the information you need to disable auto updates. I hope you re-consider but you do have a choice and that article can help you out.

  7. seosoldier
    Member
    Posted 1 year ago #

    Okay, I appreciate the responses, and I admit to my ignorance that WP is an open source project which does change my attitude towards it and the folks who create it.

    I also just found out that it was not the minor update that broke the WP theme I spoke of above, but it was the major update to 3.9. I am willing to admit when I am wrong.

    That said:
    The point is you should ALWAYS give people the OPTION of updating, whether minor or major. If you were to put a pop-up that comes up when someone first starts with a WP site and it said something like "WP will update itself with minor security updates. We highly suggest you allow this because if not you may regret it by having your site hacked. However if you are an expert user and would like to be notified of updates so you can update manually, please un-check this box."

    I think that would cause the vast majority of users to willingly allow auto-updates (minor updates) and would give the expert users the OPTION of checking to see if their themes and plug ins will still work with the minor update, before updating all of their WP sites.

    For that matter I would also like to see the OPTION to roll back to the last update in the case that something DOES break. It would give one time to contact the vendor of the plug-in or theme and get it ready for the new update, before updating back to the newest version.

    I can't stress how much giving the end user the OPTION to update is important to establish user appreciation, loyalty, and general happiness with your "product" or service. If you took a poll of people who have more than 3 WP sites I'm sure you would find that most agree with me.

  8. just today I was reading on a theme forum for a theme I build most of my sites with, that the newest update BROKE some important functions of his theme

    That is actually scary, not because it happened, but because the theme dev is claiming this.

    Very little changes in minor releases. I'm talking under 100 lines of code and maybe 4 files are touched. I mean here: https://codex.wordpress.org/Version_3.8.3

    wp-admin/includes/upgrade.php
    wp-admin/includes/post.php
    wp-admin/about.php
    wp-includes/version.php
    readme.html

    Of those files, the last three were changes from 3.8.2 to 3.8.3 (that is version changes), and that means there were TWO files touched! If THAT is breaking your code, you have a much bigger issue. 3.8.2 had more changes, but again, look at WHAT changed.

    If those changes break a theme, or a plugin, then the dev needs to seriously take stock in their own code, because we're not making MAJOR changes here, we're making security changes, and if your theme breaks because of THAT then the implication is it was insecure...

Topic Closed

This topic has been closed to new replies.

About this Topic