Closed (fixed)
Project:
Nodewords: D6 Meta Tags
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
24 Oct 2009 at 09:13 UTC
Updated:
5 Jan 2010 at 13:40 UTC
Placeholder for downgrade instruction...
Comments
Comment #1
hass commentedThis is a documentation issue for the reason that many asked how to downgrade to a previous stable 1.0 version.
The main reason why this is written here - is that 1.1 and 1.2 releases have deleted many if not all of your previously entered nodewords data and the module settings and there is no way to recover this data without restoring a backup.
Required:
Step by step instruction:
admin/build/modules.admin/build/modules/uninstallnodewordsfolder from your installation. Typically it can be found in the foldersites/all/modules.DELETE FROM variable WHERE name IN ('nodewords-repeat', 'nodewords-use_front', 'nodewords_page', 'nodewords_story');on your database. You need to see that 4 rows have been affected (deleted). If you use a table prefix, prependvariablewith your table prefix. You can execute this query via MySQL Query Browser or myPHPAdmin, whatever is your preferred tool for DB administration.sites/all/modules.nodewordsfrom your backup and replace/overwrite the existing table. You can use MySQL Administrator for this task and go to Restore > Restore content by selecting the nodewords table only'nodewords','nodewords-repeat'and'nodewords-use_front'. Replace below with your settings and execute the query on your DB server.Example:
admin/settings/performance.@Kiam: Please think about adding this to a doc page or the modules readme themself.
Comment #2
chaloalvarezj commentedsubscribe for tracking..
Comment #3
avpadernoI added the text in the file README.txt.
Comment #4
lost305 commentedThere's a problem. There's a column in the nodewords table called mtib which wasn't there before so now my backup won't fit.
Could I just delete that column? Or will there be problems in the future?
Comment #5
hass commentedAs written in #1 - no 2 - You need to UNINSTALL the module before the restore! This will remove all tables. There cannot be any stale table.
Comment #6
lost305 commentedThank you for your reply.
I did uninstalled the old modules and ran the sql script from above.
Then I installed 6.x-1.x-dev and the mtid column was there again.
What do you suggest I do?
Thanks for your time.
Comment #7
hass commentedAfter you uninstalled (this does NOT mean - ONLY remove the folder!) check if there is a nodewords table in the database. If you have it - you haven't uninstalled. Additional - you should not use DEV versions and you need a backup from nodwords 1.0 - not any other!
Comment #9
avpadernoI am changing the status of this report to make it visible for the next 2 weeks.
Comment #10
jamesoakleyThanks - all went well, except when running update.php whilst moving from 1.0 to (the current release) 1.5. I got the following error that I don't think is serious:
user warning: Can't DROP 'tin'; check that column/key exists query: ALTER TABLE nodewords DROP KEY tin in /...mypath.../includes/database.mysql-common.inc on line 417.Comment #11
hass commentedNever seen this myself yet... maybe something that has changed after 1.3beta5, but I'm only guessing...
Comment #12
avpadernoComment #13
chaloalvarezj commentedGot the same error as #10... and just ignored it... maybe tin was introduced somewhere between the 1.0 and 1.5 ?!
Comment #14
avpadernoThe update function is trying to remove an index that has been already removed. You can ignore that message, which is caused by a query that has been executed to be sure the index is not present; as there isn't a Drupal function that allows to verify if an index is present, that is the only way to be sure the index is not anymore present.
I am restoring the original metadata, as this report was about the documentation to add to the module.