This was already present in my setting.xml. And after changing a little in Pom, the build was successful. But now the core bundle is in installed stage and throwing this error => com.adobe.acs.commons.email,version=[1.3,2) -- Cannot be resolved

Failed to execute goal on project project-name.all: Could not resolve dependencies for project com.project-name.aem:project.all:content-package:1.0.0-SNAPSHOT: The following artifacts could not be resolved: com.adobe.acs:acs-aem-commons-ui.content:zip:min:5.6.0, com.adobe.acs:acs-aem-commons-ui.apps...

@karthik2906 If I understand correctly, we need options to add pages manually instead of fetching them dynamically. For this we can create our CQ dialog in this way =>Create a checkbox to decide whether page will be manually authored or not.If this is checked show (CQ dialog show hide) a dialog box ...

 Try changing these configurations according to your need. This should work. 

Hey @satishpothabathula ,I am having a little hard time understanding the problem statement. Can you explain a bit more with screenshots?

Hello @sateeshreddy As per my knowledge, it will be better if we create a separate component whose cq dialog will have a multifield with a text field that will take a name (nodes of this name will be created under the parent component to save the authored data for every button). You will author the ...

If we need a part of the existing dialog and not the actual content authored, we can use something like this <dialog jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/include" path="path/to/the/origianl/dialog"/> But if we want the content of the e...

I have 7-8 components on a page, and all these are the same component with different content( authored differently). Now I want to hide the 4th component for a particular user and the 7th one for another particular user group. Any idea on how to achieve this? The only thing that is making it hard fo...

Thanks for the reply. I tried changing the class names. It somehow does not work. But I found out the issue.The attribute: data-cmp-is="carousel" is the main entry point for the JS. If this attribute is not there, the OOTB JS would never work. So I replaced the value of this attribute with data-cmp-...