Hmm... interesting. Apparently it seems that you need either a ContentElement or a ElementTemplate to add a new element to the existing content fragment, but they are adaptable interfaces, so can't make a direct object out of it. You can still play around using the Resource API or the Node API and a...

Hi @prithwi, Maybe another approach will help you (which might be easy):Create a container component like "visual-filter-container"Allow only visualFilter component to be dropped insideAdd the visualFilter components and you should be able to re-order them.This approach is not fancy as the above, bu...

Hi @prithwi, Unfortunately I dont have a custom example of mine, but found this from @arunpatidar's blog: https://aemlab.blogspot.com/2022/09/aemaacs-core-components-children-editor.htmlhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-blogs/things-to-know-when-implementing-t...

Hi @prithwi, I think you need a component with a childreneditor dialog enabled. Basically it is a component with a dialog in which you can add other components and rearrange them on the go. You can also define which components you would like to allow as child components. Please see the below for ref...

Hi @KannaKarthi, sorry need more details here:What kind of changes are we looking at?Are your changes dependent on any config? If so, can you pls check if the configurations are setup correctly in the dev server?Could you fetch the logs from the dev server and see if something is wrong?

Hi @Ankan_Ghosh, I think you need to embed the ACS commons dependency in your project. If you have all package, it should be in all/pom.xml, if not then preferably it should be ui.apps/pom.xml. Please check if the below link helps. https://adobe-consulting-services.github.io/acs-aem-commons/pages/ma...

Hi @Starpuff, What does the log say? It would be better to debug the workflow steps & check the logs to see what happens actually, as the workflow could fail because of some exception. Regards,Ramkumar

Hi @LyonMartin, I had a similar issue in my local and then I found out that it was caused due to an empty folder in my component structure. I had an empty _cq_template folder (wanted to add a file later) but once I removed that folder, I was able to use my component as intended. So please check if y...

Thanks for the update, good to hear that it is working, and pls post if you are able to sort out the color stuff. Unfortunately I didn't try that.

Hi @Nirmal_Kumar1,Normally you would have a path in which you would have configured the RTE settings, for example pls see the first screenshot from @hibikik74610607 . So that path of that node should be mapped to the RTE field separately for rtePlugins, uiSettings and htmlRules. Hope this helps.