Try adding this to the dialog as a new field:<keywordsString jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/form/hidden" name="./jcr:content/metadata/dc:subject@TypeHint" value="String"/>

Delete the property that is currently just a "String" and then try again (this my answer was for classic UI).  For Touch UI, use this:<myFieldString jcr:primaryType="nt:unstructured" sling:resourceType="granite/ui/components/foundation/form/hidden" name="./myField@TypeHint" value="String"/>

You need to set the typeHint in the dialogtypeHint="String"This will save the value as a String[] regardless of 1 or multiple values.

We place the robots.txt in a folder in the DAM and then have the dispatcher redirect any requests for it to the appropriate sites robots.txt file.  Simple and works.

Can't help with SQL2, but, using the query building/debugger it's pretty darn simple.http://localhost:4502/libs/cq/search/content/querydebug.html?_charset_=UTF-8&query=type%3Dcq%3APage%0D%0A2_group.1_relativedaterange.property%3Djcr%3Acontent%2Fcq%3AlastReplicated%0D%0A2_group.1_relativedaterange.lo...

I think the appropriate action here would be to go back to whoever created this requirement and simply say, no.This is quite possibly one of the craziest requests i think i've ever seen.

Also you shouldn't use $[currentPage.template} - it'll be blocked on the dispatcher due to permissions.

I would stay away from implement any custom xtypes/touch ui dialog fields like Scott's article mentions.  You'll undoubtedly run into issues during an upgrade.Personally i would think of how to re-structure the component to where the multifield isn't needed and rather use a component per item.  Loke...

private final String MY_OSGI_PROPERTY = "MyProperty"; private String myProperty; @Activate protected void activate(final Map<String, Object> config) { this.myProperty = PropertiesUtil.toString(config.get(MY_OSGI_PROPERTY), null); }

Are you by any chance creating another .web rendition, other than the OOTB 1200.1200?