Amita Singh wrote... Thanks Justin, can you give me an idea of how complex the customization would be ?    Maybe a 7 out of 10. Definitely not for the faint of heart. And to be clear, even if that case, you would only get the replicated versions, not any manually created versions.

In general, versions aren't created on publish and doing so requires non-trivial customization. Let alone creating a UI for visualization.

FYI - There is no version 5.6.2. There is 5.6.0, 5.6.1, and now 6.0.0

What version of AEM are you using? What, if any, feature packs and hotfixes have been installed? What differences exist between /apps/cq/personalization/components/clientcontext and /libs/cq/personalization/components/clientcontext (IIOW, why was the /apps copy created?)?

Hi,> Do ALL of the injectors get called if NO @Source annotation is declared for the field/method ?Yes, at least until one of the injectors returns a non-null value, at which point no other injectors will be called for that field/method.> If a @Source annotation value IS declared, ONLY that injector...

It's under the Status dropdown in the Web Console. Direct URL would be something like http://localhost:4502/system/console/status-slingmodels.In your injector, you can inspect the AnnotatedElement passed to it. Take a look at the sample code here: https://github.com/justinedelson/sling-models-demo/b...

Fraser-Does the output of the Sling Models Configuration Printer show your injector coming in last? That would be the best way to check that the configuration was correct.Note that even if it is last, your injector may still be invoked for methods/fields which don't have a specific @Source injector ...

Hi,I can't reproduce this issue on AEM 6.1 in publish mode (both with and without the nosamplecontent runmode). The best thing to do would be to create an issue at https://github.com/Adobe-Consulting-Services/acs-aem-commons/issues and attach the Configuration Status ZIP file from the OSGi Web Conso...

AEM uses a proprietary binary format for replication called Durbo. Durbo includes the necessary checksumming to ensure that replicated content is not corrupted during transport. If it is, the replication receiver servlet (on publish) will reject it and the replication sender (on author) will retry. ...

Hi,The correct way to do this with the c:forEach tag is to use the varStatus attribute to capture the status object (of type http://docs.oracle.com/cd/E17802_01/products/products/jsp/jstl/1.1/docs/api/javax/servlet/jsp/jstl/core/LoopTagStatus.html). It would look something like this: <c:forEach var=...