Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
Trying to use this to set the blocks shown in the various regions of a particular theme but the available regions for block positioning are those of the "default" theme and not the theme chosen as part of the contextual rule..
So if I want to place blocks into a region of a theme that isn't the default I can't do it because that region isn't available for me to select..
Comments
Comment #1
ryanwebpage CreditAttribution: ryanwebpage commentedI have not experienced this behavior before. Context plugins do not handle the active themes, regions and blocks. That is handled in the context core. When I get a chance I will see if I can recreate this behavior.
Comment #2
ryanwebpage CreditAttribution: ryanwebpage commentedI think I know what is happening now. To be honest I've never used this plugin for that use case. I've always used it for loading CSS files based on the active theme. Context blocks and regions load only the default theme regions. I will have to see if I can change the theme loaded by context blocks if you define a condition with a theme that is not the default.
Comment #3
wipeout_dude CreditAttribution: wipeout_dude commentedThat would be useful..
To complicate thing further, the module allows you to select multiple themes in the condition.. So really the reactions need to be able to address all the regions of all the selected themes selected in the conditions area.. I guess that makes things really complicated as far as managing the UI goes.. :(
Comment #4
Baysaa CreditAttribution: Baysaa commentedAgreed with wipeout_dude. Honestly, the core Blocks module handles different themes just fine. Maybe this is an issue for Context core?
Comment #5
Baysaa CreditAttribution: Baysaa commentedFound an issue already: Context only knows about the current theme