7 Comments

  1. Rod Olman
    · Reply

    Why does WordPress insist on forcing updates? Didn’t they learn anything about the forced alpha version update a few days ago?

    WordPress feels less and less like self-hosted blogging system and more like Windows 10, where the corporation behind it has total control of one’s PC.

    Report

  2. Jonathan Desrosiers
    · Reply

    not in favor of using a filter to hide the UI on a page that is not likely to be accessed by users who have the ability to update core

    I’d like to point out that this is not an accurate summary of my current stance as expressed on the ticket. From my comment:

    ” The update page is ONLY accessible to those WITH the update_core capability.

    It’s not that the users are unlikely to access the page with the new UI. It’s that this page is only accessible by Administrators (by default), and these users actually should be presented with this information.

    By default, only Administrators have this capability. If a site owner does not want auto-updates for major versions, then they should use the constant to enforce only minor updates (or none, if desired).

    Rather than allow this UI to be hidden entirely, I’m arguing that it would potentially be a better user experience to instead disable the form when auto-update behavior is being controlled by the constant and inform the user (who will always be a trusted individual because they have the update_core capability) of how the site will behave when new major and minor versions become available for auto-updating.

    Report

  3. Gary Taylor
    · Reply

    Could the note be dynamic, with three options? Read the current version (it’s stored as a variable somewhere), then add three options/checkboxes:
    – automatically update to 5.6 when it comes out.
    – automatically update to 5.5.4 when it comes out.
    – remember these settings after the next update.

    And a link to a wordpress.org post explaining the differences more fully.
    And only available to Admin users, of course.

    Report

    • Cavalary
      · Reply

      Something like that would actually make sense, including clear options for both major and minor updates and remembering the setting after one update or not. Could also use the text to explain major and minor, as in (assuming a start from 5.6, and checks representing defaults):
      [ ] automatically update to the next major version (5.7)
      [x] automatically update to the next minor version (5.6.1)
      [x] remember these settings after updating
      But, of course, since it’d make sense, not to mention also make it easier for users to get back more, it won’t happen.

      Report

  4. Petr
    · Reply

    Oh, now I’ve got it! The last two funky updates were a teaser for this new feature, right?

    Report

  5. Ciprian Popescu
    · Reply

    Depending on how well the theme is coded and how the plugins are being kept up to date, I think it’s a great feature for website maintenance companies or for multiple site admins.

    I have already started using the auto-update feature for plugins and I’m always up to date (same day or next day updates), so it’s a pretty solid setup. Being a theme/plugin developer myself, I try to keep on top of all the plugins I’m using by always reading the changelogs and the upcoming (or deprecated) features. This way I’m not taken by surprise when a major update is due.

    Report

  6. Lee
    · Reply

    Auto-updates prevent site admins and site managers seeing any of the new benefits that are shipped with plugin and theme updates and they prevent them knowing whether security holes have been patched. This is a disservice to end users. How are site admins and site managers to know to check for data breaches or content graffiti? When plugins that integrate with 3rd party services are updated and they require new API keys or re-authorisation with 3rd party services, how do site admins and site managers know they need to act unless they get a notice to tell them?

    The auto-update needs a rethink before it’s universally enabled or before it’s generally available to be enabled.

    1) Website developers and site maintainers need a way to disable auto-updates through wp-config.
    2) Plugin and theme developers need a simple way to notify site admins of feature additions and security patches via an admin messages/notices page in the Dashboard. Not just a Dashboard notice but an inbox for admin notices.
    3) Changelogs need to be emailed to site admins and site maintainers.
    4) There needs to be a way to set the recipient of update notice emails (and error emails) in the site settings admin page.
    5) The system that checks whether a site is down needs to be external to WordPress core. This way the error messaging system will not be dependent on the functioning of WordPress core.

    I’m about 50/50 on whether auto-updates are a good idea. Maybe a little more against than for. I will be more comfortable with auto-updates when the feature has been given more thought. It’s a good idea but badly executed.

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: