You know, it actually looks like it's not supported.See here: http://www.slideshare.net/justinedelson/demystifying-oak-search slide 40 and 41, specifically states that synonyms are not supported.

I believe you can utilize the tilde (~) to do this.

Try this:/jcr:root/home/users//element(*, rep:User)Also, the query debug tool is a great way of playing with queries: http://localhost:4502/libs/cq/search/content/querydebug.html

We ran into the same issue.  If you check the error log you're probably getting a generic error from T&T.  After some back and forth with Adobe, it turned out it was because the length of the path from AEM was too long for T&T to handle, which is likely why one of yours is working and the other isn'...

I don't exactly know that I understand what you're saying about the user drag/drop, impersonation piece, but from the perspective of using it in a service to create/read/etc, you shouldn't have any issues.  The only restriction that i'm aware of is that only the "admin" user has access to the CRX Ex...

You can create a user and assign it to the administrative group and use it's credentials rather than the default admin user.You may also want to take a look at this article which goes over using the correct resource resolver in AEM 6.

I don't know that i truly understand what you're trying to accomplish, but the business requirement sounds pretty out there and impossible.  I think maybe it'd be worth going back to management and teaching them the best practices of a CMS and websites, rather than trying to tailor a CMS to do somet...

Do you have a custom site catalyst configuration file?at org.apache.jsp.apps.cq.analytics.components.sitecatalyst.config_js_jsp._jspService(config_js_jsp.java:44)

I don't have an answer to the exact question you asked, since it's a custom plugin and we do not have the code, it's impossible to diagnose, however, i would question the implementation method.I think that writing custom plugins for the text editor, especially moving forward with the Touch UI (and t...

Rather than doing that, you could potentially utilize the path field of the workflow launcher to prevent it from running.  Maybe try something like this:/content/dam/(/.*/)renditions/original(?!\\.pdf)\\.+I haven't verified that this would work, but it certainly would make more sense than extracting...