I have a strange problem that is causing a huge headache here.

When I edit a context, clicking any of the condition or reaction links causes no reaction from the browser (other than the link rollover turning black). I also cannot add blocks to any region as the add button does not appear to react when I click it. The X link does not remove a block either.

I have another commons install running on the same server and within context the lists down the right hand side appear correctly when I click a condition or reaction and I am able to add / remove blocks at will.

I have compared module versions for various modules between the two sites and I appear to be running the same versions across both sites.

I have tried various browsers but with exactly the same reaction.

I've considered upgrading to v 3 of context but have been warned off that here: http://drupal.org/node/914398

It looks like a similar issue was being reported here: http://drupal.org/node/878816

I am not getting any errors within Watchdog but I'm guessing that this is a front-end problem so I'm not too surprised about that. When using firebug on firefox 3.6.12 I receive no console errors when clicking on the links from within a context editing screen. However when I F5 the screen I get a whole bunch of warnings (which I detail in the attached file).

Versions:
Acquia Commons beta 1 (with context/panels modules installed as part of the commons feature)
ctools 6.x-1.8 (upgraded from default commons install but it's the same version as I have working on the other site)
jquery 6.x-1.4 (upgraded from default commons install but it's the same version as I have working on the other site)

My front end scripting knowledge is weak but if anyone can give me a nudge as to what could be the issue, I'd appreciate it and do some further investigation and report back.

Thanks,
Crom

CommentFileSizeAuthor
firebug_console_warnings.zip1.92 KBCrom

Comments

Crom’s picture

Crom commented
Status: Active » Closed (works as designed)

Having done some digging I've discovered that the incompatible module is jquery update 6.x-2.x-dev.

See here for more details: drupal.org/node/984524.

I have closed this issue but hopefully this will help others in the same position.

Crom

lelizondo’s picture

lelizondo commented
Title: Cannot edit conditions, reactions or add/remove blocks within context editing screen. » Cannot edit conditions, reactions or add/remove blocks within context editing screen using Jquey Update 2.x-dev
Status: Closed (works as designed) » Active

Some users claim this is a problem with context and not with jquery update, so let's keep this issue open for a few days

steven jones’s picture

steven jones commented
Title: Cannot edit conditions, reactions or add/remove blocks within context editing screen using Jquey Update 2.x-dev » Conflict between context admin UI and JQuery Update 2.x-dev
steven jones’s picture

steven jones commented
Status: Active » Closed (duplicate)

Strongly suspect this was a duplicate of #1004094: Badly performing CSS selector

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

Error could be caused by another module, e.g. #510012: Not compatible with Jquery Update -- Breaks node edit page!.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Version: 6.x-2.0 » 6.x-3.0
Status: Closed (duplicate) » Active

I still see this happening in 3.x in Open Atrium when jquery_update 2.x is enabled.

univate’s picture

univate commented

I am experiences a similar issue with jquery_update and context editor not wanting to work properly together. Everything works fine when you go back to the default drupal version of jquery.

It allows you to drag& drop blocks between regions, but it just doesn't allow new blocks to added.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented
Status: Active » Closed (works as designed)

See comment #5. If you're getting this error message, this is not a bug in context.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented
Status: Closed (works as designed) » Active

@nedjo, as far as I can tell, this isn't related to the issue you link in #5. For one, I'm not running that module, but secondly, there is no JS error thrown, so if anything, this is related to the issue linked in #4, being a simple selector that no longer works in more recent versions of jQuery.

univate’s picture

univate commented

@nedjo can you confirm you are running current jquery_update-2.x and context-3.x and have tested the context inline page editor?

I tried installing the specific module you mentioned and there is no difference, I'm still experiencing the same results with or without that module. The context ui will allow move items between regions but I can not add new blocks - maybe something to do with the ajax that retrieved the blocks?

I assume there something related to the change in jquery version similar to the issue: #1004094: Badly performing CSS selector although that file no longer exists in 3.x so can not be the cause.

I will continue to investigate, at this stage I feel the most likely cause is in the context_ui javascript code.

nedjo’s picture

nedjo
he/him/his
Primary language English
commented

My bad, please ignore my post #8, I was misremembering and confusing this issue with #984524: Jquery Update 2.x breaks Context UI.

univate’s picture

univate commented
Status: Active » Needs review

Ok, I seem to be having some success fixing this by upgraded to jquery.ui 1.7

So my modules/library configuration is as follows:
context_ui-3.x
jquery_update-2.x
jquery_ui-1.4 (with library - jquery.ui 1.7.3)

@jhedstrom would be interested if this fixes the problem for you, although I should add that I am not using open atrium with this.

jhedstrom’s picture

jhedstrom
Primary language English
Location Portland, OR
commented

@univate Confirmed. jquery.ui 1.7.3, combined with jquery_update 2.x resolves this issue.

Perhaps a patch to the README, or an update to the module page would help others who stumble across this issue.

oliver huynh’s picture

oliver huynh commented

confirmed #12. Thank bro!

soulfroys’s picture

soulfroys
Primary language Portuguese, Brazil
commented

Confirming #12, upgraded to jquery.ui 1.7.3 and... success!

beanjammin’s picture

beanjammin commented

Adding a note that context-6.x-3.2 introduced a new permission (context ajax block access) that produces similar behaviour to what is described in this issue for users that do not have the context ajax block access permission (blocks can be moved and deleted, but not added). Adding the permission fixes the issue.

paulocs’s picture

paulocs
Primary language Portuguese, Brazil
Location Belo Horizonte
commented

As #12 solves the problem and context 6.x is no longer supported, I'll close this issue. Thanks.

paulocs’s picture

paulocs
Primary language Portuguese, Brazil
Location Belo Horizonte
commented
Status: Needs review » Fixed
paulocs’s picture

paulocs
Primary language Portuguese, Brazil
Location Belo Horizonte
commented
Status: Fixed » Closed (fixed)