The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I've written a basic context reaction that allows users to switch the home page url (site_frontpage) based on conditions. I think it would be better for this to go into the context extra's module as opposed to creating a new module with just a simple reaction. Let me know what you think.
- Scott
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | context_extras-847312.patch | 4.1 KB | tim.plunkett |
| context_reaction_front.tar_.gz | 1.5 KB | hadsie |
Comments
Comment #1
chriscalip commentedHadsie,
Tested and added in the module as a new release "beta2". Thank you for your contribution.
kind regards,
Chris Calip
Comment #2
chriscalip commentedComment #3
chriscalip commentedComment #4
hadsie commentedSweet, thanks chris! :)
I think it's probably safe to mark this as fixed.
Comment #5
tim.plunkettFor a site I was building I needed a context on available on pages that weren't of a specific taxonomy term.
This plugin is very similar in theory to cep_negate_path, and it's working beautifully on my site.
A review of the code and possible inclusion in the module would be great.
Comment #6
tim.plunkettI think this doesn't work as well as I'd like, it seems to hate the node/% panels page.
It really should just return true for non-nodes, and be called by hook_nodeapi(), but I don't know how to do that. Also, panels prevents hook_nodeapi() from ever getting to the 'view' $op.
I'm stuck!
Another plugin solved my use case for the short term: #813954: Path exclusion and active context condition
That one is very useful.
Comment #7
chriscalip commentedsaw the post, will take a look later tonight.
Comment #8
chriscalip commentedits a tough one, looks like short term solution for now works.
Comment #9
tim.plunkettI think using #813954: Path exclusion and active context condition is a better approach.