Closed (won't fix)
Project:
jQuery Update
Version:
7.x-2.3
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
15 Jun 2011 at 17:00 UTC
Updated:
8 Mar 2017 at 16:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
kinnel commentedOOPS, I mean
Comment #2
tnfno commentedYour first post was better, but the value returned is not 0, it is FALSE. I got it to work with:
if (!empty($variables['scripts']) && !strpos($_SERVER['REQUEST_URI'],'/admin/')) {Comment #3
andreap commentedtnfno, your solution is working correctly?
Comment #4
cprouvot commentedI had exactly the same issue on Drupal 7. With jQuery 1.8, the Views module was crash.
I work with the actual stable released of jQuery Update (7.x-2.3) and i had this in the line 69 of the jquery_update.module :
I think this issue is in relation with another issue in the Views issue queue #1869988
Comment #5
damienmckennaHow about a patch like this? It provides two options that let you disable the new jQuery version on either admin or node-add/edit pages. Using this patch allowed Views v3 to work on my site.
Comment #6
superspring commentedSame patch for D7
Comment #7
berliner commentedAlso consider #1969244: Specify jQuery version per theme which would allow theme specific jQuery versions, tackling quite some problems that result from a conceptual mixup between admin pages and admin theme.
Comment #8
markhalliwellThe 7.x-3.x branch removed the concept of the "admin jQuery version/paths" and replaced it with #1969244: Specify jQuery version per theme.
The 7.x-2.x branch will no longer be maintained or have patches applied to it.