I'm completely unsure whether or not this is a Panels bug, a Context bug, or simply no one's fault.

I'm using Panels to override a certain node type "group".
If I use Context.module to enable certain blocks for the node type "group", it doesn't work unless I disable the panel.

My guess is that once Panels takes over, context doesn't know what's going on.

Any suggestions?

Comments

mstef’s picture

mstef commented

I think this is a context module. This patch/module worked fine for me.

http://drupal.org/node/595744#comment-2136758

You be the judge.

merlinofchaos’s picture

merlinofchaos commented
Component: Plugins - contexts » Code
Status: Active » Closed (fixed)

Looks like they decided it was their issue, so we're all good.

hazah’s picture

hazah commented
Version: 6.x-3.3 » 7.x-3.x-dev
Status: Closed (fixed) » Active

Hey there. This is another issue currenly active along the same lines.

https://drupal.org/node/1271324#comment-6300598

While these were, in fact, "resolved" by applying changes to context, I don't believe it's fundamentally its issue. It's likely that Panels is changing certain parameters such that context no longer recognizes that it's displaying a page type it supports. Basically the plumbing changes just enough from the default that the context module breaks (any module that makes similar assumptions is in the same boat). I could be off base in this regard, but I feel that the true issue is in the way Panel changes the environment another module might come to expect. I'm not aware of the extent to which this is necessary, so I'm merely bringing this up again to see if the path of least resistence lies here.

lsolesen’s picture

lsolesen commented
Issue summary: View changes
Status: Active » Postponed (maintainer needs more info)

Could you please try with the latest dev and update the version accordingly if the issue is still present?

lsolesen’s picture

lsolesen commented
Status: Postponed (maintainer needs more info) » Fixed

Closing for inactivity. Please reopen with exact steps to reproduce on latest dev, if you still have the issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.