We did cancel the inheritance both at component level (i.e) on the carousel and then on the individual items as well, but then still we are able to replicate the issue. We tried the below use case :Author a Carousel Component with 3 buttons at Master level.Go to a livecopy, break inheritance on the ...

Thanks for your reply @Vijayalakshmi_S . Tried with the latest version of core components 2.17.8. But the issue still persists. 

Thanks @arunpatidar for your reply. We did setup a vanilla instance and tried this scenario again. And the issue is replicating in 6.5.8 and core component version Core Components 2.14.0 . Looks like a possible bug. Will raise the issue at https://github.com/adobe/aem-core-wcm-components/issues . Wi...

We are on AEM 6.5.8 with core component version 2.14.0 and facing an issue with rollout of container based core wcm components such as Carousel,Tabs and Accordion. Steps to replicate:Create a page on master copy using editable template.Author the master page with Carousel, Tabs and Accordion compone...

My local AEM Instance was corrupted. I deleted crx-quickstart and re-started AEM instance. It worked for me later.

We had a use case where we had to extend inheritance locks on live copies for Experience Fragment pages. In one of the page rendering components observed that there was node defined as : <msmConfigEndpointjcr:primaryType="nt:unstructured"sling:resourceType="granite/ui/components/coral/foundation/for...

Got it, I think deleting the unnecessary modules , every time a new project is created is the only way.

How can I create a perfect AEM project according to my requirement using maven archetype 23 ?I am using the below configuration, But this always results in creation of other modules such as dispatcher.ams, frontend.angular, frontend.general, frontend.react also getting created, though I have marked ...

Facing the same issue in AEM 6.4.8.2