Closed (fixed)
Project:
Context
Version:
7.x-3.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Apr 2011 at 15:48 UTC
Updated:
1 Jan 2012 at 20:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
kevinn commentedYou need to activate context module first.
Comment #2
sutharsan commentedThis occurs during the standard upgrade procedure, in this case executed with "drush sup". In my opinion the module should handle this situation.
Comment #3
ar-jan commentedPerhaps a notice on the project page and in the README.txt concerning "Upgrading from Context 6.x-3.x to 7.x-3.x"? Since the standard way to upgrade is with modules disabled.
Comment #4
michaelfavia commentedThis error occurs with the module disabled as well when you upgrade it after d7 does its thing.
Comment #5
sanduhrsHad the same problem.
The attached patch fixed it for me.
Comment #6
sanduhrsJust had the same problem again, upgrading a different site.
The patch in #5 fixed it.
Increasing this to critical, as it breaks the upgrade path from D6 to D7.
In addition the patch doesn't introduce any problems, it just checks whether the module is loaded and if not loads it.
Please review.
Comment #7
tekante commentedCommitted to 7.x-3.x branch and will be available in latest dev release shortly. Thanks for the bug report and patch.