In the current versions, the render tag <%!! Context:CurrentDepth !!%> is not working properly, in some versions it isn’t even recognized as a render tag in the templates.
Today I found a nice workaround for it:
<%!! Context:CurrentIndex.GetPath(¶).Split(¶).Length !!%>
I practically does the same thing: It reads out the current navigation path (with ‘¶’ as dividing char, as it’s normally not used for page names), splits the resulting string and gets the number of elements returned. Voilá, you’re done.
Discussion
No comments for “Quick Tip: Workaround for render tag “Context:CurrentDepth””
Post a comment
Stay up to date! - Get notified about followup comments
If you don't feel the urge to comment but wish to stay in the loop:Just enter your email and subscribe to new comments.