Hi,

I tried the "Upgrade from Nodewords"-Option. After that I get the message "228 results processed in 0 iterations.". And all meta tags fields of the sites are empty. I don't know what I did wrong.

Jan

CommentFileSizeAuthor
#2 1.JPG31.52 KBknarzer77
#2 2.JPG11.01 KBknarzer77

Comments

valthebald’s picture

Did you select any field in 'Fields to import'?

knarzer77’s picture

StatusFileSize
new11.01 KB
new31.52 KB

Yes, I did. You can seen my steps in the screenshots.
I'm running the drupal 7 sites on XAMPP. Can this be the reason?

knarzer77’s picture

Version: 7.x-2.0 » 7.x-2.1

Thing I have noticed: when I go to the meta fields in the content types and try to edit, I get the message "There is data for this field in the database. The field settings can no longer be changed."

valthebald’s picture

And you didn't enter data manually? Could that mean that data actually was imported, but is not displayed in produced HTML? Can you please check field_data_meta_description, field_data_meta_keyword etc. tables in your database?
And no, I don't think the problem is related to XAMPP

knarzer77’s picture

I really do not understand it yet. 3 website upgrades I've done. From one website are only 5 pages filled with the correct metatags. This are very old blog entries. The other blog pages and all other are empty.
From the other websites all field_data_meta_description, field_data_meta_keyword, ... are completely empty.

knarzer77’s picture

Now I tried to upgrade again, I got following error message:

FieldException: Attempt to create field name meta_revisit_after which already exists and is active. in field_create_field() (line 81 of C:\xampp\htdocs\drupal\modules\field\field.crud.inc).

valthebald’s picture

Version: 7.x-2.1 » 7.x-2.2

7.x-2.1 had broken import code (my bad). Could you rerun with 2.2 please?

knarzer77’s picture

I tried the new version. While trying to upgrade at my one website, I still get the message:
FieldException: Attempt to create field name meta_revisit_after which already exists and is active. in field_create_field() (line 81 of C:\xampp\htdocs\drupal\modules\field\field.crud.inc).
I had to delete something in the database?

At my other website, I get the message:
The website encountered an unexpected error. Please try again later.

craigjones’s picture

I have reproduced the same here - import looks like it's run, but the data is empty.

I ran the import as follows:

  • Enabled 'metatags_quick' and 'metatags_quick_import' modules
  • Navigated to admin/config/search/metatags_quick/import ('Upgrade from nodewords' in the menu)
  • Selected 'Create fields' as this was from-scratch without any existing configuration
  • Selected 'description' and 'keywords' in the 'Fields to import' section (though which fields are selected doesn't matter)
  • Submitted form via 'Convert' button

Convert seemingly ran, giving the message...

Converting metatags for 821 nodes
1642 results processed in 9 iterations.

... but no data is contained in either of the field_data_meta_description or field_data_meta_keyword tables.

valthebald’s picture

What version of nodewords do you import from?

knarzer77’s picture

I have the latest version of nodewords: 6.x-1.11.

justindodge’s picture

I have the exact experience as #9, the import looks like it's running but no data ends up in the tables. I'm using 7.x-2.2 and coming from Nodewords 6.x-1.12-rc1

justindodge’s picture

Version: 7.x-2.2 » 7.x-2.3

This is still an issue as of 7.x-2.3

Any direction to help troubleshoot?

justindodge’s picture

So I've done a little investigation into this issue and I have discovered the cause of my problem.

The D6 site I was importing from at one time had the locale module on, even though there was only one language on the site (en). All of the nodes in the node table had language = 'en'.

I tried turning locale back on with my D7 site, but it seems that the field is not translatable for 2 reasons:
1. The field settings declared by the function _metatags_quick_field_attach()

$field = array(
      'field_name' => "meta_$meta_name", 
      'type' => 'metatags_quick', 
      'module' => 'metatags_quick',
      'settings' => array(
        'meta_name' => (isset($known_tags[$meta_name]['meta_name']) ? $known_tags[$meta_name]['meta_name'] : $meta_name),
        'max_length' => variable_get('metatags_quick_default_field_length', 255),
      ), 
      'cardinality' => 1,
    );

do not set 'translatable' to be true.

2. There is no translation handler - the function field_has_translation_handler returns false when called for this field. Note that I have no idea what a field translation handler is or what would provide it. My first guess is that the "Content translation" module might do it, but I didn't test.

Without these requirements in point 1 & 2 above, the available languages for the fields for meta_description and meta_keywords as returned by field_available_languages() comes back as LANGUAGE_NONE (which is a string 'und').

Since the nodes I was trying to import had the language set as 'en', there are no values to save in the function metatags_quick_field_update() because _field_invoke() did recognize 'en' as an available language.

The real bug here and the ultimate result is that only nodes that have 'und' (no language) would be importable by the nodewords upgrade.

Solutions
One hypothetical solution would be to set the field as translatable by default and perhaps then turning on something like the "content translation" module would allow the import to complete.

The solution I utilized was to set all of my nodes languages to 'und' by executing the following query:
UPDATE `node` SET `language` = 'und';
but of course, this is not an acceptable solution if you have nodes in more than one language.

valthebald’s picture

#14: thanks a lot, that's really helping comment!
I will investigate the issue, since I get lot of complaints that import is not working (while it works fine for me)

valthebald’s picture

Status: Active » Closed (duplicate)

I try to minimize number of open issues, let's have further discussion at #1386438: Importing from D6 Nodewords fails

justindodge’s picture

This is definitely not a duplicate of the #1386438: Importing from D6 Nodewords fails - the issues are quite different in their nature. I highly recommend leaving them both open and treating them distinctly.

valthebald’s picture

Version: 7.x-2.3 » 7.x-2.x-dev
Status: Closed (duplicate) » Fixed

Please try the latest 2.x-dev or forthcoming 2.4 release

Status: Fixed » Closed (fixed)

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

subhojit777’s picture

Status: Closed (fixed) » Active

I cannot upgrade from nodewords. I am getting this error:

FieldException: Attempt to create field name meta_revisit_after which already exists and is active. in field_create_field() (line 85 of /var/www/hcl/docroot/modules/field/field.crud.inc).

Tried with 7.x-2.7 version and 7.x-2.x-dev version of this module.

valthebald’s picture

working on it right now

federico’s picture

Hi,

I've just updated a website from d6 to d7 and I'm not able to update from nodewords. My site is in Spanish (using locale module) the import looks like it's running but only 4 nodes get meta tags. The import says:

Converting metatags for 2723 nodes
5445 results processed in 28 iterations.

SELECT * FROM `field_data_meta_description`

edit entity_type bundle deleted entity_id revision_id language delta meta_description_metatags_quick
edit node page 0 124 124 und 0 description sample  

I'm using metatags_quick 7.x-2.7 and I'm coming from nodewords 6.x-1.14

No dblog errors are shown after "import".

Thanks

siramsay’s picture

using #14 and setting all languages to und worked for me.
version metatags_quick 7.x-2.7

luckily my site is only English (before I make it bilingual)

manuel.adan’s picture

Issue summary: View changes

This is an old bug (almost 3 years). In the meantime, multilingual websites administrators will appreciate a note in project page information indicating that upgrade from D6 nodewords is not available for multilingual websites.

astonvictor’s picture

Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.