I have the same problem in Umrbraco v6.1.3. Does someone know if there is a solution for this?

thanks
 

Same in 6.1.6... Any solution?

Hi I´m running Umbraco v6.1.6 (Assembly version: 1.0.5021.24867) and i can´t get the Cogworks - Flexible Navigation to render.

Here is the debug result, it looks like it should work.

Any ideeas..

René

Hi, I've got exactly the same problem as René. It would be really great if someone (from Cogworks?) could help us with this critical problem.
Thanks
/Jan

Its really strange since its pure xslt, and as far as i know there hasn't been any change to xslt in V6?!?!?!

Hi

I have been looking at this and it is a bit strange.

When i Visualize XSLT - Cog Navigation it works

Any ideas???

Rene

Hi again

It is a bit strange. Here is the output from the Cog Navigation, I do not know where the div come from.

<div title="Macro Tag: '[COG]Navigation'" style="border: 1px solid #009;"></div>

Here is the markup for the macro

<umbraco:Macro 
        startingLevel="0" 
        recurse="1" 
        selectBranches="1" 
        maxMenuDepth="99" 
        ulBaseClass="nav" 
        branchClass="" 
        selectedClass="current" 
        forceNode="" 
        expandChildren="1" 
        forceHome="1" 
        securityTrimming="1" 
        Alias="[COG]Navigation" 
        runat="server">
        </umbraco:Macro>    

I have tryed to uninstalle Cog Navigation and install again.

Here is the information from the CogWorks Navigetion

Package name Cogworks - Flexible Navigation Package version 1.0 Author Tim Saunders Package repository Umbraco package Repository Package readme This is the Umbraco 4.5+ version. it contains support for the new 4.5 schema.

Any suggestions?

Kindly René

Hi again 

Now i have tryed on a new install of Umbraco 6.1.6 - With the same result.

Any ideas would be great.

A simpel demo with 3 menues, all XSLT

• Cog Menu
• Level 1 menu
• Level 2 Menu

The content three

The XSLT Files

This is the source view off the simple site (Nothing for Cog navigation) - The other 2 XSLT Navigation is rendered fine

Any Ideas

Have a nice sunday

René

Hi René,

I noticed above that you had startingLevel to zero — that will not render any menus, since there is no level zero node in Umbraco (<root> is level="-1" and top-level nodes are at level="1")

I'm plowing through the XSLT to see if I can find anything that would cause the problems others are having here...

/Chriztian

Hi Chriztian

I have tested with level 1 and -1, nothing renderes in the COG Menu

Here is the out put with level 1 (Nothing rendere)

   <umbraco:Macro 
        startingLevel="1" 
        recurse="1" 
        selectBranches="1" 
        maxMenuDepth="99" 
        ulBaseClass="" 
        branchClass="" 
        selectedClass="" 
        forceNode="" 
        expandChildren="1" 
        forceHome="1" 
        securityTrimming="1" 
        Alias="[COG]Navigation" 
        runat="server">
    </umbraco:Macro>

Here is the output with level -1

<umbraco:Macro 
        startingLevel="-1" 
        recurse="1" 
        selectBranches="1" 
        maxMenuDepth="99" 
        ulBaseClass="" 
        branchClass="" 
        selectedClass="" 
        forceNode="" 
        expandChildren="1" 
        forceHome="1" 
        securityTrimming="1" 
        Alias="[COG]Navigation" 
        runat="server">
    </umbraco:Macro>

Hi 

Is there anything new on this one. 

Chritzian, could you produce the error?

René

Hi Rene

Have you tried setting the variables in the xslt manually to see if it works?

Replace macro/startingLevel with 2, macro/recurse with 1 etc.

Cheers

Rob

Hi Rob 

I have tried and it works. 

Now the navigation is rendered, so there is som troubles with umbraco and getting the data from the macro.

<!--This sets the level that the nav starts at and tells us if we should recurse through child elements-->
<xsl:variable name="startDepth" select="1" />
<xsl:variable name="recurse" select="1" />
<xsl:variable name="selectBranches" select="1"></xsl:variable>
<xsl:variable name="maxMenuDepth" select="99"></xsl:variable>
<xsl:variable name="forceNode" select="0"></xsl:variable>
<xsl:variable name="walkChildren" select="1"></xsl:variable>
<xsl:variable name="forceHome" select="1"></xsl:variable>
<xsl:variable name="securityTrimming" select="1"></xsl:variable>
<!--Alternate page title variable in here-->

