How to find References to Components in the site hierarchy

[sureshr31455031]

Is there any default feature that is available in AEM 6.1 and later versions to find out the references to components in the entire site hierarchy and a way to activate them in bulk or in chunks.

We had a situation recently where a component's[#1] HTML has been modified and we need to flush the cache of all the pages which are referencing the component[#1]. Even though it is a simple HTML change but the effect we had on the site is huge as the component fall under a application specific General Group [For ex: AppName-General.] which can be used anywhere in the site. In these scenario's it would be helpful to have a wizard view to chose the resource type or select a component, find all its references and activate all the pages.

http://localhost:4502/etc/reports/compreport.html I believe this report can only show the number of page references available. However, It doesn't have any further ways to activate those pages. Other alternative is to delete the dispatcher cache files which doesn't seem to be an ideal one when the content is huge. This can even be achieved programmatically.

Even though this is not any regular operation in the project implementations, but it can be very handy in above situations.

[smacdonald2008]

Is there any default feature that is available in AEM 6.1 and later versions to find out the references to components in the entire site hierarchy and a way to activate them in bulk or in chunks.

There is no such feature with respect to an entire site.

With Respect to page components - you can view which components are on a page using this URL: 

http://localhost:4502/editor.html/content/geometrixx-outdoors/en/men.html?debug=layout

[sureshr31455031]

Thanks for your time sir!!

Can we treat this requirement as an FR if it helps adding value in the project implementations ?

[smacdonald2008]

You can log a Request bug too. That is the power of the AEM Community that drives product improvement.

[Jörg_Hoh · Accepted solution]

Hi,

I would think, that purging the complete cache might be much easier than identifying the relevant pages and just activate them. Actually you don't need the activation of the affected pages at all, but you just need a side-effect of it, the purge of the dispatcher cache.

Jörg

[sureshr31455031]

I agree Jorg. Thank you

Thanks Scott.