Node meta tag description does not correctly work

I've got this issue as well. The meta keywords are there on the pages. However, the meta description entered doesn't appear in the page source.

Thanks!

@Summit: Some of the meta tags generation options (the ones that were present also in the content type settings page) have been removed.
Some users thought that changing those global settings would also change the content type settings, which was not true; the global settings were applied for the content type without specific settings (which means the Drupal variable nodewords_<setting>_' . $node->type was not set).

The content type settings are under /admin/content/types. On that page you see a table listing all the defined content types; if you click on edit, then you will see all the settings for that content type, including the ones added by Nodewords.

The code has been changed, and committed in CVS.

Thanks for your report.

I'm still experiencing this issue.

Tested with a fresh install of the Jan 5 dev release.

I'm aware of new settings and ensured these are as they should be.

The auto-generation of metatags for nodes is not working for me.

I have marked #674712: Problems with meta tag DESCRIPTION as duplicate of this report.

@redraven: You should describe better the issue you are having, as the meta tags generation works fine, for me.

I find a typo in the code, which has been fixed.

I'm sorry to reopen this issue but I am having this, or a related, problem with the latest official release of nodewords (6.x-1.11).

I am using a fresh installation of Nodewords, not an upgrade from a previous version.

I can manually edit description meta tags which then appear on nodes. I can also set default global description tags which appear. However, the auto generation of tags from node teaser does not seem to be working (this is a neccessity for my site as I have over 100k nodes). When this option is set the auto generated meta tag does not appear in any content except simple nodes (eg pages).

Is this related to the bug you have identified/ fixed above? If so, when do you expect to make a new official release that solves this problem? Or if it is completely unrelated please let me know if you want me to start a new issue and/or if you need any additional info.

Thanks very much for the module and for your help.

Hi,

The problem in dev version is the same that in version 1.11, ít's in function "nodewords_metatag_from_node_content" as I reported in "#674712: Problems with meta tag DESCRIPTION".
I've just test dev version with the same code that I found in comment #4 of that case to get the values of $node->teaser and $node-body and it works. But as I said before I'm not a Drupal coder so I don't know is this correct solution for this issue (don't know if this code affects other things in nodewords module).
Thanks for your help.

Julio

I'm sorry to reopen this issue but I am having this, or a related, problem with the latest official release of nodewords (6.x-1.11).

The issue reported here is present in version 6.x-1.11; that is the reason you find this problem in version 6.x-1.11. An official release cannot be changed, once released.

I am changing the referring version, so it is clear in which version the issue is first found. Clearly, if the issue is present in version 6.x-1.11, then the issue is also present in at least a development snapshot for the simple fact official releases are created from development snapshots.

I am marking this report as fixed because the code has been already changed in one of the latest commit I made in the development snapshot.

I'm opening this issue again because it remains unresolved and another similar issue has been flagged as a duplicate of this issue.

The autogeneration of node metatags is still not fixed in the most recent dev release (Jan 7)

Tested with a fresh install.

If a default description metatag is set, the autogeneration of node metatags based on node body does *not* function correctly.

If no default description metatag is set, the autogeneration of metatags works correctly, and are populated by node body.

Likewise, the 'other pages' metatags do *not* function correctly if a default description metatag is set, however, work as expected if no default metatag is set.

So it seems like there is something wrong with the inheritance/cascade of metatags if defaults are set.

The generation option description says Generate meta tag content when the meta tag content is empty, which is exactly what it does. If you don't enter a value for a node, then it is used the default value; if that value is not empty, then the meta tag content will not be generated.

I added a default value for the meta tag DESCRIPTION, and changed the meta tags values for the tracker pages; so far, I have not gotten anything wrong.

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <link rel="canonical" href="http://sunradio.local/dr61/tracker" />
<meta name="description" content="description: tracker page" />
<meta name="revisit-after" content="1 day" />
<meta name="robots" content="noarchive, nofollow, noindex, noodp, nosnippet, noydir" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

Even not setting a value for that meta tag, and letting the module use the default value doesn't create problems.

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <link rel="canonical" href="http://sunradio.local/dr61/tracker" />
<meta name="description" content="description: default description" />
<meta name="revisit-after" content="1 day" />
<meta name="robots" content="noarchive, nofollow, noindex, noodp, nosnippet, noydir" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

Likewise, the 'other pages' metatags do *not* function correctly if a default description metatag is set, however, work as expected if no default metatag is set.

If you are having a problem, then describe the steps necessary to reproduce it, the result you obtained, and the result you thought to obtain; saying it doesn't work doesn't describe anything; so far, I cannot reproduce the issue you are reporting.