Looking at the code sitewide conditions should get overridden by a matching path condition in the namespace/attribute, but they don't seem too. An issue was raised in IRC about two contexts, one with a sitewide condition and the other matching the path 'admin/*' the sitewide context always won.

Comments

steven jones’s picture

Status: Active » Fixed

This was down to some misleading documentation. Fixed in http://drupal.org/cvs?commit=365148.

This is what the 'default' condition is for btw.

Status: Fixed » Closed (fixed)

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

chriscalip’s picture

Version: 6.x-2.0-rc3 » 6.x-3.0-beta5
Status: Closed (fixed) » Active

bug report for block assign on same regions: default condition (sitewide context) not being trumped by a matching path condition instead both default reaction (assign block:box) and overriding reactions (assign block:box) appears in same region.. on a side note: using context layouts to implement multiple layouts

sime’s picture

Is my support query redundant and actually related to a bug in how sitewide context works? #813954: Path exclusion and active context condition

yhahn’s picture

Version: 6.x-3.0-beta5 » 6.x-3.x-dev
Assigned: Unassigned » yhahn
Priority: Normal » Critical
yhahn’s picture

Status: Active » Closed (works as designed)

I could be interpreting #3 wrong but this is how context 3 is currently designed to work. If you have two active contexts you will indeed get both of their reactions. You may be interested in #813954: Path exclusion and active context condition where we're working on a way for one context to require or deny the active status of another.

chriscalip’s picture

Hey yhahn, yes you got it right. I guess my assumption was a default context gets overridden.

default - an option that is selected automatically unless an alternative is specified

That said, I am looking forward to #813954: default context that gets overridden

Thank you.