Refresh XML of content node and update cache without publication
I'm just moving to 6.2.5 from 4.7.1 and have problem with new Umbraco API.
I need to update content properties very often so I change property value then refresh XML and content cache without publication to prevent all events and new content version.
Is it possible in 6.2.5 API to refresh XML of the node and update content cache?
Yes it is strange for most of cases but not at our project. I need to change content property very often sometimes for the same node. So I have to omit normal publication due to new version of content which is automatically generated after each publish.
For example I need change update date of parent node when any child is published.
Refresh XML of content node and update cache without publication
I'm just moving to 6.2.5 from 4.7.1 and have problem with new Umbraco API.
I need to update content properties very often so I change property value then refresh XML and content cache without publication to prevent all events and new content version.
Is it possible in 6.2.5 API to refresh XML of the node and update content cache?
Hi,
When you right click your root node of the content tree there is option to "Republish entire site". This does what your a looking for.
If you want to do this using code that would be a good starting point to see how it is done.
Dave
I know functionality you mentioned but it is not the same what I need to achieve.
I need to do something like this:
Hi,
You can all this using the content service.
Have a look at the documentation : https://our.umbraco.org/documentation/Reference/Management/Services/ContentService
Dave
There is only one associaded method:
RebuildXmlStructures(params int[] contentTypeIds)
which don't allow generate XML for one node.
I know that I can publish node but as I have mentioned I don't want to do it due to generation a new version of content.
Hi
But why you want to update a content item without publishing, but have the published content cache updated ? Seems a bit strange to me.
Dave
Yes it is strange for most of cases but not at our project. I need to change content property very often sometimes for the same node. So I have to omit normal publication due to new version of content which is automatically generated after each publish.
For example I need change update date of parent node when any child is published.
is working on a reply...