Issues in the upgrade path from 1.x to 2.x

I'll be taking a look at this.

Well I think we'll be taking a completely different approach here, but this will still apply to the 1.x to 2.x upgrade. As I understand it we'll (hopefully) be moving what is now called 1.12 into the 2.x branch since it is indeed a major upgrade, not a minor version update.

Here are the results of my testing however, which we'll still need to address if upgrading from 1.x to 2.x.

Functionality:

                             1.11 | 1.12 | Upgrade success

Global keywords                X  |  X   |  X
Node metatags save             X  |  X   |  X
Term metatags save             1  |  X   |  X
Vocabulary metatags save       2  |  X   |  X
Profile metatags save          X  |  X   |  X
Custom path metatags save      3  |  X   |  X
Term metatags on term listing  X  |  X   |  X
Term metatags on node page     X  |  X   |  4
Node metatags on node page     X  |  X   |  X
Description gen from teaser    X  |  X   |  5
Profile metatags on profile    X  |  X   |  X
Frontpage Yahoo displayed      X  |  6   |  6
Frontpage Bing displayed       X  |  6   |  6
Frontpage Google displayed     X  |  6   |  6
Frontpage metatags displayed   X  |  6   |  6
Settings page saved            X  |  7   |  8


Issues:
1. Term settings save but values are always defaults when editing.
2. Vocbulary settings save but values are always defaults when editing.
3. Custom path metatags save but values are always defaults when editing.
4. Terms are not automatically shown on the node page, since the [metatags-taxonomy-keywords] token needs to be inserted into every keyword row.
5. Description metatag reverted to default upon upgrade. The [metatags-description] token needs to be inserted into every row.
6. All front page settings continue to exist in the database but none of them display (defaults used if available).
7. The "Global keywords - first/second" group does not display anywhere on the site as far as I could tell. The previous option for just "Global keywords" both upgrades and dispays okay, but there is no longer any way to edit them.
8. A few issues with renamed variables:
 - "Generation source" option reverts to default of "Generate meta tags content from the node teaser". (Renamed from nodewords_metatags_generation_source to nodewords_description_generation_source)
 -"Global keywords" not lost but uneditable. Not migrated to first/second group.

Upgrade path oddities:
1. Token module is not enabled even if "nodewords_tokens" is enabled. "nodewords_tokens" should probably only be automatically installed if Token module is installed.

So the major issues include:
1. Front page settings are not lost but they are not in any way editable or used after upgrade.
2. All automatic description and keyword metatags are effectively ignored upon upgrading because they have been moved to tokens. In order to restore description and keyword metatags, an update function needs to insert the [metatag-*] tokens into every row of the database for description and keywords.

upgrading from 1.11 to 2.0-alpha results in no description meta tags on page views where the default (e.g. node teaser) should appear.

Making these easier to index.

Unfortunately this module is no longer supported, so I'm closing this issue.