1. Jim Casey

    I don’t know if I need this plugin or not but it might correct a rough spot I’ve noticed lately.

    More to the point, I downloaded it just now to my cell happily knowing I can more easily upload the zip file to my site later because of those belated changes. 🙂


  2. Rod Olman

    I guess this is one of the steps to permanently killing the Classic Editor. One more nail in the WordPress coffin (why use WP when one can already use Wix or Squarespace without having to put up with an alpha version page builder?).


  3. Bjarne Oldrup

    A shoutout to jQuery Manager which allows your site to include a newer and safer version of jQuery along with jQuery manager should you need that.

    And may I suggest, that all of us who identify issues with old jQuery version dependencies, get in touch with theme and plugin developers, revealing the issue to them. During my personal WP 5.5 release candidate tests, I encountered unusually many issues, and every single developer I have been in touch with, expressed an interest in fixing any issues before release, so that poor experiences with core updates can be avoided.

    Take care


    • Rob Marlbrough

      Excellent idea – the problem is, there are so many plugins and themes that are no longer supported and the developers have ghosted, that end-users have no idea what to do now… rebuild their entire site? Never update WordPress again, after learning their lesson? I hope not. A new industry of recoding old plugin/theme’s Javascript files will be born, and perhaps that’s what’s needed to keep WordPress up to date – users need to understand their plugins and themes should be updated regularly, and if updates are no longer available, recoding the outdated code is vital, whether it be jQuery, PHP, or mysql() calls.


  4. Sam

    Congratulations to the WordPress team for another successful plugin after the Classic Editor.

    They’re on a roll!


    • Otto

      Even developers have agreed that this step needed to happen. The jQuery library is years and years past the code still included in WordPress. Breakage was inevitable and necessary.

      The plugin makes the old code work, and gives admin notices telling you which plugins need to be updated or replaced. If you’re using old and outdated code, then stop doing that.


      • Peter Shaw

        “Even developers”?

        Most I know have been calling for this for ages.


      • Rob Marlbrough

        I agree it’s a much needed step forward, but in my opinion the warnings (this plugin) should have been added to core first, and give people time before just removing jQuery Migrate and breaking their sites – most end users are non-technical and have no idea what broke or how to fix it, and it tarnishes the reputation of WordPress along the way. I am not sure how it makes sense to remove it first.

        Perhaps core could have detected deprecated code, and offered a warning to update plugins etc, and show an option to enable jQuery Migrate again, with a constant warning “jQuery Migrate Helper is installed – you have plugins that need to be updated”, and clicking on the link expands to show a list of the plugins or theme.

        The major issue isn’t developers that ignored all the announcements made about it being removed, it’s about the vast number of outdated plugins and themes that are no longer actively maintained, and the developers have ghosted on end users. I am now hunting down old JS code across hundreds of websites, developing patches and search/replace scripts [find .live() and replacing with .on()] etc. Many of these clients pay for quality maintenance and security, and I treat these websites like they are my own, so I’ll ensure they are patched if no updates are available, and no replacements easily implemented.

        Sadly, I’m also seeing lots of very popular plugins like Restrict Content Pro using old jQuery libraries and causing warnings (not sure if these are site-breaking issues yet) with their latest just-released versions.

        With the pain comes progress, and this will blow over, but warnings for users first before making breaking changes like this should be a priority. These jQuery Migrate removal changes aren’t even mentioned in the 5.5 field guide at all!


  5. David Anderson

    Ordinary site owners would have been helped by first merging some code that would make it easy for them to identify out-of-date plugins/themes. i.e. Ones that haven’t been updated for a long time and have no updates apparently available. Such code will always be the major area of risk when upgrading.


  6. Herb Miller

    After updating to WordPress 5.5 I had a number of problems which jQuery Migrate “fixed”. But I dug deeper and found lots of problems when the only activated plugins were Gutenberg 8.7.1 and Yoast SEO. I then discovered the WordPress core bugs that had been raised, and for which a fix was being developed. After applying the fix I noted I didn’t actually need the jQuery Migrate Helper. Perhaps others have had similar experiences to those I documented here: https://herbmiller.me/how-to-survive-wordpress-5-5s-removal-of-jquery-migrate/


  7. Sam Petrick

    I completely agree with this jquery migrate helper plugin, It’s not for non-technical users they don’t know how to fix.


Comments are closed.

%d bloggers like this: