14 Comments

  1. Bjarne
    · Reply

    It continues to impress me how informative wptavern.com is. Thank you :)

    Report

  2. Scott Sawyer
    · Reply

    This is going to be a huge problem for many sites for many years to come (my prediction). There are so many WP sites made by a plugin jockey with commercial plugins and themes, the owner has no idea how to update or maintain. When the site starts breaking, they will get mad at WordPress, and move to Squarespace or something else they won’t have to worry about. Less jobs for developers.

    I don’t onow what the long term answer is, maybe WP should never have bundled jQuery, maybe the updater should be able to check for compatibility and require the correct version of jQuery. But this sudden change in WP from never breaking backwards compatibility to breaking every other update is not a good look.

    This is why i rarely use commercial plugins on customer sites and keep everyrging in git, disabling auto updates.

    Report

    • Rod Olman
      · Reply

      I’ve also found that completely disabling updates (including the updater code in the source) is the only way to go. This prevents autoupdates to alpha versions, breaking changes, new editors, etc etc etc.

      WordPress is no longer a CMS I control, but one that keeps giving me headaches and tons of support calls from clients wondering what happened to the normal Word interface editor that they’ve been using for decades.

      Report

      • arkay
        · Reply

        You have one side where people complain about WP being insecure and outdated. Then you have the other side where when WP makes any sort of move, even when they plan it months/years in advance – it falls on deaf ears.

        You can’t tell me with a straight face that the internet and internet browsing has remained the same in the past 5 years. There’s so much behind the scenes that has evolved.

        If you want a site that doesn’t change for a decade, tell your clients to stick with vanilla HTML circa 2009 that supports Internet Explore 9. The rest of the internet wants to move on. And we’re going to move on without them.

        Report

  3. Peter Shaw
    · Reply

    A better move would be to just transition away from jquery. It really is not required these days.

    All the complex functionality could be ported to react and all the simple functionality should be vanilla javascript.

    Report

    • Denis Zoljom
      · Reply

      There is an initiative to move all core jQuery to vanilla JS if I recall correctly, but that’s a massive undertaking.

      Not to mention all the backbone.js code that is scattered around…

      Report

    • Arkay
      · Reply

      The challenge is a lot of legacy code within plugins/themes that rely on jQuery. For example – in my company, much of our animations still run on jQuery itself. There’s nothing wrong with it, and it’s a quick fix to simply call the jQuery library within the theme.

      But all the small business WP users who are managing their pizza site off a 2017 WP theme that uses jQuery can’t get that dev support at all. And that’s the internal struggle the WP core team is having.

      Now that I think about it – maybe it is something like a basic plugin that calls the jQuery library, so WP Core can migrate out to vanilla JS — while the plugin is what supports the legacy owners.

      Report

  4. Ilya Kyselov
    · Reply

    I think this is good news for the jQuery update. To be honest, I have repeatedly encountered situations when plugins do not work correctly, and the developers simply do not have time to update them in time))

    Report

  5. Mohamed Rinaz
    · Reply

    WordPress 5.5 brought down my entire network. Still trying to recover from the issue. Hope same thing will not be repeated in 5.7.

    Report

  6. Joseph McMurry
    · Reply

    200,000 sites are using the “Enable jQuery Migrate Helper” plugin and I imagine many of those will break on upgrading to WordPress 5.6. I hope someone releases a plugin that allows using jQuery 1.x on WP 5.6.

    Report

    • Marius Jensen
      · Reply

      Hiya,

      The numbers are heavily skewed because others recommended the migrate helper plugin as a fix for an unrelated issue between concatenated (merged) scripts and localized scripts.

      But the team is looking at adjusting the plugin to account for users who may end up with lost functionality due to abandoned plugins and themes, while also trying to nudge them in the direction of using maintained software.

      Report

      • Joseph McMurry
        · Reply

        Thanks for the reply Marius. Great work on Enable jQuery Migrate Helper too!

        I wonder how many abandoned WordPress or still have broken sites after the WP 5.5 update.

        I certainly understand that jQuery needs to be updated in core, but a solution for older sites to keep running would be nice :)

        Report

  7. Bertil Wennergren
    · Reply

    jQuery UI?? It’s stone dead. How can they still be using it? That’s just crazy.

    Report

  8. Michael
    · Reply

    At the moment i have 5.7-alpha-49645 installed and i see a LOT of migrate notices on WordPress core.js, iris.js (colorpicker) etc. Is there any information on when they plan to also migrate the core itself to make it compatible with the most recent jQuery version without jQuery.migrate?

    I found it hard to debug / migrate your own code if you always have like 20 notices from the WordPress core in your console.

    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: