In versions 1.8 and 1.9 and Drupal 6.15 do not appear in the source code for custom node types keywords and description tags which I put on each node, when you edit are there, but when you see the notice in the source code are not. In story and pages are displayed correctly, but in the types of content I've created custom labels are not keywords and description.

In version 1.5 and earlier appeared correctly, that happened?

Configured Options:

- "Global keywords" is empty
- "Default values" and "Tracker pages" description and keywords are empty
- "Use the node teaser if the description meta tag is not set" is enabled

PHP: 5.2.10
MYSQL: 5.0.81

Comments

k74’s picture

k74 commented
Version: 6.x-1.9 » 6.x-1.11

I upgraded from version 1.9 to version 1.11 and the result is the same, in custom node types do not show the labels of "description" and "keywords" in the source code of the page

I activated the new options:

Generate meta tag meta tag content when the content is empty
Generate meta tags from the node teaser content, or the node teaser body when the node is empty

In node story and page functions properly, in custon node types not

A part of me, someone has got it all?

recrit’s picture

recrit commented

I had a similar issue. Did you set these options in the global settings or content type settings?
I had changed the global settings, but for some reason they did not propagate to my custom content type - you can check this under your content type settings. I found some content type specific variables in the variable table - it is something like nodewords_metatags_generation_method_{content_type}. Delete the content type variables and then the global settings will work.

avpaderno’s picture

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

@recrit: If you change the global settings, but you have set content type settings, then the module will use the content type settings. The global settings are used when the content type settings have not been set.

I think I will remove those global settings that have an equivalent setting for content types.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Not appear in the source code for custom node types keywords and description tags » Meta tags KEYWORDS and DESCRIPTION do not appear in the source code for custom node types
recrit’s picture

recrit commented

@kiamlaluno: thank you for the reply. I had upgraded to 1.11 and was playing around with the content type settings after which I just decided to use the globals -- however, as you stated, my content type settings stuck since they had been set.

avpaderno’s picture

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

@recrit: See #672346: Remove the settings that have an equivalent setting for content types.

k74’s picture

k74 commented

In the content type settings have the same options than in the global settings, these:

Generate meta tag meta tag content when the content is empty
Generate meta tags from the node teaser content, or the node teaser body when the node is empty

These options are propagate ok in content type settings when the change in global settings. Also only affect the tag of description and should not affect the keywords tag, no? and my two tags fail me. Not appear in the source code, not white, do not show these lines:

<meta name="keywords" content="
<meta name="description" content="
<meta http-equiv="pics-label" content="

But the lines of this tags appear:

<link rel="canonical" href="http://www.......
<link rel="meta" href="http://www.xxxxx.xx/labels.rdf" title="ICRA labels" type="application/rdf+xml" />
<meta name="copyright" content="......

The ICRA label is half, missing the line: <meta http-equiv="pics-label" content="

I see that as specified by the taxonomy of the content appearing or disappearing description tags, keywords and pics-label, if I choose the category of taxonomy that is assigned to custom content types tags disappear, if I select the generic taxonomy category appear the tag ¿? ¿? ¿? If I no select any category of taxonomy tags appear ¿?¿?¿?

[Edited by kiamlaluno to remove the bold style from a sentence]

avpaderno’s picture

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

In my test site I have two custom content type that I use to automatically create content with devel.module.
Checking the meta tags set for a node of those content type I see:

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="canonical" href="http://sunradio.local/dr61/la/node-175-test" />
<meta name="keywords" content="default, no-custom-page" />
<meta name="copyright" content="kiamlaluno" />
<meta name="description" content="default description" />
<meta name="abstract" content="abstract: default" />
<meta name="revisit-after" content="10 days" />
<meta name="robots" content="noarchive, nofollow, nosnippet, noydir" />
<link rel="shortcut icon" href="/dr61/misc/favicon.ico" type="image/x-icon" />

No one of the meta tags has the problem you reported.

avpaderno’s picture

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

I also enabled nodewords_extra.module, and I have not found any problems with its meta tags too.

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<link rel="schema.dc" href="http://purl.org/dc/elements/1.1/" />
<link rel="canonical" href="http://sunradio.local/dr61/la/node/175" />
<link rel="meta" href="http://sunradio.local/dr61/la/labels.rdf" title="ICRA labels" type="application/rdf+xml" />
<meta name="keywords" content="default, no-custom-page" />
<meta name="copyright" content="kiamlaluno" />
<meta name="description" content="default description" />
<meta http-equiv="pics-label" content="(pics-1.1 &quot;http://www.icra.org/pics/vocabularyv03/&quot; l gen true for http://sunradio.local/dr61/la/node-175-test r (n 0 s 0 v 0 l 0 oa 0 ob 0 oc 0 od 0 oe 0 of 0 og 0 oh 0 c 1))" />
<meta name="abstract" content="default content" />
<meta name="dc.title" content="Camur Vel Nimis Sagaciter" />
<meta name="revisit-after" content="90 days" />
<link rel="shortcut icon" href="/dr61/misc/favicon.ico" type="image/x-icon" />
k74’s picture

k74 commented
Title: Meta tags KEYWORDS and DESCRIPTION do not appear in the source code for custom node types » Meta tags KEYWORDS and DESCRIPTION disappear in the source code witch module Node breadcrumb

Ok, after many test, the problem no is in the custom node types, is with the module Node breadcrumb 6.x-1.0-beta6.

From that enable this module and configured it several rules for some of the terms used in the taxonomys. In the nodes that use the same terms of taxonomys configured in the Node breadcrumb module, these nodes disappear in Meta tags KEYWORDS and DESCRIPTION of the source code. If disable the breadcrumb Node module or remove the rule that they contain the term of the taxonomy, Meta tags KEYWORDS and DESCRIPTION reappear in the source code...

It's the fault of the module Nodewords or module Node breadcrumb?

Thanks!!

[Edited by kiamlaluno to remove the bold style from a sentence]

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Meta tags KEYWORDS and DESCRIPTION disappear in the source code witch module Node breadcrumb » Meta tags KEYWORDS and DESCRIPTION disappear in the source code when Node breadcrumb is enabled

I will check the code of the other module.

avpaderno’s picture

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

If Nodewords works when the other module is not enabled, then I would think the problem is with the other module, not Nodewords.

k74’s picture

k74 commented

ok, thanks, I created this Node breadcrumb issue -> #673276: Module Nodeword Meta tags KEYWORDS and DESCRIPTION disappear in the source code of the node when Node breadcrumb is enabled

Status: Fixed » Closed (fixed)

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