I'm not sure where to look to find a resolution to this, but it is a frustrating issue. When using context, certain blocks simply refuse to abide by their display settings within the block menu. For instance, the search form block should only be displaying in a certain region on a select few pages, but will populate that same region on every page, unless it is hidden via CSS (not the way I would like to accomplish this functionality).

Any suggestions?

Comments

i-dont-use-this-account’s picture

i-dont-use-this-account commented

Sounds like the Search box is still enabled on the block management page ( /admin/structure/block ).

threadsniper’s picture

threadsniper commented

Just as a clarification. Why would I not want the search box enabled on the block management page? Is there some compatibility issue with this block and the context module? I am not using Context's block management functionality. I want to control blocks via the block administration area...

i-dont-use-this-account’s picture

i-dont-use-this-account commented

Alright. So, let me make sure I'm understanding you completely.

You aren't using context for block management. And you're including the search form in a region at /admin/structure/block, and then controlling what pages the block appears on by using the tick box to only show the block on certain pages, and then using paths to control what those pages are?

If that's the case, then how did you come to the conclusion that the search form is displaying on all pages because of context. Did you disable context and then the form goes away?

Everyone works differently, and there are always multiple ways to skin a cat. Personally, when I use context (I always use context), I handle all my block management with context. It just seems cleaner and more manageable, to me.

threadsniper’s picture

threadsniper commented

You've got it!

When not using context, I don't have the issue. I double and triple checked my contexts to see if I had erroneously added the block somehow and have no blocks enabled via context.

What are the benefits of using block management within Context? Am I correct in assuming (given this discussion) that, should I decide to use context to manage blocks, I should use ONLY context for block management from that point forward?

I guess I never went down this road because there was no "configure" option in the context blocks area, which meant that I was arranging blocks via context, but still using the /admin/structure/blocks page to edit the blocks, which seemed like an unnecessary extra step...or am i missing something (perhaps a contrib that gets me that functionality)?

i-dont-use-this-account’s picture

i-dont-use-this-account commented

You're right. If you're creating a block by just adding something like HTML to the body of the block then you would use the block admin page to do so. Then you would use contexts to place the boxes in the regions they belong to. Seems like extra work I'm sure. However, on most sites, I'm lucky if I have a single block that was actually created on the blocks page. Meaning, most of my blocks are generated by views, because I need the content of them manageable by the client I'm building the project for.

i-dont-use-this-account’s picture

i-dont-use-this-account commented
Status: Active » Closed (works as designed)

I'm going to go ahead and close this.