The context's path condition should use the popular fieldset seen on block's (and other items) settings page, where you can choose between showing or NOT showing the element on the specified pages, or use PHP code to determine visibility.

Comments

jmiccolis’s picture

jmiccolis commented

I'm not sure we're going do this.

For a variety of reasons php code is entirely off the table, chief among them being security and beyond that the very reason the module exists it to get away from needed to use php code for block visibility.

I'll let others voice opinions about path conditions supporting 'not' but this seems to go against the additive model we've got right now and I'd prefer not to have it.

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

yes, I absolutely agree. The current context model does not allow 'not' conditions.

If it would be implemented, then it should be done globally for all condition types, not only for paths.

steven jones’s picture

steven jones commented
Status: Active » Fixed

Looks like the latest context code in the 2.x branch checks the paths, but doesn't use PHP visibility settings on the block setting page.

Marking as fixed, if this doesn't work, please re-open as a bug.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.