Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
When I upgraded to 2.4 at least two bugs appeared (these are the problems, which are immediately visible, maybe there are others):
- When checking for module updates only the upper part of the page is shown with usual admin menus and the title. Nothing more
- I use "module filter". After the update all filtes on the left and on top have disappeared. There is no dependency to JQuery
I verified this by restore my previous installation and apply again the update of jquery update
Comments
Comment #1
carlodimartino CreditAttribution: carlodimartino commentedYes I'm having the same problem. Administration Menu search and shortcuts toolbar also no longer work.
Comment #2
reptilex CreditAttribution: reptilex commentedIt also creates problems with the wysiwyg module (I have it with CKEDITOR installed).
Comment #3
burmfilip CreditAttribution: burmfilip commentedI have experienced the following problems after updating the jquery_update module to version 2.4:
- the functionality to check manually for updates is no longer working
- unwanted lay out modifications in the design of websites
- image slide shows are no longer working
- image lightbox effect is no longer working
All suggestions for fixes are more than welcome.
Filip
Comment #4
Nicolas Bouteille CreditAttribution: Nicolas Bouteille commentedI just installed 2.4 too and I got the same weird behaviors. Looks like a cascading failure causing a lot of JS to break. Looks critical to me.
Comment #5
beauregard CreditAttribution: beauregard commentedYes, I also don't understand why the maintainers do not look at this bug. Obviously it causes massive problems. I will deinstall this module.
Comment #6
reallyordinary CreditAttribution: reallyordinary commentedJust chiming in - yeah, upgraded to 2.4 and it broke the Views admin interface. Ajax is now breaking intermittently for no discernible reason.
Comment #7
reptilex CreditAttribution: reptilex commentedIs this issue so rare or how come a critical issue like this is not even commented on by the maintainers?
Comment #8
dude74 CreditAttribution: dude74 commentedMy upgrade to 2.4 broke rules autocomplete and panels display choice. I'm back to 2.3, too much criticals
Comment #9
bradweikel CreditAttribution: bradweikel commentedA workaround for some of these issues:
Go to your site's jquery_update settings page (admin/config/development/jquery_update) and set the default version to 1.5
Comment #10
joeebel CreditAttribution: joeebel commentedThank you bradweikel!! That fixed it for me. I couldn't check updates the manual way until I set default version to 1.5.
Thanks again!!
Comment #11
ecvandenberg CreditAttribution: ecvandenberg commentedAs stated in #9 setting jquery version to 1.5 helped to get CKeditor working again. All other versions did not.
But I have a site with https://drupal.org/project/equalheights and https://drupal.org/project/responsive_menus which requires jquery version 1.7 or higher.
So I boldly tried with version 1.7 and CKeditor worked fine. In fact it worked with all jquery versions.
Strange...
Comment #12
dude74 CreditAttribution: dude74 commentedI try to debug and to help. I test on a fresh kickstart install, with jquery 1.8
(working with 1.5 version, but I won't upgrade a module to "downgrade" the jquery version, currently 1.8 working with old modules)
rules - any action or condition - "data selector broke "
console report :
Uncaught TypeError: Cannot set property '_renderItem' of undefined rules.autocomplete.js?n4zus5:108
Drupal.rules.autocomplete rules.autocomplete.js?n4zus5:108
(anonymous function) rules.autocomplete.js?n4zus5:12
p.extend.each jquery.min.js?v=1.8.2:2
p.fn.p.each jquery.min.js?v=1.8.2:2
$.fn.once jquery.once.js?v=1.2:55
Drupal.behaviors.rules_autocomplete.attach rules.autocomplete.js?n4zus5:10
(anonymous function) drupal.js?n4zus5:76
p.extend.each jquery.min.js?v=1.8.2:2
Drupal.attachBehaviors drupal.js?n4zus5:74
(anonymous function) drupal.js?n4zus5:412
k jquery.min.js?v=1.8.2:2
l.fireWith jquery.min.js?v=1.8.2:2
p.extend.ready jquery.min.js?v=1.8.2:2
D
Hope that will help developpers
Comment #13
memcinto CreditAttribution: memcinto commentedDitto for #9 and #11 -- this update broke Wysiwyg on one of my sites; setting jquery to 1.5 fixed it.
Comment #14
paean99 CreditAttribution: paean99 commentedModule filter seams to works with 1.8 admin. Admin menu do not appear with 1.5 admin.
Comment #15
old_dog CreditAttribution: old_dog commentedInterferes with operation of the Marinelli 7.x-3.0-beta11 theme.
Also prevents set-up of contexts in new Page Manager pages.
Simply disabling module restores normal operation.
Comment #16
Rhino-new CreditAttribution: Rhino-new commentedBradweikel you are my hero. the admin/config/development/jquery_update reset trick turned my site from an image-less mess into the functioning websit it was before. Thank you so much for sharing.
Comment #17
BDaggerhart CreditAttribution: BDaggerhart commentedJust chiming in on this, though it doesn't seem like a lot of effort is being put into fixing it. I also had my site broken when I updated, and used the "fix" described above of setting my jquery default to 1.5. Hopefully there will be a better fix for this eventually.
Comment #18
ontoligent CreditAttribution: ontoligent commentedJust to confirm what others are finding, I installed 2.4 and many things on my site stopped working, including module filter, admin, and various other things. Does anyone know if it's the jquery itself that is incompatible or if there is something in the module that is causing these problems?
Comment #19
MattBridger777 CreditAttribution: MattBridger777 commentedI have recently experienced this. Upgrading to 2.4 caused Ajax to cease responding. I am in a pickle however due to the site requiring jQuery 1.9 for its myriad of slideshows to operate. Setting the Default jQuery Version and the Alternate jQuery version for administrative pages to different versions has no effect for me, Ajax just continues not to respond.
I have tried every combination of the options available and nothing yields joy.
To add insult to injury, the site I'm building also requires Responsive, which causes its own problems with making the CMS unresponsive (ironically enough) which I require jQuery Update to counteract.
Help please.
~Matt Bridger
Comment #20
markhalliwellI have updated the release notes of jquery_update 7.x-2.4 to reflect the change that occurred and the solution to fix it:
Comment #21
beauregard CreditAttribution: beauregard commentedHi Mark
thanks for the update. I would like to add one comment: Not every drupal user is a technical expert, some have some IT background and use Drupal as CMS (like me). So, when I update a module, then my assumption is, that it works, or at least it is very basically tested.
As I understand from your comment, for you it is very logical that a new version might break several other modules. From technical point of view you are correct. From user point of view, it is not really user-friendly. When I update for example MS Word, then I expect that MS Excel is still working. I would like to propose that it would be much better to keep the current version when an update is done and the new jquery version must be set by the user. A comment during update and/or the module page would be helpful. What do you think?
best regards
Comment #22
markhalliwellThat is what I did:
I agree this kind of change should have either 1) introduced an update hook that detected whether the variable was set and, if not, set it to the previous default so it didn't break anything or 2) bump the major version which is indicative that it would break existing installs (which is what major version bumps are for).
However, I only recently joined the jquery_update team and wasn't involved in the release of 7.x-2.4. The only thing I can do is help mitigate the damage by pointing people to where the changes were made and how to easily fix them.
That being said this kind of change, in all reality, is not that big of a deal. All one has to do is set the version of jQuery their site needs. It is a very, very simple fix.
Comment #23
beauregard CreditAttribution: beauregard commentedHi, thanks for your follow-up- Certainly, the instructions you provided are easy and for this case the problem is fixed. My comment was meant for future updates.
Comment #24
sanj CreditAttribution: sanj commentedeverybody talk about upgrading Jquery, but no one provide links to older versions of Jquery. upgrades are like hells
Comment #25
StephenRobinson CreditAttribution: StephenRobinson commentedAdministration Menu - admin_devel.js breaks jquery.once, has a jQuery.extend call that causes the issues, see https://www.drupal.org/node/2404661 with default jquery 1.4.4
Comment #26
canardesign CreditAttribution: canardesign commented#9 did the trick, thank you !