Migration presentations Web Publisher 6.5 SP1 to Web Publisher 6.5 SP5

Hello,

I am migrating from 6.5 SP1 to WP WP 6.5 SP5 and I have a problem with my WP 6.5 SP5 presentations, these presentations work well in WP 6.5 SP1, encoding en_US ISO-8859-1, but I found that in WP 6.5 SP5 does not work when the content has special characters (accents, ç), if the content has no special characters is fine. There is no error in the presentation.

I have enabled the trace in WP and I get very little information about the error:
February 14, 2012 13:36:52,949 DEBUG [Timer-39] com.documentum.wcm.servermethod.WcmServerSideUtilActionHandler - ExecuteAction: Error = [9115] Error when calling the utility of Content Server: [ID = 0901cf3580369f48, exception =]
[ID = 0901cf3580369ed1, exception =]
.
February 14, 2012 13:36:52,949 DEBUG [Timer-39] com.documentum.wcm.servermethod.WcmServerSideUtilActionHandler - WcmServerSideUtilActionHandler: stack trace = WcmException :: THREAD: Timer-39, MSG: [9115] Error when calling the usefulness of content server: [ID = 0901cf3580369f48, exception =]
[ID = 0901cf3580369ed1, exception =]
., ErrorCode: 239b; NEXT: null

How I can solve it?

Please is urgent.

Find more posts tagged with

Documentum

Comments

kcrkarthik

Is the problem while storing the XML content into the repository or while transforming the xml using xslt?

if it is while storing the xml content to the repository, you will have to check the encoding on the content server.

try opening the xml content directly from the repository's file system and see how the special character is appearing.

-Karthik

Usuario

Hi Karthik,

The problem is that the transformation to html through presentation don't work when the content have special characters (accents, ç) in WP 6.5 SP5.

However the presentations run in WP 6.5 SP1 always and in WP 6.5 SP5 in content without special characters (accents, ç) also

Thanks

kcrkarthik

any errors you see in WP when trying to apply presentation?

are the 6.5Sp1 and 6.5 Sp5 two separate instances? if yes, make sure the encoding values are same in both.

or, is the 6.5sp1 and sp5 web publiser instances pointing to the same repository?

There is also a job that takes care of creating rendition. i guess it is Create Dynamic Content. is the html rendition getting created through that job? this might help you identify if the problem is when applying presention through application server (WP) or at the repository level also (thru method server).

-Karthik

Usuario

I have a repository with WP 6.5 SP1 everything works fine.
Now I'm moving to WP 6.5 SP5, so good except the presentations that do not work with files with special characters, but if you work with content that is not special characters.
The problem with xsl I'm sensing is that it will not let me make several call-template by passing a parameter whose content has special characters. Wonder the xsl processor not leave work by sending a parameter for different templates

example in my presentation:

<xsl:call-template name="az_META">

<xsl:with-param name="clave" select="info_buscadores/palabras_clave"/>

<xsl:with-param name="global_clave">general</xsl:with-param>

<xsl:with-param name="desc" select="concat(info_buscadores/descripcion,' ',titulo_contenido)"/>

<xsl:with-param name="idioma" select="$idioma"/>

</xsl:call-template>

[...............]

<xsl:template name="az_META">

<xsl:param name="clave"/>

<xsl:param name="global_clave"/>

<xsl:param name="idioma"/>

<xsl:param name="desc"/>

<xsl:call-template name="az_TRATARCLAVE">

<xsl:with-param name="clave" select="$clave"/>

<xsl:with-param name="global_clave" select="$global_clave"/>

<xsl:with-param name="idioma" select="$idioma"/>

</xsl:call-template>

<xsl:call-template name="az_TRATARDESC">

<xsl:with-param name="desc" select="$desc"/>

</xsl:call-template>

<xsl:call-template name="az_TRATARAUTOR"/>

</xsl:template>

Thanks

Usuario

Hi,

I think thats the problem is in the XML transformation engine, how can I look the character set to use in the XML transformation engine?

When I insert a link with 'ñ' in a content and I download the xml of the content WP 6.5 SP5 and see in my href link '%C3%B1'.

If I perform this same test in my old version WP 6.5 SP1 the href link is ok with 'ñ' without '%C3%B1'

thanks

kcrkarthik

Are you saying that the special character itself is not stored properly in the content xml? If yes, then the problem is at the repository level. Have you checked the encoding settings in the content server machine, the value set in the repository startup script and also the encoding set at database level.

The XML that you are mentioning, is it the orginal content's xml or the rendered XML?

-Karthik

Message was edited by: Karthik Chokkaraman

Usuario

Hi Karthik,

Yes, the problem is that the special character itself is not stored properly in the content xml.

I have reviewed the configuration of the machine is ISO-8859-1, but the parser and the XML transformation engine have UTF-8 engine

the xml and rule:

<?xml version="1.0" encoding="UTF-8"?>

<pagina>

[....]

The xsl:

<?xml version="1.0" encoding="utf-8"?>

<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns="http://www.w3.org/1999/xhtml">

