Just out of interest (and possibly a useful addition to the module description), what is the advantage of using this module over using the standard context *condition* in the derived context? It would seem to me that is in fact more "in the spirit" of the context module; contexts *react* to something, the conditions that trigger them are contained within the context themselves and not influenced from the outside.

Comments

baldwinlouie’s picture

baldwinlouie commented

This module allows a user to set an additional piece of information once your context is set.

For example, one of my sites has three different sections with three different home pages. On each of these homepages, a different set of nodes, based on a node flag is rotated through via javascript. The javascript to do the rotation is custom, and depends on the flagged nodes, which is sent to the front end in Drupal.settings.

So, once one of these homepage conditions were set, I then used this module to set a bit of context information about which flag to use, and then in my code, I can use this context to load the flagged nodes, and set it in Drupal.settings.

I think the module is useful if you need to set conditional context information and use it to communicate with the theme layer.

Hope this helps.

baldwinlouie’s picture

baldwinlouie commented
Status: Active » Closed (fixed)