I am using AEM 6.3, Touch UI. I wanted to expand the default text component from we-retail by adding the RTE table plugin into the rich text editor. So I added a "cq:editConfig"  with this node structure:<?xml version="1.0" encoding="UTF-8"?><jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:j...

Thank you for the advice - I appreciate the replies.Even though those options didn't fix it, I have figured it out. It's not about recompiling the jsp or java. It's on the thumbnail.png node. After the thumbnail.png is uploaded and used in the UI, AEM automatically generates different sized thumbnai...

We are using 6.3. We were using Classic UI, and we are making the transition to Touch UI.One of our static templates uses a thumbnail file. In Touch UI, on the sites.html page to select content (http://localhost:4502/sites.html/content), all the pages using that template automatically show up with t...

Is there a way to prevent certain templates from showing up while in Touch UI, yet remain available while in the Classic UI? We have been working on moving from classic to touch. We have only enabled some of our templates to work in Touch UI. Some of them will remain only workable in Classic, so we ...

Hello,I am using AEM 6.3.  I am trying to understand the relationship between template policies (i.e. policy_123456) and the configuration stored in etc/design/<your-project-name>/.content.xml.In [template]/policies, you can store mappings (sling:resourceType="wcm/core/components/policies/mapping") ...

Thank you Gaurav for the information you provided. Although I ended up going a different route, I appreciate you taking the time.What I ended up doing was overlaying /libs/cq/gui/components/common/wcm/clientlibs/wcm/js/copy.js , and within the .cq-wcm-paste-activator onClick function, the naming pag...

And can anything be done if using static templates in Touch UI?

Our project is moving from Classic to Touch (AEM 6.3). Our content uses a custom service (generating a numeric string) for naming pages (i.e. "12345"). For page creation, the default pagename field has been replaced via overlay to have a hidden input field that is automatically populated by the serv...

I'm still trying to process and understand what Gaurav put in there. I've tried adding and configuring 'cq:deviceGroups' property on my root page's jcr:content, but that did not seem to change anything. The rest is still new to me, so I'll keep trying to figure it out.So you understand, I'm working ...

Thanks Prashanth (and Peter and Scott). Adding that client library did the trick.Now that I know the answer, I found places where it even says as such:https://helpx.adobe.com/experience-manager/6-3/sites/developing/using/page-templates-editable.htmlNote: