How to downgrade broken nodewords 1.1+ to 1.0 for a smooth upgrade to 1.3

hass - October 24, 2009 - 09:13
Project:Nodewords
Version:6.x-1.x-dev
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:needs work
Description

Placeholder for downgrade instruction...

#1

hass - October 24, 2009 - 11:06

This 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:

  • A valid backup of your Drupal site having Nodewords 1.0 installed. If you don't have a backup, there is now way to recover!

Step by step instruction:

  1. Disable all Nodewords modules (Basic meta tags, Extra meta tags, Site verification and Nodewords) with version 1.1 or 1.2 or other DEV versions up to <1.3 at admin/build/modules.
  2. Uninstall the modules Basic meta tags, Extra meta tags, Site verification and Nodewords at admin/build/modules/uninstall
  3. Remove the nodewords folder from your installation. Typically it can be found in the folder sites/all/modules.
  4. Execute 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, prepend variable with your table prefix. You can execute this query via MySQL Query Browser or myPHPAdmin, whatever is your preferred tool for DB administration.
  5. Install Nodewords 1.0 to your modules folder e.g. sites/all/modules.
  6. Enable Meta tags 1.0 module (this is Nodewords)
  7. Restore the table nodewords from 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
  8. If you haven't changed any settings in your Drupal installation that are saved in "variable" table you can restore "variable" table the same way. Otherwise you need to extract the 3 settings from your SQL backup file by searching for 'nodewords', 'nodewords-repeat' and 'nodewords-use_front'. Replace below with your settings and execute the query on your DB server.

    Example:

    INSERT INTO `variable` (`name`,`value`) VALUES
    ('nodewords','your settings array is here...'),
    ('nodewords-repeat','i:0;'),
    ('nodewords-use_front','i:1;');

  9. Clear all caches in admin/settings/performance.
  10. Finished. Now you are able to review your previous meta tag settings.
  11. Wait until Nodewords 1.3 final has been released.
  12. Upgrade smoothly to 1.3 without loosing any data or setting. :-)

@Kiam: Please think about adding this to a doc page or the modules readme themself.

#2

chaloalvarezj - October 27, 2009 - 01:21

subscribe for tracking..

#3

kiamlaluno - October 27, 2009 - 08:18
Status:active» fixed

I added the text in the file README.txt.

#4

lost305 - November 2, 2009 - 20:02

There'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?

#5

hass - November 2, 2009 - 20:32

As 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.

#6

lost305 - November 3, 2009 - 19:32

Thank 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.

#7

hass - November 3, 2009 - 21:34

After 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!

#8

System Message - November 17, 2009 - 21:40
Status:fixed» closed

Automatically closed -- issue fixed for 2 weeks with no activity.

#9

kiamlaluno - November 27, 2009 - 12:26
Status:closed» fixed

I am changing the status of this report to make it visible for the next 2 weeks.

#10

JamesOakley - December 4, 2009 - 17:43
Version:6.x-1.x-dev» 6.x-1.5
Component:Documentation» Code
Status:fixed» needs work

Thanks - 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.

#11

hass - December 4, 2009 - 18:58

Never seen this myself yet... maybe something that has changed after 1.3beta5, but I'm only guessing...

#12

kiamlaluno - December 4, 2009 - 19:30
Version:6.x-1.5» 6.x-1.x-dev
 
 

Drupal is a registered trademark of Dries Buytaert.