Best integration point for a path condition? [#966880]

How would I go about integrating a path condition into my module? I've tried putting it in mymodule_init() but context_active_contexts() called there doesn't return any contexts. I have successfully integrated the path condition into a hard-coded menu item in my module, where context_active_contexts() returns the expected contexts when I hit that path (and path is defined in the GUI). However, I'd like users to be able to define any arbitraty path in Context's admin GUI.

I've integrated checks for node conditions into mymodule_nodeapi(), I just can't figure out where the best place to check for path conditions is.

Comments

Comment #1

markj commented 10 November 2010 at 16:29

After a bit more experimenting, I adjusted the weight of my module to 50 and now context_active_contexts() works in hook_init(), so I can use hook_init() in my module as an integration point. I took a hint from the comment "This should be run at a late stage of the page load to ensure that relevant contexts have been set." in the context_active_contexts() function definition in context.module.

Comment #2

ymakux commented 7 October 2012 at 10:30

I faced the same problem for d7. It's better idea to not use hook_init at all, use hook_context_page_reaction() instead

Code sample

function mymodule_context_page_reaction() {
  if (module_exists('context')) {
    if ($plugin = context_get_plugin('reaction', 'myreaction')) {
      $plugin->execute();
    }
  }
}