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

Comments

chriscalip’s picture

Status: Active » Closed (fixed)

Hadsie,

Tested and added in the module as a new release "beta2". Thank you for your contribution.

kind regards,
Chris Calip

chriscalip’s picture

Status: Closed (fixed) » Active
chriscalip’s picture

Version: 6.x-3.0-beta1 » 6.x-3.0-beta2
hadsie’s picture

Status: Active » Fixed

Sweet, thanks chris! :)

I think it's probably safe to mark this as fixed.

tim.plunkett’s picture

Status: Fixed » Needs review
StatusFileSize
new4.1 KB

For 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.

tim.plunkett’s picture

I 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.

chriscalip’s picture

saw the post, will take a look later tonight.

chriscalip’s picture

its a tough one, looks like short term solution for now works.

tim.plunkett’s picture

Status: Needs review » Closed (won't fix)

I think using #813954: Path exclusion and active context condition is a better approach.