Have you verified the following URL works on the render instance - /libs/granite/dispatcher/content/vanityUrls.html ? Also, in the access.log file of the renderer find this URL and see if it is getting called after every 300 sec or not. If it is not getting called then enable debug [1] log level on ...

I would recommend you to bind this servlet to a page path using the resource type and then use closed user group feature in AEM to secure this path on the publish instance. You need to expose only the page path to your external applications. If they request the page with authentication then they wil...

You can try the following pattern for this use case-^/content/www/xx/xx/(?!(test-templates)).*$

It is not possible to access JSONObject in Sightly. Check the below thread- http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__r2p9-is_there_a_waytous.html

Yes you can call MSM API to roll out pages programmatically. RolloutManagaer has method for rollout - https://docs.adobe.com/docs/en/aem/6-1/ref/javadoc/com/day/cq/wcm/msm/api/RolloutManager.htmlExample-Page masterPage = pageManager.getPage(path); //source page RolloutManager.RolloutParams params = ...

Well I was able to replicate this issue on my instance when I created a test node under actions and thats why I concluded that the culprit is the JS code. I don't know why you don't see it on all the instances.

If you inspect the network calls made by the browser when you load the siteadmin page then you will see it makes a request to - /libs/wcm/core/content/siteadmin.infinity.json. This means the javascript which creates the context menu bar processes all the nodes created under siteadmin configuration n...

You need to add a special parameter to the URL named "_charset_=UTF-8" and then the following code in JSP will work. Your url should be  abc.com/about?q=安&_charset_=UTF-8<meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> <% out.print(java.net.URLDecoder.decode(request.getParameter ...

Thats not the way how scene7 works. You do not have to create scene7 preset for every image but only a finite number.When you upload an image in AEM DAM then AEM create renditions of that image based on the pre configured sizes in the Update Asset workflow. For example if you created two renditions ...

The class loader in 6.1 for JSP files was changed to FSClassLoader bundle. The compiled JSP files are now stored in the filesystem and not in the CRX repository. Check this link - http://labs.6dglobal.com/blog/2015-06-23/new-apache-sling-fs-classloader-console/