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...

Thank you Community Administrator for your speedy reply! However, your original question strikes me as misplaced. In my humble opinion, this type of pre-made question & response would be better suited as a help article in the AEM help section.

One approach would be to simply build a component with that has an edit dialog that allows the author to choose either the grid display or the list display. Or have it use one display by default if the author has not chosen one.The problem here is that there is no distinct way for you to detect that...

You might try escaping the path to your resource.This article on escaping & encoding paths, names, and values may be useful:http://wiki.apache.org/jackrabbit/EncodingAndEscaping