Active
Project:
Context
Version:
6.x-3.0
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
26 Aug 2010 at 14:10 UTC
Updated:
4 Nov 2010 at 20:41 UTC
Jump to comment: Most recent file
Comments
Comment #1
auberdjinn commentedI think the only way to do this is to define a new condition in a plugin. At least I hope it is because that's what I've just done. I've created a custom module to do this for the site I'm working on and have attached it. Maybe you could give it a go and if it works for you I could work it up into a proper module or a patch for Context, whichever is more appropriate.
I may well have done this horribly - have just muddled through to work out how to put a plugin together. But it's a start!
Comment #2
auberdjinn commentedOops, sorry, named the file properly this time!
Comment #3
bkosborneAhh I'll check it out this weekend. It would be great to get this integrated with the menu condition though.
If I can assign a context to a menu "level", it would be so great. Most of the sites I build out have primary, secondary, and tertiary page templates.
Comment #4
jumpfightgo commentedThis won't solve every use case, but another option is to use the cep_immediate_taxonomy_child module of the "Context Extras" module, which lets you select terms whose children activate the context.
http://drupal.org/project/context_extras