Hi Henrik

I guess you have probably upgraded from an earlier version of Umbraco before 4.5?

There has been a change in the XML schema so that is probably why the XSLT does not render anything.

You can either alter the XSLT files to match the new schema or you can use the legacy schema in the umbracoSettings.config and you XSLT files will work again.

You can read more about the differences in the new schema here: http://blog.leekelleher.com/2010/04/02/working-with-xslt-using-new-xml-schema-in-umbraco-4-1/ (It's about 4.1 but this was renmaed to 4.5 before release)

/Jan

Hi and thanks...
I tried to change <UseLegacyXmlSchema>true</UseLegacyXmlSchema>
but nothings render...
It there anything more I can look at ?
/H

Hi Henrik

Did you refresh the XML chache afterwards? Otherwise you'll need to do this by going to the "Content" node in your content section and choose "Republish entire site".

Then the XML cache is refreshed and the settings should take effect. Otherwise try restarting the IIS site if it's possible.

/Jan

Hi and thank you very much for the help..
to bad nothings changes

Everythings looks good at backend

Down below there is an xslt example for topnavigation I have

It doesnt render at all

I have republish my site
I change this to true again true

*************************************************************************

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xsl:Stylesheet [ <!ENTITY nbsp "&#x00A0;"> ]>
<xsl:stylesheet
 version="1.0"
 xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
 xmlns:msxml="urn:schemas-microsoft-com:xslt"
 xmlns:umbraco.library="urn:umbraco.library"
 exclude-result-prefixes="msxml umbraco.library">

<xsl:output method="xml" omit-xml-declaration="yes" />

<xsl:param name="currentPage"/>

<xsl:variable name="level" select="2"/>

<xsl:template match="/">

<xsl:if test="count($currentPage/ancestor-or-self::node [@level=$level]/node [string(data [@alias='umbracoNaviHide']) != '1']) &gt; 0">
<ul id="secondLevelNavigation">
<xsl:for-each select="$currentPage/ancestor-or-self::node [@level=$level]/node [string(data [@alias='umbracoNaviHide']) != '1']">
 <li>
  <a href="{umbraco.library:NiceUrl(@id)}" title="Navigera till {@nodeName}">
   <xsl:if test="$currentPage/ancestor-or-self::node/@id = current()/@id">
    <!-- we're under the item - you can do your own styling here -->
    <xsl:attribute name="class">selected</xsl:attribute>
   </xsl:if>
   <xsl:value-of select="@nodeName"/>
  </a>
 </li>
</xsl:for-each>
</ul>
</xsl:if>
</xsl:template>

</xsl:stylesheet>

it was a relay bad example/wrong I Give you a new one later

I try to do a new topnavigation from the macro templates and not even that one render so something else is wrong
It comes to this line
<xsl:for-each select="$currentPage/ancestor-or-self::* [@isDoc and @level=$level]/* [@isDoc and string(umbracoNaviHide) != '1']">
no longer

/H

Hi Henrik

Everytime you change the value in the umbracoSettings.config be sure to update the XML cache or try restarting the application to make sure the changes take effect.

Now...what happens if you create a blank XSLT macro and place it in one of your templates, where you make a copy-of like this...

<textarea>

<xsl:copy-of select="$currentPage" />

</textarea>

Does it return anything? (Please notice I've omitted the template stuff etc.

/Jan

Hi
Yes it return alot of data...

Thanks

If I understand it right it is like this
my old xslt would work if I change<UseLegacyXmlSchema>true</UseLegacyXmlSchema>?
Otherwise I need to rewrite them ?

Can you give me a tip how this would look like ?

<xsl:for-each select="$currentPage/ancestor-or-self::node [@level=1]/node">
 <xsl:if test="string(./data [@alias='umbracoNaviHide']) != '1'"> 
|
<xsl:choose>
<xsl:when test="$currentPage/@level &gt; 1 and contains(concat(',',@path,','), concat(',',$currentID,','))">
<strong><xsl:value-of select="@nodeName"/></strong>
</xsl:when>
<xsl:otherwise>
 
<a href="{umbraco.library:NiceUrl(@id)}"><xsl:value-of select="@nodeName"/></a>

</xsl:otherwise>
</xsl:choose>
</xsl:if> 
</xsl:for-each>

/H

is working on a reply...