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.
I am not sure if this is a good idea, but my main reason of using JQuery Update is front end, not drupal admin, not sure about others.
Comment | File | Size | Author |
---|---|---|---|
#8 | 1766240-path-based-update.patch | 2.41 KB | muka |
Comments
Comment #1
PI_Ron CreditAttribution: PI_Ron commented+1
Is it possible to only perform jQuery update to the front end?
Comment #2
RobW CreditAttribution: RobW commentedThis would amount to jQuery Update settings per theme. On sites that don't use Drupal's built in jQuery UI and ajax features, replacing with the latest jQuery on the front end theme could be nice. There would be a performance hit for site owners/ authenticated users though, having to download two versions of jQuery. Couldn't hurt as an option though.
Comment #3
gagarine CreditAttribution: gagarine commentedGreat idea. This has to be an option.
Comment #4
gagarine CreditAttribution: gagarine commentedA workaround
Comment #5
cpliakas CreditAttribution: cpliakas commentedgagarine,
Cool technique! Works well for me.
Thanks for sharing,
Chris
Comment #6
gagarine CreditAttribution: gagarine commentedcpliakas, I toke the time to write a blog post about http://antistatique.net/blog/2013/01/04/drupal-use-a-different-jquerys-v... hop that's help some peoples.
Comment #7
drupal_jon CreditAttribution: drupal_jon commentedCool, thanks gagarine, this works for me.
Comment #8
muka CreditAttribution: muka commentedHi, I'm using this to allow block-like path selection for replacement
Comment #9
willvincent CreditAttribution: willvincent commentedUpdating status
Note: The patch in #8 works for me
Comment #10
Albert Volkman CreditAttribution: Albert Volkman commentedMarking this as a duplicate of #1524944: Allow different version for administrative pages
Comment #11
DamienMcKennaI've pushed #1524944: Allow different version for administrative pages back to Needs Work so the path functionality from this issue can be merged into it.
Comment #12
marcvangendThe workaround in #4 works pretty good for me, but we ran into fatal errors when deploying this to the test server combined with features and drush -fra, because the hooks were invoked before jquery_update was enabled. Here is an improved version of the workaround which prevents that problem with module_exists('jquery_update').
Comment #13
geetotes CreditAttribution: geetotes commented@muka Thanks for the patch! The workaround posted in #12 did not work for me
Comment #14
allvintage CreditAttribution: allvintage commentedworkaround in #12 works great, but only if placed in a custom module, not in template.php
Comment #15
kris digital CreditAttribution: kris digital commented@muka Thank you for the patch! works!