Posted by pkcho on July 30, 2010 at 8:06pm
I attempted to upgrade my site again from 2.0 to 2.1 with the exact same result with Features (not being able to finish the final step in the upgrade process with Features).
No Features lists display. When I attempt to click on Features to set each "overridden component" to "default", no components show up at all.
I remember there being a discussion between sTattler and irakli about OP not finding Features correctly? sTattler did something to redirect some tables in the database to the correct location... would something like this be helpful in my situation?
If so, could someone show me how to do this?
Thank you.
Joe
Comments
.. that depends on whether
.. that depends on whether the reference to the folders are wrong in the database tables. In my case there was a folder named openpublish_features6x14 in my /sites/all/modules directory. I noticed that after irakli's comment and then deleted the folder and kept the actual one. Only because of this, I had to manually edit the paths in the database table which were referring to the wrong directory.
I wish I could help you but the problem is there is a high probability that the problem is at your end, but we dont know where. Because I myself did the upgrade and after some issues with the features, I was finally able to solve the problem. In my case however, the relevant files and folders were there!
Now, if you have older backups of your database, you could try to upgrade on them to get some more avenues of possibly finding the root of the problem. Otherwise, if you keep upgrading on the already "upgraded" database, it won't resolve the problem.
I remember you said something that after upgrading from OP 2 to 2.1, the folders that were supposed to be deleted were not there. That is certainly a problem and this indicates that you had problem in the upgrade from 1.7 to 2.0.
Any thoughts from anybody else? Thanks.
sTattler.com
I understand that it's quite
I understand that it's quite possible that I made a mistake somewhere along the way with the upgrade process. Does anyone see any clues here on what I might have done incorrectly in the upgrade process?
What if I took a step back and asked if anyone knew why the files/folders that I am supposed to delete are not there?
When i unpack the upgraded version of OP on top of the old version, doesn't that overwrite these folders that need to be deleted? For example, in sites/all/modules/... the context folder (that contains the folder to be deleted) is replaced with the newer version from the latest version of OP. Am I installing this in the wrong order?
––Joe
If you ask why those files
If you ask why those files and folders are not there, then the answer would ask you to go and check your previous installation.
As for upgrading from 2.0 to 2.1, please read the following carefully
# Manually delete the folder sites/all/modules/context/context_contrib.# Manually delete all the files under the folder: sites/all/modules/openpublish_core/contexts
It never said that you are deleting the
contextfolder. Rather, its the files insidecontexts(note the plural, s) folder. They asked to delete the context/context_contrib folder, i.e., the context_contrib folder inside the /sites/all/modules/context folder. This should not be considered as deleting the whole context folder.Why deleting files/folder?
My understanding is that they have moved the context thing somewhere else.
Also notice the content of the openpublish_features folder:
op_blog op_imagecrop_config op_resource README.txtop_article op_defaults op_imce_config op_slideshow
op_audio op_event op_misc op_videos
op_author op_image op_package premium_default_off
Hope you can track back to the point where the root of all error lies.
sTattler.com
Yeah, I didn't delete the
Yeah, I didn't delete the context folder. I just replaced it with the version from the upgrade and these lines...
# Manually delete the folder sites/all/modules/context/context_contrib.# Manually delete all the files under the folder: sites/all/modules/openpublish_core/contexts
are not in the upgraded Context folder, but they are in my 1.7.1 version of the install.
If they are in your 1.7.1
If they are in your 1.7.1 version of the install, then you are instructed to delete them. :)
sTattler.com
But the order of operations
But the order of operations in the upgrade instructions are:
# Unpack openpublish 2.0 tar.gz on top of 1.7 installation. Make sure unpack overwrote corresponding parts of 1.7 and did not just create a subfolder in 1.7.# Manually delete multimedia.inc, events.inc and resources.inc in openpublish_core/views/. These views are now respectively stored in op_misc, op_event and op_resource.
The upack overwrites the files that I am asked to delete.
I must be missing something obvious.
Sorry, I am a bit confused
Sorry, I am a bit confused now. Which are the particular folders and files that you think are being deleted. Please specify them version by version. For example,
From 1.7.1 to 2.0:
Which files are to be deleted?
What are yours confusions?
From 2.0 to 2.1
Which are to be deleted?
What are your confusions?
sTattler.com
For each upgrade (for 1.7.1
For each upgrade (for 1.7.1 to 2.0 and for 2.0 to 2.1), the files that the upgrade instructions say to delete exist in my install prior to doing anything in the upgrade.
But if I follow the instructions that say to:
Unpack openpublish 2.0 tar.gz on top of 1.7 installation. Make sure unpack overwrote corresponding parts of 1.7 and did not just create a subfolder in 1.7.When I unpack and copy the new OP version onto my current version, the files that I am supposed to delete manually are overwritten by the unpack.
For example, copying all of the contents of sites/all/modules/... from the OP 2.0 replaces all of the same module folders in my sites/all/modules/... which effectively gets rid of the files that I am then asked in the next step to manually delete.
The same problem occurs for the 2.0 to 2.1 process.
Maybe the problem is how I unpack and copy over the newer version of OP?
Either you are not following
Either you are not following what I am saying or I am not getting what you are saying. How do you know that you will be deleting the files that you have just upgraded? Are you sure? How? I don't think people who made OP are instructing you to delete the files that you just upgraded.
That is why I asked you to specifically verify (for your satisfaction) (or list the files) that you are overwriting and then deleting. I believe this is NOT what we are doing. This does not make sense.
When you overwrite the existing install with the updated one, that does not mean that you are overwriting everything. It may create some new files in new locations and leave some of them untouched. IT is likely that the files that you will be deleting were not touched during the overwriting process. However, they are to be deleted because another set of files to do the same job has been copied.
sTattler.com
Ok. Just so that I am
Ok. Just so that I am clear.
When you unpack the upgrade onto your old OP, especially the modules, do you copy all the new module folders (for example sites/all/modules/context) into your old modules folder (sites/all/modules/context)?
Or, do you go into the module folders themselves and copy the contents of the new module folders into the contents of the old module folders (For example, sites/all/modules/context/context_layout, etc...)?
The first method, overwrites all the files within the module. The second method overwrites most of the specific files within the module. I say most because if the file structure in the module folder has changed than the new files won't necessarily overwrite the old (if the file names have been changed).
I have been doing the first. Are you doing something different?
Do you mind explaining in some detail how you are handling your unpack? Hopefully, this might clarify things.