Hi All,
We are having a scenario where /content/versionhistory... path are also coming in references for pages. We tried to limit it by adding exclude path property in cq:lucene but no luck. Can someone please help in this ?
Solved! Go to Solution.
Views
Replies
Total Likes
You can handle by Simply creating an JCR Event Listner for versionhsitory node created and delete version history node as soon as node created.
observationManager.addEventListener(this, Event.NODE_ADDED , "/content/versionhistory", true, null,
new String[]{"cq:Page"} , true);
You can find more detail about above method at ObservationManager (Content Repository for Java Technology API 1.0)
Whenever author do page compare with any older version, that older version is created as page inside versionhistory node and shows as a page. Please check the below post and it will give you an answer.
I am aware that version gets created but we are trying to remove those entries from the references which should not be there. When we check for references from the miscadmin, we should not be seeing versionhistory nodes.
You can handle by Simply creating an JCR Event Listner for versionhsitory node created and delete version history node as soon as node created.
observationManager.addEventListener(this, Event.NODE_ADDED , "/content/versionhistory", true, null,
new String[]{"cq:Page"} , true);
You can find more detail about above method at ObservationManager (Content Repository for Java Technology API 1.0)
We don't require a version history node deletion but only remove them from page reference.
Views
Replies
Total Likes