<xsl:output method="xml" omit-xml-declaration="yes" indent="yes" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" encoding="ISO-8859-1"/>

Do you think all of this are correct for WP 6.5 SP5?

Thanks

kcrkarthik

What is the character set configuration on the environment where it is working fine? Did you compare that?

In your case, you dont have to worry about the XSL at this point of time, because the original content itself is not getting stored properly. If the original content is proper and the rendition is NOT proper, then XSL comes into picture.

-Karthik

Usuario

Hi,

Comment that we have tested to upload a template, presenrtacion (attached) and rule with head ISO-8859-1(<?xml version="1.0" encoding="ISO-8859-1"?>) and another with head UTF-8 (<?xml version="1.0" encoding="UTF-8"?>):

<page>    <link link="http://www.españaescultura.es/" texto="Enlace from textline" />    Text from <a href=" <text> http://www.espa%C3%B1aescultura.es/"> content </ a> </ text></page>

Presentation UTF-8

<?xml version="1.0" encoding="UTF-8"?><xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns="http://www.w3.org/1999/xhtml">    <xsl:output method="xml" omit-xml-declaration="yes" indent="yes" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" encoding="UTF-8"/>    <xsl:strip-space elements="*"/>    <xsl:param name="DMS_SESSION_ID" select="'default value'"/>    <xsl:param name="DMS_INPUT_OBJECT_ID"/>    <xsl:template match="/">        <xsl:apply-templates select="pagina"/>    </xsl:template>    <xsl:template match="pagina">        <html lang="{$idioma}" xmlns="http://www.w3.org/1999/xhtml" xml:lang="{$idioma}">            <head>                <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>            </head>            <body>                <div class="capaDocumentum">                    <div class="plantillaDestacado">                         <div>                            <xsl:element name="a">                                <xsl:attribute name="href"><xsl:value-of select="enlace/@link" ></xsl:value-of></xsl:attribute>                                <xsl:value-of select="enlace/@texto" ></xsl:value-of>                            </xsl:element>                        </div>                        <div><xsl:apply-templates select="texto"/></div>                    </div>                </div>            </body>        </html>    </xsl:template>    <xsl:template match="a|A">        <a href="{@href}"&gt;<xsl:value-of select="."/></a>    </xsl:template></xsl:transform>

Presentation ISO-8859-1

<?xml version="1.0" encoding="ISO-8859-1"?><xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns="http://www.w3.org/1999/xhtml">    <xsl:output method="xml" omit-xml-declaration="yes" indent="yes" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" encoding="ISO-8859-1"/>    <xsl:strip-space elements="*"/>    <xsl:param name="DMS_SESSION_ID" select="'default value'"/>    <xsl:param name="DMS_INPUT_OBJECT_ID"/>    <xsl:template match="/">        <xsl:apply-templates select="pagina"/>    </xsl:template>    <xsl:template match="pagina">        <html lang="{$idioma}" xmlns="http://www.w3.org/1999/xhtml" xml:lang="{$idioma}">            <head>                <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>            </head>            <body>                <div class="capaDocumentum">                    <div class="plantillaDestacado">                         <div>                            <xsl:element name="a">                                <xsl:attribute name="href"><xsl:value-of select="enlace/@link" ></xsl:value-of></xsl:attribute>                                <xsl:value-of select="enlace/@texto" ></xsl:value-of>                            </xsl:element>                        </div>                        <div><xsl:apply-templates select="texto"/></div>                    </div>                </div>            </body>        </html>    </xsl:template>    <xsl:template match="a|A">        <a href="{@href}"&gt;<xsl:value-of select="."/></a>    </xsl:template></xsl:transform>

I got the same problem coding 'ñ' to '% C3% B1' with two encoding.

And in none of the two tests was generated html, the content keeps red dot.

I think some encoding settings of WP is doing this does not work. Can the parser? How I can change it?

Thanks

kcrkarthik

Try this test and give me the results from both the environments.

1) create an xml content with special character

2) import that in both the environments

3) now, download the xml content (dont worry about xsl or rendition for now)

4) Does the special char appear properly or is it messed up? if so, is it in both or only one environment?

Next test

1) create an xml content with special character using API and not using Web Publisher

2) use apis to create a object and set content (try this from the content server)

3) now, download the xml content

4) Does the special char appear properly or is it messed up? if so, is it in both or only one environment?

This will tell you if the encoding issue is application server level (web publisher) or are repository-level itself.

-Karthik

Usuario

Hello,

Of the two problem, as identified in the SP5 version:

1. When you insert special characters on a content item content, saving the UTF-8 transforms, such as ñ =% C3% B1, and therefore the generated html special characters appears to UTF-8. It seems that happens in enough clients and occurs from the SP2, if not solved.

2. When you insert special characters in a TextLine content, this transformation to UTF-8 is not performed, but the content is saved with red dot, that is, not generated html, error processing, presentation fails. If the TextLine no special characters, the presentation works.
This problem we have found that adding the rule: encode = "false" and entering special characters in the content, the html is generated without problems.

</textline>

</tagattribute>