I was able to upgrade from OP 1.7.1 > 2.0 and everything worked. Then I proceeded to upgrade from 2.0 > 2.1 following the upgrade procedure, but for some reason, when I go to the last step of the upgrade:
Go to admin/build/features and if you see any features showing "overriden" status, go into the feature, check overriden components and click on "revert components". Repeat for all other overridden features, until all of them show status: "default".
I see "Features" and "Testing", but when I click on "Features" nothing happens. The list does not display. Also, I notice that previously, "Testing" was on top and "Features" was below, now "Features" is on top and "Testing" is below.
I've reinstalled the Features module. I've cleared cache. I've rerun the update.php. It's still not working and I don't know what else to do.
Thank you for your help.
Joe
Comments
Did your features show in OP
Did your features show in OP 2.0?
If yes, then I would redo the upgrade and follow the steps exactly as it it mentioned. Make sure you deleted the files and folder as mentioned in the upgrade instructions.
sTattler.com
Actually, for the steps that
Actually, for the steps that asked to delete files...
**Manually delete the folder sites/all/modules/context/context_contrib.
**Manually delete all the files under the folder: sites/all/modules/openpublish_core/contexts
These files did not exist for me, so I obviously did not delete them.
Any clue as to why?
How come! Did you not use
How come! Did you not use context module in OP 2.0? When did you upgrade your 1.7.1 to OP 2.0? Make sure in that upgrade, features and the contexts were included and enabled.
sTattler.com
I did the upgrade from 1.7.1
I did the upgrade from 1.7.1 to 2.0 to 2.1 today :).
As far as I could tell, the upgrade from 1.7.1 to 2.0 went well. I didn't check context, but Features was working. I was able to revert all those overridden features to default. Though, I do remember I had similar issues with whatever files were supposed to be deleted in the upgrade (from 1.7.1 to 2.0). That worried me some, but I couldn't find those files and things appeared to work ok (though I will admit, I didn't do thorough testing).
These upgrades are so stressful. I'm always on pins and needles.
Thanks stattler for your response. If you have any special insights on this or an epiphany, it would be greatly appreciated : )
—Joe
I am sad to know that things
I am sad to know that things are not going well on your side. This happened to me as well when I upgraded from 2 to 2.1. For me it was strange that there was another folder was created with the name openpublish_features6x14 under /sites/all/modules directory. I had to remove that in order for me to use the features and contexts.
Check with yours if that is the case, for some unknown reasons.
Other than this, I am afraid, I have nothing else left to suggest. I am only a user of Drupal and I am poor on its insight (i.e., programming aspect).
sTattler.com
Well, you're a very helpful
Well, you're a very helpful user and more insightful than me.
By the way, I just went back to my last back up which was OP 2.0. I noticed that there is a sites/all/modules/context/context_contrib, which is the folder that the upgrade instructions say to delete (which I did not see before). When I do my unpack of 2.1 onto 2.0, I copy the context module folder into my sites/all/modules folder, which effectively replaces everything in the context folder with whatever is new in OP 2.1's version of context.
When the instructions ask to "Manually delete the folder sites/all/modules/context/context_contrib" after the instructions to unpack 2.1 over 2.0, shouldn't the file they wanted deleted already be gone because the folder is over written?