Hi Nergal,

Did you set any hostnames on your nodes via right-click -> Manage Hostnames? In your web.config file to what value is the 'umbracoHideTopLevelNodeFromPath' set?

Do you mean by assigned that on the properties tab for the first subnode you get the wrong url displayed under 'Link to document'?

What happens if you republish the entire site (right-click on top node -> 'Republish entire site')?

Sascha

Hi,

I register 2 hostnames for that page.

the value for umbracoHideTopLevelNodeFromPath is true

yes, on the properties tab there it gets shown with /main/home.aspx and in my navigation-xslt

If I republish the singel site or the entire site I get the correct url. But after a while it returns to /main/....

Thank You :)

Cheers Nergal

If you like to, I could give you access to my umbraco installation so you can have a closer look.

For the moment I would be very happy with a workaround :) Any ideas?

I can have a look if you like, though I doubt I can do much but it can't hurt either I guess. Feel free to send me the login details to sascha at publiczone.co.uk. Installing the formidable Config Tree package by Tim would be a good idea as well.

The only thing I can think of for a work around would be to use the xsl replace function whenever you are creating links via xslt, e.g.

<a href="{Exslt.ExsltStrings:replace(umbraco.library:NiceUrl(@id), 'main/', '')}">somelink</a>

You can also create a global xslt file and create a new template in there which you can call then whenever you create a link:

<xsl:template name="CreateLink">
  <xsl:param name="id">
  <xsl:if test="$id != ''">
    <a href="{Exslt.ExsltStrings:replace(umbraco.library:NiceUrl($id), 'main/', '')}">somelink</a>
  </xsl:if>
</xsl:template>

Wherever you want to use this you need to add and import (or include) statement like so:

<xsl:import href="../xslt/Global.xslt" />

You can then call the template as if it were in your current xslt:

<xsl:call-template name="CreateLink">
  <xsl:with-param name="id" select="@id" />
</xsl:call-template>

It's not ideal but should work for link creation and as long as the page is actually accessible under /home.aspx.

Sascha

I can confirm this issue.

I have a website with just one root node, and assigned a host name for the root node.

Home
- Products
- - Car

Sometimes the NiceUrl property includes the urlname of the root node, where www.domain.com/products/car becomes www.domain.com/home/products/car

It is quite annoying :-)

umbracoHideTopLevelNodeFromPath is true

useDomainPrefixes is true

I have no idea how to work around this other than writing my one GetNiceUrl method to replace the urlname for the root node before returning the url.

/Dennis

I got the very same issue with version 4.5.1. I have no workaround either. i have installed Ucomment and the list of comments also share the same bug. PLEASE HELP fixing this.

im running 5 sites with subdomains prefix set to true, and this just comes up randomly, but only on subnodes.

Og hej Dennis, håber alt er vel, er lige blevet Level2 certificeret. Hilsen Bo/Synergi1.dk

Found a simple XSLT workaround, NOT elegant, and can be heavy when referencing many nodes, but nontheless, it works :-)  

Just add "?debug=whatever" to your url to see it in action and to simple debug

    <xsl:variable name="node" select="$currentPage/@id" />
    <xsl:variable name="topnode" select="$node/ancestor-or-self::node[@level = 1]/@urlName" />
    <xsl:variable name="fullpath" select="umbraco.library:NiceUrlFullPath($node/@id)" />
    <xsl:variable name="newpath" select="umbraco.library:Replace($fullpath, concat('/', $topnode,'/'), '/')" />

    <xsl:if test="umbraco.library:Request('debug') != ''">
      node<textarea><xsl:value-of select="$node" />&nbsp;</textarea><br />
      topnode<textarea><xsl:value-of select="$topnode" />&nbsp;</textarea><br />
      fullpath<textarea><xsl:value-of select="$fullpath" />&nbsp;</textarea><br />
      newpath<textarea><xsl:value-of select="$newpath" />&nbsp;</textarea><br />
      <hr/>
    </xsl:if>

<a href="{$newpath}">your working url</a>

You can use it the same way, as Sascha Wolter proposed

is working on a reply...