Hi Peter,Do you literally mean "components" (e.g. /apps/geometrixx/components/title) or instances of a component (e.g. /content/geometrixx/en/products/jcr:content/title). If it the former, then the answer should be "all of them" as you should be deploying your codebase to both author and publish mor...

What exactly isn't working? This code should run fine on AEM.

I also created https://issues.apache.org/jira/browse/SLING-3982 to provide a more intuitive solution, but I think the regex is good enough for now.

kumarlal123 wrote... justin_at_adobe wrote... Very interesting problem... If you have version 1.0.6 of the Sling Security bundle (org.apache.sling.security), you can solve this by using the allow.hosts.regexp configuration property. Set this value (or one of its values, as it is a multi-valued ...

Very interesting problem...If you have version 1.0.6 of the Sling Security bundle (org.apache.sling.security), you can solve this by using the allow.hosts.regexp configuration property. Set this value (or one of its values, as it is a multi-valued configuration property) to file://:0.If you do not h...

Hi Dmitry,The trick is to lower case the property4_property=fn:lower-case(jcr:content/jcr:title)and then lower case the search term4_property.1_value = %namefragment%Regards,Justin

Correct - the HTML output by the standard RTE plugins is generally allowed under the default XSS protection configuration.

Hi,The best thing to do is to modify the XSS Protection configuration to allow the font tag. See http://docs.adobe.com/docs/en/aem/6-0/administer/security/security-checklist.html#Protect%20against%20Cross-Site%20Scripting%20%28XSS%29.Regards,Justin

SamThadhani wrote...   justin_at_adobe wrote... This warning refers to the JCR Observation queue, not the Replication queue. This warning typically happens when there is a JCR Observation listener which is poorly behaved. It is unfortunately a bit tricky to figure out which one isn't behaving. ...

This warning refers to the JCR Observation queue, not the Replication queue.This warning typically happens when there is a JCR Observation listener which is poorly behaved. It is unfortunately a bit tricky to figure out which one isn't behaving. One approach is to take thread dumps. Another is code ...