Hello @kashyap691 , From my experience, I faced this situation many times and was successfully supported by a simple component. What I did is, I created a new component called "flex container". This is 100% the width of the layout and has a paysys.Features of this component: Different Background ima...

Hello @supriya-hande , For your requirement, the best practice is using Sling Delegation Pattern where you need to change the logic of "Options for Child Pages" in your Java implementation class. The core list implementation: https://github.com/adobe/aem-core-wcm-components/blob/main/bundles/core/sr...

Hello @samsri , You can see this similar thread, https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/com-day-cq-wcm-api-cannot-be-resolved/td-p/385695  If it's not helping you please let me know the following details. Your AEM service pack version and the Uber Jar you are using...

@NitroHazeDev Yes you are right.Actually, from our development perspective, it seems incorrect but according to AEM architecture/concept, this is expected.

Exactly that's the case, When you edit an experience fragment you basically edit a page. (ex: experience fragment page template). On that page, wcmmode behaves as a regular pattern. And you get your desired value.Note: Here I am talking about (/aem/experience-fragments.html/content/experience-fragme...

Hi @krist_wang , From your Ajax call, call the servlet,   bin/public/aem-demo/blog?page=2   Where the page params will be the page number. Try with the following Java code and change them according to your logic.   @Component(service = Servlet.class, property = { Constants.SE...

Hello @NitroHazeDev , See this chart, where the same component is on a page. Once it drops the page directly by parsys, another one comes from XF. This result is from the Slightly. Now, you can question why it happened. The answer is by XF the component is already rendered and comes to the page. Us...

Thanks for responding,image = modelFactory.createModel(resource, Image.class); also, you mentioned image = resource.adaptTo(Image.class); Both of them are getting null point exceptions.   I am assuming your Annotate modelFactory is not null. It is perfectly initialized. Since both line doesn't work,...

Hello @NitroHazeDev , The answer is related to the author's instance. The Slightly code doesn't detect the wcmmode edit because the XF is rendered from a different path on the page. When you want to use wcmmode edit it's always like/behaves view as publish mode.The Solution is linked to a Model clas...