Thanks for confirming @arunpatidar 

I configured Context Aware Config using wcm.io. When I edit a CA Config page, I saw my custom configurations which I wrote via @Configuration annotation. Till now everything is fine.But in the list of the configuration UI page, I saw all the configurations. Is there any way to restrict the configura...

I also faced the same issue. In my case, it was not fixed by page refreshing. And it's not related to the we-retail and my local project. I found this in the core-components-library demo section also.My Steps:1. Add Tab/Carousel component2. Add Image component in every container. Probably after addi...

Hi,I have a content path /content/my-project/gb/en/home/test. Then I used request.getResourceResolver().map("/content/my-project/gb/en/home/test").Output: https://www.myproject.com/en/home/test.html  Now I want to reverse this process. I need the actual content path from the mapped path.Ex: https://...

Thanks @Pawan-Gupta for your reply. Yes, manual process is working but needs an automated process like normal parsys. If it's not possible then need to think about other way but not manual.

I have a page template that body part contains iparsys. In that iparsys I allow some components and that component also contains each individual parsys.Now the problem is when I drop a component using iparsys that component's parsys policy is working fine. But after dragging the same component again...

Hi, unit test for Accordion will be like this->@ExtendWith({AemContextExtension.class, MockitoExtension.class})public class AccordionTest { private final AemContext context = new AemContext(ResourceResolverType.JCR_MOCK); private Accordion accordion; @Mock private ModelFactory modelFacto...

Hi there, I also faced this similar issue.Then I used sling:resourceType="granite/ui/components/foundation/form/datepicker"instead of sling:resourceType="granite/ui/components/coral/foundation/form/datepicker" And this is able to prepopulate the previous value.

In the browser cookie section, there is a cookie called “login-token”. After removing this cookie it should be alright.