Looks like, the latest version is calling the old 3.6.1, which is 404 indeed:
public_html/wp-content/plugins/jquery-updater/jquery-updater.php: wp_register_script( 'jquery-core', plugins_url( '/js/jquery-3.6.1.min.js',FILE ), [], $ver_core );
I had the hosting site revert back to 3.6.1 so these features would go back to working status.
This seems to be affecting alot of our websites too. Nightmare.
Also here, I needed to deactivate the plugin and insert the jQuery version manually in the Header of my site.
Every update is a headache =(
Hey @feriato , doing the above fixed your issues with 3.6.2 update?
i have the same problem but with search bar and i get a alot of console error
Yes, this is the 2nd time I have seen this developer make this mistake when publishing an update. We have turned auto-updates off for this plugin as the quality control seems non-existent. The one job this plugin has is to load the latest version of JQuery, but sometimes they pull the new query file, but try to link to the old ones. This last auto update killed an entire day for us fixing sites.
A quick fix is to go into the plugin folder and duplicate the file being called ad rename as 3.6.1, this way you actually get the new 3.6.2. Then you can turn off auto-updates and just use this plugin to track when jquery changes, and you can update manually and test.,
Hi @kraftig
Yes, after that my custom jQuery files start working well. Look at Replaced the default WordPress jQuery with Google Library
Hi All,
There is a fixed new version available (3.6.2.1), but somehow doesn’t yet show up as an update in the updates page. The issue has been resolved in this new version. You might need to forcibly update it with wp-cli to v3.6.2.1.
See the diff (and new updated version) here:
https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=2835158%40jquery-updater&old=2833955%40jquery-updater&sfp_email=&sfph_mail=
But I need to be honest: this should have never happened! Updating the plugin to a newer version of jQuery without actually updating jQuery, and not testing the plugin before pushing an update is absolutely unacceptable for a plugin with 40k+ active installs.
One just cannot do this in between work and dinner without testing this properly. My advise for the dev would be: get proper testing procedures in place.
I am strongly considering forking the plugin and update it myself in order to prevent my sites from getting broken by a sloppy action of a plugin developer.
you are right, and I’m aware of it. i did mess up that release
i was short on time, pushed a version with a type causing this issue
