Thanks. Good to know Wayfinder might be an option if I can’t get this to work.
My Debug report is attached.
The StartID is being reported as [!UltimateParent
Should this be the case, or should it show the ID that Ultimate Parent should be fetching?
-
☆ A M B ☆
- 24,524 Posts
Looks like the RTE replaced the & with & . Try editing the page without the RTE and get rid of the & bits.
I just replaced the RTE with & and it hasn’t made any difference.
Ultimate Parent on its own (outside of a Ditto call) is returning the correct parent ID I require. Judging from the Ditto debug report it looks as if Ditto might not be recognising the Ultimate Parent call properly.
Yes, I just noticed the debug console available (I was not aware that this would be available to the public when active, should only be for managers). Strange that the UltimaParent is getting cut rather than parsed. It is obvious that this is causing the problem and my guess is that the parsing order is to blame.
OK I did some tests and I was able to get the same problem when using the outside snippet cached and the inside one uncached like this:
[[Ditto? &parents=`[!UltimateParent? &topLevel=`1`!]` &tpl=`test` &display=`all` &debug=`1`]]
By reversing it it worked:
[!Ditto? &parents=`[[UltimateParent? &topLevel=`1`]]` &tpl=`test` &display=`all` &debug=`1`!]
I also noticed that you get slightly different results when using &parents and &startId.
In your HTML, you have this somewhere:
<-- You are here!
use <-- instead
Maybe this confuses the parser.