Menuperformance conflicts with context. When menuperformance is activated, in context the condition "menu" shows --none--. When we deactivate menuperfomance, everything is back to normal. For now, the only workaroud is to deactivate menuperformance in admin/config/user-interface/menuperformance when we want to edit a context with the menu condition.

Using context-7.x-3.0-beta4.

CommentFileSizeAuthor
conflict_context_menuperformance.png19.57 KBletrotteur

Comments

firebird’s picture

firebird commented

I'll have a look at this when I get the chance, possibly next week.

firebird’s picture

firebird commented

Do you need multiple selections in the menu condition? The widget that Menuperformance offers currently only support single selections. I'm already working on getting that to work, but if you need multiple selections, I'll also need to build a new selection widget.

I could also see if I could disable Menuperformance just for the menu condition selection. I'd prefer some other solution, though, since if the menus are huge, the original menu item selectors won't work in the menu condition form.

letrotteur’s picture

letrotteur commented

I would need multiple selections in the menu condition.

Disabling Menuperformance, or allowing to do so for context could be an alternative in the mean time.

Would be willing to try any patch/improvement that you come up with. We've got a project with huge menus and your module saved a lot of scrolling time.

firebird’s picture

firebird commented

This isn't easy at all to fix on Menuperformance's side. The problem is that Context calls menu_parent_options() directly, so hooking the call is difficult.

Luckily, some people have run in the same problem, and they have a patch for Context that improves performance, see this thread: http://drupal.org/node/873936 .

It's still not compatible with Menuperformance, but I'll see if that could be changed; I've posted a comment in the other thread.

caschbre’s picture

caschbre commented

I've run into this issue as well with Context conflicts. My current project can probably work around this for the time being but I've had previous projects that relied heavily on Context and the Menu condition.

I'd also be interested in a multi-section widget.

steinmb’s picture

steinmb commented
Title: Conflict with context » Conflict with context module
Version: 7.x-1.0-beta3 » 7.x-1.x-dev

Confirm that this still is an issue. #873936: Context UI very slow needs reviewers. Let's head over there and help out.