This feature has been proposed by hass and other user two days ago. There are node types without body, neither teaser (eg. items in e-shops). I really love this one!

Comments

hass’s picture

hass commented

+

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Use configurable field in node types for DESCRIPTION Meta tag, (other tags also?) » Use configurable field in node types for meta tag DESCRIPTION Meta tag, (other tags also?)

What is the difference between this feature request, and #670802: Create a module that changes the default values on a content type base?
As far as I can understand, once that #670802: Create a module that changes the default values on a content type base would be implemented, there would be a value for the meta tag DESCRIPTION that depends from the content type too.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)

I forgot to change the status.

ilo’s picture

ilo commented

Hi Kiam.. #670802: Create a module that changes the default values on a content type base provides different meta tag configuration for content type: enabling or disabling them, but from the availability point of view.

This issue request the feature where each meta tag is linked with a field of the content type, so not only description meta tag can be enabled per content type, also in one case, Description meta tag is just the body or the teaser of the node, but in other content type it is a cck field, not the body (content types without body are allowed).

I'm not changing the status, I wait for you to do so ;)

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Use configurable field in node types for meta tag DESCRIPTION Meta tag, (other tags also?) » Use configurable field in nodes for meta tag DESCRIPTION (other tags also?)

I thought I wrote a different title, but it seems I partially corrected. I changed the title to better reflect what the feature request is.

As Nodewords 6.x-3 already supports tokens, isn't this feature already possible? The support for tokens is not enabled for all the meta tags (it is not enabled for the meta tag REVISIT-AFTER as there isn't a token that returns an integer), and it could be extended for all the meta tags.
We should also verify if there isn't a token that returns the teaser of a node; in the case there isn't such token (I mean a token as supported by token.module), then Nodewords could implement it. In the case there is a module that implements a similar token, then Nodewords could detect it, and avoid to add its own version of the token.

summit’s picture

summit commented

Subscribing, token support should be great for "other pages" using wildcards and tokens makes flexible system! I am on Nodewords 1.9/1.10. will switch to 3.dev if stable release.

greetings,
Martijn

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Postponed (maintainer needs more info) » Closed (duplicate)

@Summit: Branch 6.x-3 is not stable; that is the reason it is not shown in the project page.

Description meta tag is just the body or the teaser of the node, but in other content type it is a cck field, not the body (content types without body are allowed).

Once that the default values per content-type will be introduced, it will be possible to use a token to populate the content of a meta tag with the content of a CCK field.

I am marking this feature request as duplicate of #670802: Create a module that changes the default values on a content type base.

Andrew Gorokhovets’s picture

Andrew Gorokhovets commented

+1

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
Version: » 6.x-1.x-dev

v6.x-3.x is not supported, moving this to 6.x-1.x.