Hello,

This is the first time I'm trying to set up a website with context and I might be doing something wrong. I've set up only one context, but the blocks aren't showing up.

This is the first part of my context. The blocks I'm trying are just random blocks.

<?php 
array(
  'namespace' => 'context_ui',
  'attribute' => 'global',
  'value' => 'everywhere',
  'description' => 'Blocks that should show everywhere.',
  'sitewide' => '1',
  'path' => array(
    '*' => '*',
  ),
?>

I also have another little issue: I disabled all my blocks in the normal blocks settings page, but when I edit this one context, the drupal icon block is showing in the footer of the region list. (see attachment) It's kinda stuck there. It doesn't show on my website. (none of the blocks do). Previously I had another error which said: The block Devel Node Access was assigned to the invalid region footer and has been disabled. . So this was stuck there as well, but I removed that error by disabling the module.

Any ideas?

Comments

danny_joris’s picture

Obviously I must be doing something completely wrong because I tried to disable some regions and that didn't work either.

danny_joris’s picture

Version: 6.x-2.0 » 6.x-3.0-beta5

I upgraded to the latest 3.0 version, but none of that works either. What can I do to debug this?

yhahn’s picture

Status: Active » Postponed (maintainer needs more info)

I'm lost at what you're trying to do? Try creating a context using the UI by enabling the Context UI module.

danny_joris’s picture

That's exactly what I tried to do. I tried to set up just something very basic through the context UI.

For example:

Condition > node type > Page
Reaction > blocks > added some blocks in the footer

The blocks don't show up in the footer when I view a Page node. I haven't got the chance yet to actually use it, because it didn't work for me.

Please let me know what I can do to debug this more. I saw that there was a zen issue about this too.

danny_joris’s picture

I just wondered about something: the region overview in the blocks section of the context ui, are those the regions of the default theme?

Edit: I guess it is. Just checked.

danny_joris’s picture

Just tested: in Garland everything works fine...

liquid06’s picture

@Danny_Joris: I haven't experienced the blocks assigned by context not showing on the site, but I did notice some ghost blocks that appear greyed out in the context UI. It's as if they're stuck in a region, but they're not even enabled for the current theme. (I'm testing with context 6.x-2.0 and a custom theme based on Zen)

I have a few inactive themes on my site, and I got those extra blocks to disappear from the context UI and avoided error messages about blocks being assigned to 'invalid regions' by using admin/build/block to disable all blocks from all regions in all themes except for the currently-active theme. It may just have been Garland where the stubborn blocks were being added from, though.

Maybe this (kind of old) issue is related? #316555: Context only knows about the current theme

kvantomme’s picture

danny_joris’s picture

#8 Thanks, interesting article. I think it's indeed that issue and I have it in Zen 6.x-2.0 . This is a workaround for it: http://drupal.org/node/634552#comment-3244662 . But it doesn't solve the actual issue yet.

aldenjacobs’s picture

Not sure if this helps, but it may!

Are you using a custom theme?

Plausible solution:

http://drupal.org/node/922032#comment-3491534

gr33nman’s picture

Same thing with Drupal Head - fresh install, using core default theme.

# The block Devel Node Access was assigned to the invalid region footer and has been disabled.
# The block Devel Node Access by User was assigned to the invalid region footer and has been disabled.
danny_joris’s picture

gr33nman’s picture

@Danny_Joris, I'm assuming that's a patch for zen theme. This must be a separate issue. My bad. I don't even have zen installed.

stephenrobinson’s picture

Same here, neither zen or zen960 show any blocks from context with 2.0 or 3.0

paulocs’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

Do you still have problems with 7.x or 8.x?
As context 6.x is no longer supported, I will close it.

Thanks.