Can you prevent a rollout of a page based on the the existence of a property?If not, how could I prevent the rollout when the page has a specific property?
First question:We have a parsys used in an admin area of our site, that has over 1000 components inside. Other than browser rendering slowness, is this something that is still recommended to avoid with Oak, regarding read performance of nodes.Node structure:/content [sling:orderedFolder]+ page [cq:P...
I have a CLASSIC UI dialog multifield. For each multifield item, I have a dropdown that is populated from an expensive API call to an external system. As the multifield could have 40+ items, I want to avoid making 40+ API calls to populate each item dropdown.What is a good approach to solve this?
I am already using the explain tool. I have observed that it doesn't always pick the fastest - when lucene index is 510.0, cq:tag index is 310.0, it still prefers to use the slowest - traverse.
In AEM 6.0 using OAK, is it possible when writing a XPATH query to force what index is being used rather that letting the system determine which it thinks is the fastest evaluated index.
How do I access a request query string parameter in Sightly HTML. Do I have to expose it through the WCMUse model or can I just access it directly in the HTML?
Is there any documentation yet how to integrate AEM 6.0 with Solr using the new Oak/Solr integration option. I want to push specific content paths e.g. /content/* to Solr.Oak Solr embedded server configurationOak Solr indexing / search configurationOak Solr remote server configurationOak Solr server...