Strange behavior after republish copying and moving nodes.
Hi,
Umbraco shows strange behavior after republish copying and moving nodes. When I for example use a recursive lookup by "ancestor-or self" the results don't correspond to the content in Umbraco.
Currently I'm working on a site that completely relies on copying nodes and recursive lookups.
I tried republishing(for real using publish on the site and clearing cache on content), regenerating index (first cleared the umbdont.. folder), regenerating umbraco.config, checked for a webgarden and I checked the accessrights.
The only way to get everything working is by republishing every node manualy. This is not the first time this problem accurce, I noticed this behavior before. Only now I realy need the functionality
Strange behavior after republish copying and moving nodes.
Hi,
Umbraco shows strange behavior after republish copying and moving nodes.
When I for example use a recursive lookup by "ancestor-or self" the results don't correspond to the content in Umbraco.
Currently I'm working on a site that completely relies on copying nodes and recursive lookups.
I tried republishing(for real using publish on the site and clearing cache on content), regenerating index (first cleared the umbdont.. folder), regenerating umbraco.config, checked for a webgarden and I checked the accessrights.
Any help would be much apriciated.
Ron
Are you programmatically moving then nodes or are you doing it within the UI?
If you're doing it programmatically make sure that you do an update of the cache via umbraco.library.PublishSingleNode(int id).
The Document.Publish method doesn't refresh the cache.
I know slace, I am just using the ui.
The only way to get everything working is by republishing every node manualy.
This is not the first time this problem accurce, I noticed this behavior before. Only now I realy need the functionality
Ron
Has anyone from the core team a suggestion?
Ron
is working on a reply...