At this time I have tree major clients who encounter this problem on there websites. The problem is as following:
To reproduce use a xslt with a recursive field: ancestor-or-self::node/data[@alias = 'banner' and . != '']
Then use a documenttype with a property having alias 'banner'. Create a structure simular to: myTopPage - mySubPage
when both 'banner' properties are filled on the pages you would expect mySubPage to show his own banner. Unfortunately he won't. The only way to accomplish this is to republish myTopPage. Only then the correct banner is shown on mySubPage.
The stange thing about it is that the normal recursive field on a template does work as expected.
Major problem with publishing nodes.
Hi,
At this time I have tree major clients who encounter this problem on there websites.
The problem is as following:
To reproduce use a xslt with a recursive field:
ancestor-or-self::node/data[@alias = 'banner' and . != '']
Then use a documenttype with a property having alias 'banner'.
Create a structure simular to:
myTopPage
- mySubPage
when both 'banner' properties are filled on the pages you would expect mySubPage to show his own banner.
Unfortunately he won't. The only way to accomplish this is to republish myTopPage. Only then the correct banner is shown on mySubPage.
The stange thing about it is that the normal recursive field on a template does work as expected.
Any help will be much appreciated.
Ron
CODEPLEX WORKITEM
http://umbraco.codeplex.com/WorkItem/View.aspx?WorkItemId=24889
is working on a reply...