hi there,

i was excited about your module since it closes a huge gap in drupal. i tried to install and set it up today, but unfortunately, it does nothing. means, i installed, what worked well, and then created a new context. to make sure to see any result, i triggered all node pages, and as action, i hide a region and show a new block somewhere. i saved it, and the context was stored. but nothing changes on the page, and there's no entry in the logs.

did i miss anything while installing?

thanks a lot

CommentFileSizeAuthor
#10 context_settings.jpg165.47 KBhamsterbacke42
#6 footer.png11.6 KBpasqualle
#3 context_settings.png144.83 KBSchneck

Comments

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
Category: bug » support
pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

can you attach a screenshot of your context setting?

Schneck’s picture

Schneck commented
StatusFileSize
new context_settings.png144.83 KB

ok, a screenshot attached. having these settings, i would except that e.g. the footer ("fußbereich") and header will be hidden if i visit a page node, right?

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

the problem is that you set "Sitewide context" to "TRUE"

Should this context always be set? If true, this context will be active across your entire site.

that means your "Powered by Drupal" block (in the footer region) will not be visible on any page, that is why you do not see any difference between pages.
The other context conditions does not really matter as OR operator is used between conditions.

Schneck’s picture

Schneck commented

First, the footer region _is_ visible, and changing the value of "sitewide context" to false does not change anything.
Any other ideas?

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented
StatusFileSize
new footer.png11.6 KB

from your screenshot I can see that the footer region is not visible as there is no "Powered by Drupal" icon..

Schneck’s picture

Schneck commented

this might be an issue with the admin-menu, but on and all other nodes (using garland), the "powered by drupal"-icon appears.

darren oh’s picture

darren oh
Primary language English
Location Lakeland, Florida
commented
Title: Does nothing at all » Node pages condition does nothing

For me the problem occurs with the node pages condition. The path condition seems to work fine.

tahiticlic’s picture

tahiticlic commented

Same here, the only things working are the theme variables changes (so I can be sure that the context reactions apply).

Others stuffs like css injection, blocks adding/removing or regions disabling don't work.

hamsterbacke42’s picture

hamsterbacke42 commented
StatusFileSize
new context_settings.jpg165.47 KB

same as #9 with beta 7

additionally the standard block listing is wrong

is that an issue with the Zen theme maybe ? or does that work?

If this module would work it would be awesome

kyle_mathews’s picture

kyle_mathews commented

I noticed the same thing (that node page conditions aren't working) on this issue #586396: Context Active menu problem

pasqualle’s picture

pasqualle
Location 🇭🇺 Budapest
commented

If you have a problem with block listing, then
1. make sure that in the {blocks} table you do not have records with themes which are not enabled (simply delete the unused db rows)
2. make sure your frontend theme is the default theme

tahiticlic’s picture

tahiticlic commented

This doesn't work. I've checked the {blocks} table and have left only rows corresponding to current theme. Still blocks don't show...

Since it worked with Garland subtheme and not with Zen subtheme, I also beleive it's a Zen issue. Can it be a function that is overriden by Zen?

mrfelton’s picture

mrfelton commented

see #633778: Conflict with themes implementing theme_blocks() perhaps?

yhahn’s picture

yhahn commented
Status: Active » Closed (fixed)

Also please check #664256: Conflict with Panels3. Closing this issue for now, please reopen if you have more specific information about the problem that isn't in one of these other tickets.