This topic was raised in an internal discussion at my company where there is a desire to use HTML5 "data-" attributes without having to wire each one into the AntiSamy config.xml. This use case was once publicly discussed in a non-AEM project at https://jira.sakaiproject.org/browse/KNL-1007 . I was ...

If I had an overlay of of the AntiSamy config file at /apps/cq/xssprotection/config.xml, could I adjust it to allow random data attributes specified by authors? I see it uses regular expressions to validate attribute values, but can I use a regular expression to validate an attribute name? For examp...

I don't know precisely what the issue is but here are a couple things to check. Make sure your local and dev instances both have the same service packs & cumulative fix packs. In general it's not uncommon to see subtle variations like this when your AEM instances aren't all the same. Also, sometimes...

I didn't see the issue you described after fixing my issue in AEM 6.0. I also haven't seen this issue in AEM 6.1 after several months.

So it sounds like this is a known issue with the clientcontext component. I know I can ignore these errors because I've been ignoring them for years. Is there something I can do to either fix or suppress these errors? Would removing those ACLs from /etc/segmentation be helpful?

Why do requests for /etc/segmentation.segment.js generate these errors in the error log? This happens in a new AEM 6.1 instance and also when service pack 1 is installed. The segmentation.segment.js is called when a page contains the clientcontext component. 11.03.2016 15:58:50.595 *ERROR* [127.0.0....

Here's how I fixed this. There is an ootb component at http://localhost:4502/system/console/configMgr/com.day.cq.wcm.core.impl.PageManagerFactoryImpl which normally swaps illegal characters with hyphens by default. This component is the "Day CQ WCM Page Manager Factory". It has a configuration field...

Normally when I author a new page in AEM 6.0, AEM takes the spaces in the page title and replaces them with hyphens in the page name. However, at one of my AEM 6.0 instances, AEM fails to insert hyphens into the page name as expected, so a page titled "my test page" becomes named "mytestpage" instea...

Here's how I fixed this. There is an ootb component at http://localhost:4502/system/console/configMgr/com.day.cq.wcm.core.impl.PageManagerFactoryImpl which normally swaps illegal characters with hyphens by default. This component is the "Day CQ WCM Page Manager Factory". It has a configuration field...

Normally when I author a new page in AEM 6.0, AEM takes the spaces in the page title and replaces them with hyphens in the page name. However, at one of my AEM 6.0 instances, AEM fails to insert hyphens into the page name as expected, so a page titled "my test page" becomes named "mytestpage" instea...