Found it!In my first post, I mentioned "I also tried looking in CRXDE Lite /apps/system/config for the configuration I set via Felix". I don't know which article I found that suggested looking there, but it turns out there was a node in /apps/cq/commons that appears to have the values I set in the F...

That also doesn't seem to be making a difference.When you add the \ character, as inexternalizer.domains="[local\ http://donotuse.com,author\ http://donotuse.com,publish\ http://donotuse.com,project-placeholder\ http://project-placeholder.com]"/>do you see that character in CRXDE Lite after deployin...

I'm using AEM 6.1, and writeback is enabled.Here's a screenshot of what I see in CRXDE Lite after deploying my package[img]Externalizer1.jpg[/img]Also, here's a screenshot of my project in Eclipse - hopefully that explains where the XML file I'm referring to comes from. I believe the other OsgiConfi...

Thanks, but it looks like that's not making a difference.

I'm having trouble configuring the externalizer service via an XML file.The first thing I did was add a domain via the Felix console to test, and that worked. Then I created a file in my project at /apps/client/project/config/com.day.cq.commons.impl.ExternalizerImpl.xml. It looks like<?xml version="...

I believe what I had to do to make this work was change the category of the clientlib containing my custom xtypes to "cq.widgets"

@smacdonald2008, I'm not seeing anything in that "admin extension" github that looks like it addresses what I'm trying to do. Nothing there seems to be attached to a specific component - am I missing it? I think I have a POC working. The steps I took are1) Create a clientlib and configure the action...

It looks like my problem with the approach at http://experience-aem.blogspot.com/2015/04/aem-6-sp2-touch-ui-open-component-dialog.html was that I missed there was a special clientlib name that needs to be used. I was trying to use an arbitrary name, and then use cq:includeClientLib in my component J...

@bsloki, I think I got two different errors - I'm trying to repro the second yet, but the first was when I tried to just keep the actionConfig node in place, as shown in the slides linked to by smacdonald2008 (http://dev.day.com/content/ddc/en/gems/user-interface-customization-for-aem-6/_jcr_content...

I have a few components that were created for CQ 5.4 and use custom actions in the editbar. As we migrate to AEM 6.1, I'd like to support these in both Classic UI and Touch UI. I found this demo https://github.com/Adobe-Marketing-Cloud/aem-authoring-extension-toolbar-screenshot that I've tried imple...