Plugin updates manager WP 5.5 compatibility

  • Since WP 5.5 added the option of managing auto-updates this option table isn’t as necessary for most sites anymore, while some options might still be interesting.

    Essentially the problem is that it overrides everything and should instead use the newer code version to change the auto-update status BUT without overriding it.
    The meaning here is to be able to manage update settings using the plugins/theme page which is more UX-logic.

    Here is an article that describes it @ make.WP :

    Here is the related part :

    Blanket auto-update opt-in

    If a developer wants to enable auto-updates for all plugins and/or themes (including any that are installed in the future), the auto_update_plugin / auto_update_theme filters can be used.
    add_filter( ‘auto_update_plugin’ , ‘__return_true’ ); add_filter( ‘auto_update_theme’ , ‘__return_true’ );
    Note: Any value returned using these filters will override all auto-update settings selected in the admin. Changes made using these filters also will not be reflected to the user in the interface. It is highly recommended to use these filters in combination with the hooks detailed above to inform the user of the auto- update policy being enforced.
    This approach will not be appropriate for all sites. It’s recommended to use the new UI to manage auto-updates unless you’re sure blanket opting-in is right for your site.
    Also note: This filter was added to the codebase in WordPress 3.7.0 and is likely being used to blanket enable auto-updates for plugins and themes on sites today. If it appears the new UI elements are not changing the auto-update behavior for plugins or themes on your site, this may be why. #50662

    Waiting for your quick fix pls ??

    • This topic was modified 4 years, 2 months ago by tdechangy.
Viewing 2 replies - 1 through 2 (of 2 total)

  • Hello.

    Not all sites have the latest version of WordPress installed, so we can’t use the new auto-update method. Also, many people have auto-update configured in our plugin.
    Users can choose which auto-update tool to use. If you have WP 5.5, you can disable the Update Manager component and use the native tool.

    Thread Starter tdechangy

    (@tdechangy)

    You’re right, I totally forgot that the update manager was a “component”, so I will most probably disable it for most/all sites.

    Otherwise, to let users benefit of some advanced features… I get the point that some users could keep a deprecated WP version, but this is as you know a bad practice. I see these options to solve that :
    1/ wait 2-3 month to do the switch to the new WP auto-update code
    2/ include it right now alongside the old version and use the correct one by detecting which WP version is used. This would be super clever and answer each-ones needs.
    NB: of course using the new WP auto-update code, all changes should be reflected on the plugins/themes pages as well as on your Clearfy dashboard, wherever the option was selected.

    Regards.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Plugin updates manager WP 5.5 compatibility’ is closed to new replies.

Tags