I'm using Path="/{0}/%" in an ASPX template (see the bottom of this response).
I know you can leave Path blank or omit it. I've been experimenting with all the different permutations and posted what happened to be "current" at that moment. In the pseudocode in the original post I did include the trailing "/%".
For the path in the original code block...
<p class="dcLandingPgColumn"><%# Eval("DocumentName") %></p>
<ul class="quicklinks">
<cms:CMSRepeater
ID="uxArticleLinks"
DelayedLoading="true"
path="{%# Eval('NodeAliasPath') %}"
runat="server"
ClassNames="CMS.Article"
TransformationName="custom.dcsp.getArticleDesc"
OrderBy="NodeOrder" />
</ul>
... I've tried both
path="{%# Eval('NodeAliasPath') %}" and path=
"{%# Eval('NodeAliasPath') %}/%"... among other options. The results were:
-
path="{%# Eval('NodeAliasPath') %}" renders all the articles under the current page in the content tree (not the current item being rendered).
-
path="{%# Eval('NodeAliasPath') %}/%" renders no data.
I did try using the code from Dave, but it didn't work. I used yours (FroggEye's) and changed "nestedRPT" to "uxArticleLinks" to match my code...
and *that* is working. (Yay! Thank you!) So, the problem in my original post about the nested repeater is resolved (as long as the viewer allows javascript).
The other issue.I'm still working through the "new but similar" issue where
Path="/{0}/%" in an ASPX template doesn't work - but explicitly stating the path (like:
Path=”/Clerk-s-Office-(1)/%”) does work.
This is the "goal code" which would output all the documents starting at the root of the current node...
<cms:CMSUniView
ID="uxNavFlyoutMenu"
runat="server"
LoadHierarchicalData="True"
HierarchicalTransformationName="DeschutesOrg.dcNavControls.HierarchicalNavMenu"
Path="/{0}/%" />
... and the results of my experimentation:
- If the path property is omitted, I get the children for the current item.
- If I use Path="." I get the current item.
- If I use Path="/{0}/%" I get no data.
- If I use Path=”/Clerk-s-Office-(1)/%” I get what I would expect to see when I use Path="/{0}/%".
(Clear as mud, right?)