<!--Styles for the navigation-->
<xsl:variable name="ulBaseClass" select="0"></xsl:variable>
<xsl:variable name="branchClass" select="0"></xsl:variable>
<xsl:variable name="selectedClass" select="0"></xsl:variable>

<p> ---- MENU COG START ---- </p>
<ul class="0 lv1">
<li class="0 hasChildren"><a href="/" class="0">page1</a></li>
<li class="hasChildren"><a href="/1.aspx">1</a><ul class="lv2">
    <li class="hasChildren"><a href="/1/11.aspx">11</a><ul class="lv3">
        <li><a href="/1/11/111.aspx">111</a></li>
        <li><a href="/1/11/112.aspx">112</a></li>
</ul>
</li>
<li><a href="/1/12.aspx">12</a></li>
<li><a href="/1/13.aspx">13</a></li>
</ul>
</li>
<li><a href="/2.aspx">2</a></li>
<li><a href="/3.aspx">3</a></li>
<li><a href="/4.aspx">4</a></li>
<li><a href="/5.aspx">5</a></li>
</ul>
<p> ---- MENU COG END ---- </p>

<p> ---- MENU LEvel 1 STANDARD START ---- </p>
<ul><li><a href="/1.aspx">1</a></li><li><a href="/2.aspx">2</a></li><li><a href="/3.aspx">3</a></li><li><a href="/4.aspx">4</a></li><li><a href="/5.aspx">5</a></li></ul>
<p> ---- MENU STANDARD END ---- </p>
<p> ---- MENU level 2 STANDARD START ---- </p>
<ul />
<p> ---- MENU STANDARD END ---- </p>
Page 1
A

Rene

Hi there,

I had this same issue and was able to get the menu to work by changing the [COG]Navigation.xslt file:

Before:

<xsl:choose>
<xsl:when test="$forceNode">

After (this works for me):

<xsl:choose>
<xsl:when test="$forceNode > 0">

Seems the simple first test to check for a value is always returning true for me. When I tested to make sure it was a value above 0 (which it would need to be in order to be an actual node) it worked like it was before I upgraded to version 6.1.6.

Cheers,

phill

OK, that really starts looking as if there's been a change in the way the <macro> document gets created from the parameters. Especially it seems that unspecified parameters are converted into either zero or some kind of 'null' string... (Otherwise, the simple test="$forceNode" wouldn't return true())

Could you (René and Phill) try the age old copy-of trick to get some data for us? That is, setup the macro as you usually do with some parameters not specified (e.g. leave the forceNode - aka "Selected Page" - param empty), then do this inside the root template (<xsl:template match="/">) before everything else:

<textarea rows="8" cols="40"><xsl:copy-of select="/macro" /></textarea>

I'm very curious as to see what gets in there for the missing parameters...

/Chriztian

UPDATE: Added UI name of the forceNode param

Hi Christzian

Here is the output.

<macro>
<startingLevel>1</startingLevel>
<recurse>1</recurse>
<selectBranches>1</selectBranches>
<maxMenuDepth>99</maxMenuDepth>
<ulBaseClass></ulBaseClass>
<branchClass></branchClass>
<selectedClass></selectedClass>
<forceNode></forceNode>
<expandChildren>1</expandChildren>
<forceHome></forceHome>
<securityTrimming>1</securityTrimming>
</macro>

This is the settings

   <umbraco:Macro 
        startingLevel="1" 
        recurse="1" 
        selectBranches="1" 
        maxMenuDepth="99" 
        ulBaseClass="" 
        branchClass="" 
        selectedClass="" 
        forceNode="" 
        expandChildren="1" 
        forceHome="" 
        securityTrimming="1" 
        Alias="[COG]Navigation" 
        runat="server">
    </umbraco:Macro>

Hi René,

Thanks - I've been debugging a little myself, and I've tried this on an older 4.11.x version - the problem is that empty parameters are now always present in the macro XML - whereas, in the older versions, they only ocurred if they had an actual value - before, if you had an empty string, it wouldn't add the

So the way we usually have been checking this in XSLT was to just look for the node - now, it seems that the XSLT needs to be updated to make sure there's an id in there... the test="$forceNode > 0" as Phill suggested will do that - best option would probably be to refactor some of the code to do all the conversions in the variables section to make the variables act like they did before, but depending on how they're used throughout the code that needs to be tested a little more.

/Chrizitan

is working on a reply...