Stale nodes list

bsloki wrote...

Essentially, it should update the same nodes !! If not there is some issue with your component behavior !

Also, in any case there is no way AEM list all the unused nodes, it has to be handled manually or by customized services 

 

Can you please tell me what condition is to be given while filtering the stale node. As I cant see any property difference in stale node.

If you know the JCR path where your component creates nodes - then write a service that deletes the nodes. 

We authored a component and it has created content node column1 and column2. After that we modified the authoring details and it has created two more new nodes in the page content node, but it didnt delete the previously created nodes(column1 and column2). Now how to segregate these stale nodes(column1 and column2).

@Bsloki,

May I know, How do we get list of unused nodes in the repository?.

---Jitendra

As @Scott mentioned, please give a specific usecase you are looking at. It depends on what you call it as stale nodes. Is it unused version nodes or unused content nodes. Each type of stale nodes should be handled in a different way. However, there is no such OOB feature to list all the stale/unused nodes.

Can you please expand on what you mean by stale nodes.  What is your use case?