We have moved to GitHub Issues
Created by Shannon Deminick 25 Nov 2016, 17:05:50 Updated by Stephan 28 Nov 2016, 12:06:25Tags: Unscheduled
The reason this happens is because the sort order of the xml cache needs to be updated in certain circumstances when content is saved, for example if something gets unpublished, the sort order would need to change in the xml cache.
However, in some circumstances, the sort order update makes no difference:
The main problem is that every time the xml cache is updated it's cloned which has a large overhead especially when there is a lot of content.
Have made a small change to the test in
HasPublishedVersion which is cheap and should tell us whether the node is in the XML cache at all or not. Otherwise, the rest is OK for me. Comments?
Backwards Compatible: True
Due in version: 7.5.5
Sprint: Sprint 47