1. Marcus Tibesar


    I did notice a marked improvement in the speed of page loads.

    Great job WP 5.5 contributors!


  2. Marcus Tibesar

    Another observation after updating to WP 5.5:

    I cannot enable auto-updates for all plugins. For example, Restrict Content Pro, BBQ Pro, Blackhole Pro, Newspack Blocks, WP Retina 2x Pro, and some extensions to the main plugins will not allow Auto Updates.

    After enabling updates for all plugins; 26 plugins are now enabled for Auto Updates while 17 plugins are not enabled and can’t be enabled.

    Am curious if anyone else experienced this behavior when enabling Auto Updates for plugins?


    • Dōvy Paukstys

      This is probably due to the fact that we, the developers, need to now hook into another filter to enable automatic updates. Give it time, those premium plugins will eventually offer the same functionality.


    • David Artiss

      As you may have realised from the fact that most of those plugins are “Pro” versions, automatic updates don’t work, by default, for code hosted outside of the WordPress.org repository.

      In a nutshell, it can’t update code that it doesn’t have access to the source for – hence the hooks that Dōvy mentions).


  3. Stefan

    What a great update. Yay auto-updates 🙂


  4. Bastian

    Just a question. How can I disable the activation of auto updates for a specific plugin? Is there any hook available?



  5. Joe

    Those are amazing feature so finally we won’t need to disable/remove old plugins and themes to update them to latest versions.. This was so annoying time consuming issue.
    There is also an uldate related to wordpress cache.. In WordPress 5.5 a new function was added called wp_cache_get_multiple() with the capability to get multiple cache keys in a single request. The function wp_cache_get_multiple() accepts an array of keys and fetches multiple cache values from the same group.


  6. David Anderson

    “These updates will happen the same day they are available, so users don’t have to check in as often and sites are better protected from plugin and theme vulnerabilities getting exploited.”

    I think that “same day” will prove to be a mistake. The next time a plugin with a lot of users releases a version with some fatal error that got through their testing (e.g. incompatibility with some other plugin, or specific old PHP version), automatic updates will mean that the number of people affected will be much larger. I’d have suggested that it be something like 2-3 days. That, of course, still means a larger window of vulnerability if the release was a security one – but these things are always trade-offs. (If plugin authors had the facility to tag their releases as security/critical ones that would help towards a solution).


  7. Trishan Mehta

    Although I did like most of the features, I do not like the fact that converting a paragraph block into an H3 block requires two clicks.

    The dev. team should introduce a dropdown or accordion for the Heading tab so that users can directly select the desired heading level instead of first converting the Paragraph block into H2 (which is the default heading level) and then onto something else.


  8. stefanos

    I think the auto-update will cause unnecessary headaches and let me explain why…and I hope I’m wrong.

    If an auto-updated plugin is problematic, imagine how customers will feel when they work on their website without knowing an update runs behind the scenes, and all of a sudden they get these messages about “something went wrong” and have no idea how to access their websites.

    I have had a situation like that with WooCommerce…twice please!

    I immediately went on my hosting service, read the logs, and found the problem.

    Imagine now being a standard user that is not a WordPress developer how they would feel.

    I honestly have mixed feelings about this, not denying about it.

    Closing, I would like to ask the WP Dev Team: how is the auto-update procedure goes?

    a) Does it save a backup of the current plugin state before the upgrade?
    b) How does it prevent possible corruption during upgrade procedure?
    c) Does it come with a rollback mechanism? It would be really helpful to rollback to the previous working version!
    d) Is there any individual log mechanism for each plugin upgrade? It can be helpful to keep an eye in the whole procedure in case something goes wrong or should I look in my log files as a standard procedure?


  9. DJ Johnny Medley

    “Didn’t feel a thing.” Thank you!!!


  10. A in LA

    Auto-updates often result in crashing due to caching. Is there a way for the auto-update to disable caching during the processing of any updating?


    • David Anderson

      (Apologies to the moderators – I accidentally clicked on “Report” instead of “Reply” at first – there’s no way to cancel that!).

      Very possibly your caches are due to PHP opcode caching. Happily WP 5.5 now includes a call to tell the opcode to flush upon a plugin update, so we should all see much less of those particular fatal errors.


  11. Brian

    I just updated to 5.5 today. Thank you to the all the WP contributors for continually to improve and advance the best platform.


  12. Dennis

    Auto updates are ideal for small blogs. But if you run a large website with lots of custom scripts then you have to be sure of compatibility before updating any plugin. The good news is that you can disable auto update.


  13. Peter

    Lazy loading images sound good, for sure it was highest time.

    And the first thing i really like ever since Gutenberg project has started is the Block Patterns tab. Actually i never thought there will be anything i like in GB!


Comments are closed.

%d bloggers like this: