Hi
Do you also see this?
Actually i was facing this problem so I asked Sachin about the issue.

Now if you see in the page.xsl file of the publication, it contains a tag for title: -

<title><meta:value element="title" ns="http://purl.org/dc/elements/1.1/"; default="default"
         i18n:attr="default" uuid="{$uuid}" lang="{$language}"/></title>

Which fetches the title entered from the CMS. I have used the same and changed the value to description like this: -

<meta:value element="description" ns="http://purl.org/dc/elements/1.1/"; default="default"
         i18n:attr="default" uuid="{$uuid}" lang="{$language}"/>

And description starts coming as a text on the webpage but meta description tag should be like of this

<meta name="description" content="{should come from CMS}">

Please let me know if i am not clear.

Regards
Gaurav



Vik Tara wrote:
Gaurav Kalia wrote:
Hi Vik

I have tried this in both the publications (default and defaultfiredocs)
and i couldn't find the description tag in the source code of the Page.

I spoke to Sachin regarding this earlier - he told me that the source
does contain the text, but not as a meta description tag.

Do you also see this?

Regards
Gaurav


Vik Tara wrote:
Have you tried this with 2.0.3 using the default publication?

Would be useful to know if this problem relates to the firedocs
publication or not.


Vik

Gaurav Kalia wrote:
Hi All

I want to add Meta Description tag in my website. I have added the
description from the CMS successfully and published the page again but
the Meta Description tag is not coming in the source code of my website.

I am using Lenya 2.0.3 with Firedocs.

Please Help


Regards
Gaurav

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to