Closed (fixed)
Project:
jQuery Update
Version:
7.x-2.3
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
24 Aug 2012 at 00:19 UTC
Updated:
22 Apr 2013 at 20:10 UTC
I'm running the latest dev version with jQuery 1.7.
If you begin to add a new field, select the 'Field' type, which then usually makes the 'Widget' field available for select. However it stays as 'disabled' and I can't select a value for it.
I selected jQuery V1.5 instead, and it works perfectly.
Comments
Comment #1
paw-e-l commentedI needed v1.7 only on the front of the website so i hardcoded v1.5 for the backend ;)
line 79 of the jquery_update.module
replace:
with:
Comment #2
sylus commentedOn latest dev of CTools and Views I don't see this issue present itself anymore. Can you verify?
Comment #3
neilhanvey commentedThis is no longer an issue with the latest version of jquery update. I had the same problem but the update fixed it (although it did produce other errors related to clearing caches)
Comment #4
eiriksm#1:
You don't need to hack the module. And you should not hack the module (Are you sure you will remember to update it when you update jq update?)
Anyway. here is my solution:
Create a custom module (or use one you already have). Then just do as follows:
Instant win, and no hacks needed.
Comment #5
ressaThanks @eiriksm, spot on solution! I couldn't make it work though, so I entered
debug($trueversion, '');in the jquery_update.module line 185, right after$javascript['jquery']['version'] = $trueversion;. The function was called twice on admin pages:...leaving 1.8.2 as the used version on admin pages.
So I changed the weight of my own module using the code from this page http://drupal.org/node/110238:
And the order is now reversed on admin pages, so version 1.5 is used:
After reading this I changed the path check in your module to this:
I hope this solution will be committed at some point, so we don't have to add an extra module in the first place: Allow different version for administrative pages
Comment #6
ericduran commentedThis is already fixed in the latest dev version.