Currently, if you want to select the "sitewide" context, as in, always TRUE, the condition seems to be evaluated before the context_module reaction - they must share the same hook.

Increasing the system weight of context_module slightly should ensure that you can have "always on" modules in contexts.

Comments

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Status: Active » Postponed (maintainer needs more info)

Do you mean that the condition for the Context is sitewide and the reaction is the toggle modules?

The reason I ask, is that if the Context is always on and it's telling modules to be on or off, then why do you need a Context to do this at all?

If I misunderstand, can you let me know what I'm missing here?

thedavidmeister’s picture

thedavidmeister commented

Ease of deployment.

We've found it easier and more reliable to manage a single, centralised array of modules in code that we want enabled on all environments than juggling module dependencies and update hooks distributed across a project.

thedavidmeister’s picture

thedavidmeister commented
Status: Postponed (maintainer needs more info) » Active