Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
There's a lot of overlap with the Integrated Metatags module, merge it in.
Comments
Comment #1
DamienMcKennaThe best approach might be to review the feature differences between the two modules and add separate tickets for each feature missing from Nodewords.
Comment #2
lpalgarvio CreditAttribution: lpalgarvio commentedIntegrated Metatags functionalities:
(aggregates data from all the tags added with the same name)
(on Global/Node Type; any tokens)
(on Node Type only; can fetch values from field_****.data, field_****.fid, field_****.list)
(on Global/Node Type; can fetch values from node.changed, node.comment, node.created, node.nid, node.promote, node.status, node.sticky, node.teaser, node.title, node.type, node.uid, node.vid)
(on Global/Node Type; can fetch values from term.*.name, term.*.tid, term.*.vid, term.*.vocab)
(on Global/Node Type; can fetch values from user.mail, user.name, user.signature, user.uid)
It does not however allow creating tags per NODE.
from the project page: http://drupal.org/project/int_meta
further comparison of both modules here - http://drupal.org/node/532278
Comment #3
lpalgarvio CreditAttribution: lpalgarvio commentedIMO, i don't think this should be taken in consideration for Nodewords.
The reason is that D7 is closing in, and with so much work going to be needed for this, possibly close to a rewrite, i think it's wiser that Metatags module for D7 should instead take this into account.
unless ofc the maintainer of Nodewords has lots of free time.
Comment #4
DamienMcKenna@LPCA: thanks again for your help.
One of the missing pieces is already listed as a separate issue (#945676: Allow defaults to be defined per content type), so I'm not sure how much functionality from int_meta is valid. Going to postpone this to deal with later.
Comment #5
lpalgarvio CreditAttribution: lpalgarvio commentedi've written additional information in a Metatags (D7) issue located here:
http://drupal.org/node/948102
Comment #6
Dave ReidI highly recommend we just merge in the default per content type variables feature, and everything else should be put back into metatags.module. If Damien agrees, we can just close this issue since 945676 and 948102 have been created.
Comment #7
DamienMcKennaOut of interest, does int_meta do anything with CCK that Nodewords' Token support doesn't cover?
Comment #8
lpalgarvio CreditAttribution: lpalgarvio commentedi think they don't cover exactly the same CCK information
Tokens at Nodewords default metatags is listing these for Page content type at my test site:
Integrated Metatags exposed these CCK:
field_****.data
field_****.fid
field_****.list
these are all relevant to ImageFields.
i haven't had the need to toy around with CCK, for example, with a Text Field.
Comment #9
Dave ReidNow that we have #945676: Allow defaults to be defined per content type filed there's no reason to keep this open. If file fields are missing tokens, then that should be filed against filefield.module, not nodewords.