Say you have a type called glossary that is presented in a view, the nodes that make up the terms do not need to have nodeword options. It would be nice if it could be turned on and off by content type.

Thanks for your consideration of this.

Comments

vm’s picture

vm commented
Version: 6.x-1.2 »
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Turn off for different content types » Add an option to disable the meta tags for specific content types
Version: » 6.x-1.x-dev
Status: Active » Postponed (maintainer needs more info)

What I understood is that, in the example you wrote, the content type glossary, which is listed in a view, should not have the nodewords options.

To disable the meta tags for a specific content type is a feature that finds my approval. I am not sure why somebody would not set meta tags for nodes that are listed in a view; this would mean to not have the meta tags when the nodes are shown.

Maybe there is a misunderstanding about how meta tags for views work. The meta tags for a view are not used for all the nodes listed in the view; the meta tags for a view are used when the view is visualized, while the meta tags for a node are used when the node is visualized.

If you still think that disabling the meta tags for a specific content type is a feature that should be added, let me know.

vsr’s picture

vsr commented

Thank you for your quick reply.

The thing is that here is no link to a node when using the views module. The term and the meaning are listed on the page with 24 other terms and definitions. I can think of other instances where it might not be appropriate. For instance, with quizzes the individual questions would not need the extra date. A custom content type of quotes, that has only the quote, who said it and the topic; and then presented on a topical page by using the Views Module. Maybe you would like to present nutritional information that the user can sort. This would require a custom content type and presenting it in a view. None of the added meta data would be needed.

The module is great, and for many content types it is good to have on by default. I just think that not all content types need to have the extra meta data.

Thank you for our time and a great module.

avpaderno’s picture

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

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

To say the truth, this feature was already implemented; I simply added code that doesn't return the meta tags set for a content type for which they are disabled.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Actually, a bug in the code didn't allow the feature to correctly work; I have fixed the problem.

Status: Fixed » Closed (fixed)

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