Hello, i'm experimenting the context module (after a very good experience with the 7.x version), but i don't know why when I place a block inside a region, all the remaning region doesn't display the blocks assigned in the main drupal block page. Am I doing something wrong?

Comments

CRY_X2 created an issue. See original summary.

csedax90’s picture

csedax90 commented

Someone is maintaining this module?

NormySan’s picture

NormySan commented

Hi CRY_X2,

Context manages blocks on it's own and does not create blocks that can be modified from the drupal block list. All blocks have to be managed through context itself.

csedax90’s picture

csedax90 commented

I do not think it's a good idea an operation of this type. The convenience of Context has always been to be able to modify only the blocks to specific regions without rewriting all, simply and without burdening the system. An operation like this makes the module very similar to Panels.

joco_sp’s picture

joco_sp commented

I agree with CRY_X2.
It would be even nicer if there will be an option to choose if you want to remove all other blocks or not.

joco_sp’s picture

joco_sp commented

I found a solution, but I don't know if it's all right for everyone.

I just made a "Sitewide" context.
1. added only one condition - "Current theme" and set it to my theme. Or if you prefer, you can exclude your admin theme. So this context will be used on all pages of my theme, except on admin
2. added the blocks that should be displayed on all pages
3. removed all block from the /admin/structure/block, so I have everything in one place

csedax90’s picture

csedax90 commented

Ok this is definitely a great way to get around this, but I must be reconsidered the operation of the module to reflect the functionality already present in Drupal 7 , otherwise its usefulness vanishes .

NormySan’s picture

NormySan commented

@CRY_X2 If the thing you want is to have blocks placed through context intermingle with the blocks placed through Drupal this is very much possible. The only thing you would have to do is write a custom reaction that allows you to place blocks that are then rendered by extending the built in Drupal block page variant.

The module used to render blocks like this previously but i decided to opt-out from doing it this way since it introduced to much complexity for my taste. But it's very much possible to do.

steveoliver’s picture

steveoliver commented

Check this out: https://dev.acquia.com/blog/using-block-visibility-groups-to-create-cond...

jidrone’s picture

jidrone commented

In my opinion is a bad practice to use both at the same time, context is a better way to place blocks in pages because it allows you to name, group and document your contexts so that other developers can easily find them and change the region assignment.

If you are a developer supporting to a website made for someone who used both, you will need to check in several places making your work inefficient.

Even in D7 using only context is the best practice, I think this is not a bug and can be closed.

icurk’s picture

icurk commented
Status: Active » Closed (works as designed)