I am unable to get the "description" metatag to appear in the HTML source of the home page or other node pages. The "keywords" metatag seems to work, but not the "description".

This has been tested and confirmed using simplytest.me with the WetKit 1.0 distribution.

See screenshots of the Metatags configuration page where I have set the description and keywords, then see the attached source code from the frontpage that shows the keywords being rendered, but not the description.

I tried to get the description and keywords to appear on a regular node, but the same thing happened - keywords work, description does not.

NOTE: The dcterms.description (Dublin Core description) appears, but I believe the GC needs the main "description" metatag to work as well.

Comments

jayson’s picture

Attached files.

joseph.olstad’s picture

Assigned: Unassigned » joseph.olstad
Status: Active » Patch (to be ported)
StatusFileSize
new2.95 KB

Jayson and I did a bunch of peeking and prodding and came up with this patch:

with this patch the description metatag works.

I'm not sure on the history of this issue or why it is the way it is, but we have a client that wants this to work and we checked HTML5 specs, there's nothing in the HTML5 spec that says that we can't use the "description" metatag.

Tested vs wetkit distribution 1.x DEV.

Patched vs 1.x DEV

We'd like this to get looked at asap so that we can get approval and then backport it to "pre-rc2" as a stop-gap until we go live with our v1.0 upgrade/update

joseph.olstad’s picture

StatusFileSize
new2.86 KB

A cleaner version of the above patch.

Our client is waiting for us to provide a solution. If they want us to implement this we'll have to backport this to a pre-rc2 release of the distro. It seems to affect all versions including v1.0 back through to rc2 and back further than that prior to rc2.

This was patched against 1.x dev, it should work on v1.0 as well.

any objections/suggestions/comments?

sylus’s picture

Status: Patch (to be ported) » Fixed

Looks good, brought back the unset so token browser won't appear as represents a UX fail and devel/token works better. Additionally just pointed to improved_summary rather then duplicating.

Thanks!

Commited: http://drupalcode.org/project/wetkit_metatag.git/commit/5cf0580

Status: Fixed » Closed (fixed)

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