Closed (works as designed)
Project:
Context
Version:
6.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
10 May 2010 at 11:22 UTC
Updated:
29 Jul 2010 at 18:26 UTC
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
Comment #1
steven jones commentedThis was down to some misleading documentation. Fixed in http://drupal.org/cvs?commit=365148.
This is what the 'default' condition is for btw.
Comment #3
chriscalip commentedbug 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
Comment #4
simeIs my support query redundant and actually related to a bug in how sitewide context works? #813954: Path exclusion and active context condition
Comment #5
yhahn commentedComment #6
yhahn commentedI 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.
Comment #7
chriscalip commentedHey 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.