It could be very useful if the http://drupal.org/project/nodewords module could be supported.

Many thanks!

Comments

jamesoakley’s picture

jamesoakley
Primary language English
Location North Yorkshire, UK
commented

Yes: I'd love that feature too!

Specifically, in the "map file columns" stage, (stage 4 of 8), could we have two more Content Field entries for Meta Tags description and Meta Tags keywords. That way, the user can assign which data column to map to the key nodewords properties. I suppose it could be possible to add other Nodewords fields like Copyright etc., but that would complicate things somewhat.

To do this properly, it would probably be necessary to check the variable that reveals whether these Meta Tags attributes are meant to be editable at a node level, as set at /admin/content/nodewords.

rickherman’s picture

rickherman commented

I agree Nodewords support would be beneficial to bulk upload description meta tag data. However, failing that is there anyway to map an import field to the description meta tag field presently without Nodewords access?

finex’s picture

finex commented

Actually, If someone needs to import meta tags, I suggest to import the node contents (except the meta tags) and, when the nodes are imported, do a manual SQL query to add
the meta tags to the nodewords tables. This operation needs basic SQL skills and the problem can be easily solved.

@rikherman: of course, but you have to hack your template for printing it... I've done it, but I advise against it: it is difficult to mantain and, if you have nodewords installed for managing other meta tags, is really difficult to make the two solutions coexist. Otherwise you could check if nodewords is supported by rules module, in such case you could fill the cck field with nodeimport and with rules you could migrate the data to the meta tags and after you can remove the cck field... only if nodewords is supported by rules.
The easiest solution is the SQL query... (or implementing nodewords support to node import, of course) :-) :-) :-) :-) :-)

Protean’s picture

Protean commented

Maybe it's possible to solve the part of problem...

How to import meta description field only?

Table of nodewords has fields:
mtid (auto_increment), type, id, name, content

For our task we have:
mtid = auto_increment
type = NODEWORDS_TYPE_NODE = 5
id = $node->nid
name = "description"
content = serialize("text_of_meta_description");

That's all.

I'd tried write nodewords.inc for this task only, but I don't understand how function nodewords_node_import_fields must works :(

Can anybody help?

ben22’s picture

ben22 commented

Hi,
I have found that this module works really well. On drupal 5 the keywords and description for a cck import could be allocated to the nodewords module, but for some reason that is not possible in drupal 6. Is there a quick fix (i.e copy and pasting code, if so which files? ) to this or is the architecture of the module completely different?
Thanks
Ben

Robrecht Jacques’s picture

Robrecht Jacques commented
Version: master » 6.x-1.x-dev

The architecture of the nodewords module is completely different in 6.x-3.x - nodewords support in node_impot 5.x was for something similar to nodewords-6.x-1.x which is no longer supported.

Also, node_import has changed somewhat between 5.x and 6.x that a simple copy of nodewords.inc would not even work for nodewords-6.x-1.x (although it could be used as a base).

anonymous07’s picture

anonymous07 commented

Subscribe ... yet another change between D5 and D6 that I am trying to resolve.

CarbonPig’s picture

CarbonPig commented

Bump! This is exactly what I'm looking for too! I would be willing to chip in a few bucks if someone can help make the keywords and description field play nicely btwn node import and nodewords!

Please contact me if there is interest.

Cheers,

CarbonPig

pritam-osl’s picture

pritam-osl commented

I support what FiNeX has said. I is better to import all the other node field and then insert the all meta tags in nodewords table using simple SQL.
Table of nodewords has fields:
mtid (auto_increment), type, id, name, content
nodewords stores multiple entries for a single ID. It has individual entry for meta tag field. I am also trying to write a patch for it, will commit if successful.