This was confirmed to be a bug. A hotfix has been provided. I am informed that this will be rolled into a future service pack.

I appreciate it's an old post from 2017 and I am responding in 2023 Nevertheless...   I don't think the Garbage Collector works that way. I think it just keeps the footprint of the /content/cq:tags minimal. Hope you found a good solution though. Personally, I think it's a process issue and making s...

Exactly right Arun! I'd be keen to know if there is anyone in the community who is pulling content via QueryBuilder APIs to hydrate external search indexes. Neither have I personally used this approach nor does it make sense to me. I wonder if anyone out there in the community has used this and had ...

Technicalities aside - the simple answer is no. Do not store user data in AEM. Use integration that stores this data somewhere else.

Hello folks, My understanding has always been that the design pattern to follow when integrating with external search platform is always a push based mechanism whereby AEM responds to content events (publish, unpublish etc.). Traditionally this ends up being calls to the external platform to update ...

Thanks for replying. This is what we had planned for and also decided to shelf the idea because of the effort invovled. I was hoping there would some other legitimate hooks for doing this but sadly that does not appear to be the case. We will feed this as an enhancement request for Adobe to provide ...

Hi all, It's pretty standard to customise the search rail for assets but has anyone ever customised the search rail for workflow inbox? Let's say I wanted to add a different facet to filter the inbox items. I don't see any documentation regarding this anywhere and naturally would be very interested ...

Hi all, We are currently evaluating XML Documentation for AEM. The idea is to have all the technical content (dita assets) stored in AEM and exposed them via a bunch of services which the frontend will then consume and render accordingly. The existing frontend has a rich set of JSON APIs exposed out...

You could also consider the Webhooks APIhttp://developers.marketo.com/webhooks/

Doing this in practical terms is untenable from a performance point of view. Imagine one tag that references 50K pages. You do this and you will bring down your author instance or whatever instance you do this on. Then there is the question of what will you do with vast number of pages that have now...