PAGESCOPE Insertion Control

ENV: TS 7.2.1 / Solaris

I'm attempting to use a site pre-controller to inject a DOCTYPE declaration into the page (site pages have been created in "htmlQuirks" mode).

I'm using the RuntimePage.PAGESCOPE_HEAD_INJECTION constant but the injection is in the head section (as advertised). Before I go down another path is there a value I can use to place it outside the leading html tag?

TIA

Find more posts tagged with

Comments

Samir_Friend

ENV: TS 7.2.1 / Solaris

I'm attempting to use a site pre-controller to inject a DOCTYPE declaration into the page (site pages have been created in "htmlQuirks" mode).

I'm using the RuntimePage.PAGESCOPE_HEAD_INJECTION constant but the injection is in the head section (as advertised). Before I go down another path is there a value I can use to place it outside the leading html tag?

TIA

If you want an HTML5 doctype, ask Autonomy for a patch.

For other doctypes, they are already configurable in the pagetype-config.xml in livesite_customer_src folder.

The header injection can insert only in the head of the html. If there's anything special you want to do with rendering all the pages, modify the rendering XSL for that page-type after taking a confirmation from Autonomy that it doesn't invalidate your support.

Rick Poulin

If you want an HTML5 doctype, ask Autonomy for a patch.

You don't need a patch. You can produce the "legacy" HTML5 doctype, by setting your pagetype-config.xml like this:

[PHP]
HTML 5

html

about:legacy-compat

html

text/html

true

[/PHP]
..which produces this, the w3c's accepted and documented html5 doctype declaration for legacy systems..

[PHP]

[/PHP]

Whether you're doing HTML5 or not, this file is the only supported place to change doctypes (indeed, the only way that even works for all use cases).

Samir_Friend

You don't need a patch. You can produce the "legacy" HTML5 doctype, by setting your pagetype-config.xml like this:

[PHP]
HTML 5

html

about:legacy-compat

html
text/html
true

[/PHP]
..which produces this, the w3c's accepted and documented html5 doctype declaration for legacy systems..

[PHP]

[/PHP]

Whether you're doing HTML5 or not, this file is the only supported place to change doctypes (indeed, the only way that even works for all use cases).

I think the HTML5 doctype mentioned by you is actually a workaround if I take a look at the valid doctypes by w3c: http://www.w3.org/QA/2002/04/valid-dtd-list.html. Though it works, but I would surely recommend going with the standard and not including an extra system identifier.

For HTML5 doctype, Autonomy already provides a QSU update which you just need to copy to your LSDS and bounce the server. No need to update the pagetype-config.xml as well. So if you have a support account, go for it.

If not, you can also change the fixed-page-layout xsl or any other xsl that you're using to render the pages and insert an xsl text element before the html tag for the doctype. But be cautious that it might invalidate your support.

HTH.

Rick Poulin

I think the HTML5 doctype mentioned by you is actually a workaround if I take a look at the valid doctypes by w3c: http://www.w3.org/QA/2002/04/valid-dtd-list.html. Though it works, but I would surely recommend going with the standard and not including an extra system identifier.

It's perfectly valid. Source: the W3C's HTML5 spec @ http://www.w3.org/TR/2011/WD-html5-20110525/syntax.html#the-doctype

Samir_Friend

It's perfectly valid. Source: the W3C's HTML5 spec @ http://www.w3.org/TR/2011/WD-html5-20110525/syntax.html#the-doctype

The page you've mentioned is actually 'a work in progress' written in a big red pop-up that you see on the page bottom when you open it. Also, if you read the full text, it says - "The DOCTYPE legacy string should not be used unless the document is generated from a system that cannot output the shorter string." FYI again - The patch provided by Autonomy CAN generate the shorter string. So again - the doctype mentioned by you works but things are relatively easy if you use what is provided by Autonomy rather than a workaround for which, I am sure you understand the reasons.