Hi,I think your AEM instance might not be tuned properly. I have written short summary of "Sling Memory Deep Dive" here https://medium.com/the-telegraph-engineering/four-highlights-from-adaptto-2018-3781782a6b7a and a detailed session video available here adaptTo() 2018 I found it very interesting in terms of memory usage, you may want to check it.Running compaction will obviously help and 6.4 does online compaction already so make sure it's happening.Creating indexes based on your queries will ...

Hi Arun,Thank you for your reply. We are not using core components, we managed to fix it by using extraClientlibs="cq.authoring.dialog.rte.coralui2" in touchUI dialog. RTE is now showing up but it didn't show "paraformat" options as we were using sling:resourceSuperType and loading RTE from xml file, we had to copy all the RTE options and add uiSettings node to the dialog xml file in order for us to have completely working RTE in touchUI dialog. Classic UI dialog still loads them from generic xm...

Hi Have you found any solution, we are facing similar issue too.

Hi all,Thank you for your replies, we ended up using acs commons generic lists using data source option.

Hi @hamidk92094312 @JaideepBrar Thank you for your messages.What are you doing when you get the error ? Steps that leads to the errorAs soon as I open the touch ui dialog with RTE configured, I see that javascript error and it's not showing rich text editor.What version of the product ?AEM 6.0I tried to use sling:resourceSuperType as well but that didn't help. Another interesting observation, We have another template A where I tried to drop this component with RTE configured, I can see it workin...

Ok thanks!, I thought they want to make indexing faster and offloading it to somewhere else can make life easier so I replied for this question. "When I add a property/node in my custom index, then it takes a lot of time to re-index. Any suggestion to make the reindexing go any quicker ?" - offloading won't make indexing faster but it's just makes primary usable and minimal or no downtime to apply index changes on prod!

I think recommended way to clear publish dispatcher cache is always from publisher via replication agent on publisher as oppose to author.Not sure why do you need to clear publish dispatcher cache from author directly.Regards,Rachna