This issue appears to break the Drupal Commons Install Profile on Context 3.x upgrade, as Context Contrib is a Commons Core Feature dependency. In light of this post, I'm sure others have run across this already. Upon upgrading the Context module to 3.x, the Commons Core Feature is disabled, as a result of the missing Context Contrib - which in turn immediately wreaks untold sitewide havoc. Okay, maybe that's a bit dramatic. But it does result in several anomalous errors.

I vaguely recall a mention of trying the Context 3.x upgrade at your own risk (I'm paraphrasing) during the recent Acquia webinar on DCIP with Jay and Bryan. So for now it looks like upgrading the Context module from 2.x to 3.x in DCIP is a no-go, eh? I'm thinking about unhitching Commons Core from Context 2.x and trying again, but is it feasable (lots of other dependencies) and worth the trouble at this point, or am I better off sticking with Context 2.x for now?

CommentFileSizeAuthor
#2 DC Commons Core with Context 2.x dependencies35.46 KBpaskainos
#2 DC Commons Core with Context 3.x dependencies29.98 KBpaskainos
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mstef’s picture

mstef CreditAttribution: mstef commented
Status: Active » Closed (works as designed)

Stick with Context 2.x for now. I'm not sure what you mean by Context Contrib? What's important is Context_og is also v2.x. That needs to be upgraded to the 3.x branch as well. But I wouldn't recommend doing that either. I wrote the 2.x branch of Context OG so I know it works. Last time I tested the 3.x branch, it didn't work with panels - which is what powers our group homepages. Another problem is that the exported contexts in Commons were created with context 2.x.

We plan to upgrade context, features, ctools, panels, etc, in the next release (hopefully). I would just recommend waiting.

paskainos’s picture

paskainos CreditAttribution: paskainos commented
FileSize
DC Commons Core with Context 3.x dependencies29.98 KB
DC Commons Core with Context 2.x dependencies35.46 KB

@mikestefff: Thanks for the info. FYI: we upgraded both the Context module and Context OG to the respective 3.x versions. In the current use case, our install of Drupal Commons requires considerable front-end customization to create more of a 'brochureware' front-end. This includes simplifying the DC UI dramatically for front-end users (unauthenticated, low level permission...) while back-end users enjoy the extensive benefits DC offers. We figured while we were at it (customizing, turning off some panels, rewiring, etc.) we might as well try the upgrade. Based on your input, we'll stick with 2.x for now.

P.S. I've attached two screenshots to help elucidate the Context Contrib dependency issue. The Context Contrib dependency is highlighted in each image. The Context 2.x screenshot shows the Context Contrib dependency enabled, while the Context 3.x screenshot shows the Context Contrib dependency missing, since in 3.x Context Contrib no longer exists. Hope that clarifies, if for no other reason than to help others who happen on to this issue and spend all day trying to uncover what's causing numerous anomalies in their DC install.

Wolfflow’s picture

Wolfflow CreditAttribution: Wolfflow commented

Subscribe

chicagomom’s picture

chicagomom CreditAttribution: chicagomom commented

+1 for an upgrade. We have a multi-site setup and would dearly love to use DC; hoping this issue is resolved as we need the latest n greatest Context for other sites.