Closed (fixed)
Project:
Context
Version:
7.x-3.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 May 2013 at 17:14 UTC
Updated:
8 Nov 2013 at 18:30 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
h3rj4n commentedI can't reproduce this. I've got the same problem on a site but I havent got to the bottom of that. I'm not sure if that site uses jQuery Update. To try to reproduce this I installed the following:
I disabled the following:
I set the jQuery Update module to use 1.8 (production) from Google. When I try to modify / add a context it gives me all the options there are. I'm getting the forms as it should be. Do you have any other modules that could break this?
I'll try to search for the site that has the same problem as yours, see what goes wrong there.
Comment #2
jamesposko commentedJust ran into the same bug in context after installing jQuery Update module.
Context was working fine with:
Drupal 7.19
- jQuery Version 1.4.4 (default drupal package)
Context 7.x-3.0-beta6
then installed jQuery Update 7.x-2.3.
Set a jQuery Update configuration of:
jQuery Version - 1.8
jQuery compression level - Production (minified)
jQuery and jQuery UI CDN - jQuery
then context would not display any conditions or reactions added with in a set context. So, went back to the jQuery Update configuration and switched the jQuery version to use 1.7 and context works as expected.
Discovered on:
Mac OS X - 10.7.5
FireFox - 20.0
Chrome - 26.0.1410.65
Comment #3
loopy1492 commentedThe same thing happened to me.
jQuery Version - 1.8
jQuery compression level - Production (minified)
jQuery and jQuery UI CDN - jQuery OR None selected
Switching to jQuery Version 1.7 fixes it. I'm pretty sure that'll be okay for now. I don't think anything actually hinges on using 1.8.
Comment #4
loopy1492 commentedI guess it would also help to give you the javascript error from the Chrome console.
Uncaught Error: Syntax error, unrecognized expression: #:input[name="conditions[plugins][date_context_date_condition][options][operation]"]
Comment #5
justluvgod commentedSame here will work with jquery 1.7, but 1.8 will not work.
Jquery version 1.8 (breaks), 1.7(works fine)
Drupal 7.21
JQuery update 2.3
jQuery compression level - Production (minified)
jQuery and jQuery UI CDN - jQuery OR None selected
Comment #6
hefox commentedwith repetitive people experiencing it, doesn't sound like postponed issue
Comment #7
sabinemae commentedI had the same problem and in my case it was a conflict with the DHTML module. When I switch it on I cannot use the context module any more, whereas when I switch it off the context module works fine.
I used this version of it: dhtml_menu-7.x-1.0-beta1.tar.gz 24 KB 6b14c80e5ea1b167d3bfb40f780e4e1a.
I will post this also on the issues queue of the DHTML menu, which is currently being used by 28583 sites.
Comment #8
sabinemae commentedI actually just uninstalled and reinstalled DHTML menu and the problem disappeared. So I do not know what went wrong with the first version of the DHTML module, since it is actually the same version that I reinstalled.
Comment #9
sabinemae commentedI thought it was fixed but the problem reappeared after I went to the modules settings page and turned on:
static navigation: Expand on Bullet: All links will continue to function as static links. To expand an item, click the bullet icon next to the link.
I attach the screenshot of my settings-page.
Comment #10
sabinemae commentedThe dev version of DHTML module does not have this problem and works fine with the context module:
dhtml_menu-7.x-1.x-dev.tar.gz 16.48 KB d5fad330b0b1fa74d5a45b997df90317
Comment #11
hefox commentedCrossreferncing #1951588: jQuery 1.8+ Breaks Core JavaScript which breaks context_ui_dialogue.js
Comment #12
hefox commentedRe-open this is still an issue with jquery_update 7.x-2.x-dev. My guess is there error is due to the mismatch in jquery ui and jquery versions that current stable has.
edit: wrong status, should be won't fix or such, but this allows those subscribed to see. there has NOT been any commits for this