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.Attached is a patch that lets you specify the paths where you don't want jQuery Update script to be added (we had problem with jquery update for specific sections of the site or specific pages in the site). You can specify a list of paths (like node/add/blog or admin/*) in the administration page of jquery update.
| Comment | File | Size | Author |
|---|---|---|---|
| jquery_update.patch | 1.55 KB | ifuyivara | |
Comments
Comment #1
TravisCarden CreditAttribution: TravisCarden commentedThis would be valuable functionality indeed! I just spent way too long figuring out how to conditionally suppress jQuery Update from a custom module. Why don't we bump this up to 7.x where it's likely to get a little more love?
A thought on approach: Path surely isn't the only criterion people might like to test against. What about content type? or active theme? I could see this being used much like block visibility settings. Perhaps it should have similar configuration options. Or perhaps the setting should be exposed such that it could be toggled with Context, Rules, or in a custom module.
Comment #2
RobLoachContext would be the perfect thing for this.
Comment #3
caspervoogt CreditAttribution: caspervoogt commentedhear hear. Context support would be awesome. On pages with multiple QuickTabs or Views Slideshows, you can sometimes run into issues using some versions of jQuery, and it would be handy to be able to set a different version based on path or some other context.
Comment #4
joelwallis CreditAttribution: joelwallis commentedSo, how's going with the Context integration? I'm interested in contribute to it. In fact, I was already working on it when I stumbled upon that issue.
Anyone else working on it?
Comment #5
markhalliwellI don't think this is going to happen. Closing in favor of another idea that has more merit.