adding meta robots in head

Hello,
I need to add the metatag ROBOTS (for example META NAME="ROBOTS" CONTENT="INDEX,FOLLOW"
) in the head tag in some .page that I create using LiveSite 3.1.
Is it possible and how can I do it?

Thank you,
Elena

Find more posts tagged with

Comments

vpatel

You can use page context mechanism to do this.

PayalGarg

What I've tried is adding meta tag "keywords" using context. i.e.

[html]context.getPageScopeData().put(RuntimePage.PAGESCO PE_KEYWORDS, "abcccc");[/html]

To add your own meta tags then we can try something like this in your externals:

[html]context.getPageScopeData().put(RuntimePage.PAGESCO PE_HEAD_INJECTION, "<meta name=" + " />");[/html]
This will add a meta tag in the head section of the .page file. But I'm not pretty sure about the approach. Please share your thoughts.

vpatel

That should work. Alternatively, you could define "put" data into page scope and then update your page layout XSL to retrieve and display them. I would use what you have at the moment -- just personal preference.

fiquebem

That should work. Alternatively, you could define "put" data into page scope and then update your page layout XSL to retrieve and display them. I would use what you have at the moment -- just personal preference.

We have TS 7.2.1. We're using SitePublisher to generate HTML (we're not using any runtime modules).

We have a custom page type and a custom page layout XSL stylesheet. We, too, are interested in injecting custom "meta" fields in the < head > section of the generated HTML file.

How can we "put" data from a component into the $PAGE_SCOPE token, so another component (or the containing page layout XSL) can get that data via $PAGE_SCOPE[custom_name]?

Our alternative is to create a "meta-data" component with Appearance XSL that generates code such as:

< customMetaTags >
< meta name="robots" > ... < /meta >
< /customMetaTags >

Then use the page layout XSL to retrieve and render that element in the < head > section. Right?

Thanks,

S.

fiquebem

Our alternative is to create a "meta-data" component with Appearance XSL that generates code such as:

< customMetaTags >
< meta name="robots" > ... < /meta >
< /customMetaTags >

Then use the page layout XSL to retrieve and render that element in the < head > section. Right?

Unfortunately, I wasn't able to render the "customMetaTags" element from the fixed-layout XSL file we're using. XSL is a struggle for me. Anyway, unlike "/Page/ComponentData/Component," the following doesn't seem to select anything: "/Page/ComponentData/Component/customMetaTags."

It appears that "customMetaTags" is not part of the XML document tree being passed to the layout stylesheet, even though an "XML dump" (printed from the layout stylesheet) seems to include the < customMetaTags >.

In the component Appearance XSL, I have the following:

< xsl:element name="customMetaTags" >
< meta name="robots" > ... < /meta >
< /xsl:element >

But no ... from the layout XSL, I can't seem to be able to stuff the contents of "customMetaTags" into the HTML header section.

Ideas?

Thanks,

S.

tec_iwov

The page layout is indipendent from component transformation.

IT only lays out the component geometries. you need to use the page scope data and tokens do do this. Since your using a custom layout you can add all the custom page scope tokens the string that's between [] is the key used to inject the data.

follow the code example above within your component or a precontroller
look in the div-layout-page.xsl and you'll see

ls:begin[head-injection]
$PAGE_SCOPE[head_injection]
ls:end[head-injection]

fiquebem

... follow the code example above within your component or a precontroller ...

Many thanks for your help!

We need authors to input meta-data for the HTML < head > section. So I should create an External component which passes the user input as Parameters to a custom Java class, right?

However, since we don't have a LiveSite runtime environment (except for the one built into the Preview functionality within TS), I'm not sure the aforementioned Java class will be instantiated and executed properly (during the "Generate HTML" task). Will it?

Thanks,

S.

tec_iwov

Yes Generate HTML will execute your externals and since it's a run once Paradigm, That is that head data doesn't change different request of the same page it should work OK.

fiquebem

Yes Generate HTML will execute your externals and since it's a run once Paradigm, That is that head data doesn't change different request of the same page it should work OK.

Many thanks; I got it working -- my 1st External component. Yippee!

I didn't even install the Eclipse IDE. I simply dropped my Java source class under livesite_customer_src/src and run livesite_customer_src/build.bat.

Regards,

S.