It seems silly that there's no way to assign defaults for individual content types, as currently provided by the Meta tags Node Type module.

Comments

DamienMcKenna’s picture

Title: Merge nodewords_nodetype module's functionality » Allow defaults to be defined per content type
Dave Reid’s picture

Yep, would be excellent

DamienMcKenna’s picture

Lets add this to the next release.

DamienMcKenna’s picture

De-tagging, will review priorities after the next stable release.

Danny Englander’s picture

Component: User interface » Tag output

This sounds like a great feature if it were added. My use case is that I have a content type called "Products" so it would be ideal if I could simply set a default token for a CCK field on that content type's meta description. For example, I could use the cck text token [field_short_product_description-raw] for my meta description globally for the Proudct's content type. It would be a nice "set it and forget it" thing to have. I envision this working like the Page Title module for Drupal 6 where you can set defaults per content type using tokens.

I can offer to sponsor this feature if that's within the realm of possibility.

Danny Englander’s picture

Oops sorry it looks like I may have changed the component setting on this by accident but I am not sure. Still having some weirdness with OS X Lion scrolling and mouse.

DamienMcKenna’s picture

DamienMcKenna’s picture

DamienMcKenna’s picture

This won't be added to v1, but it will be added to v3: #2274037: Plan for Nodewords v6.x-3.0 release