Hello, If you followed this post completely, you find the details you are asking in the thread or you can also refer the mentioned article: Adobe Target: How to avoid Page Blank and Flickering Issues – Terryn Winter Thanks

I did use it on AEM6.3 but I would suggest you can give it a try on AEM6.5

libs/settings or /apps/settings is the path for oob files. Custom clientlibs are supposed to go in /apps/<project> folder

It is recommended to keep the clientlibs under /apps/<project>/clientlibs as also given in WKND sample site here: https://experienceleague.adobe.com/docs/experience-manager-learn/getting-started-wknd-tutorial-develop/project-archetype/client-side-libraries.html?lang=en

You would create groups for different websites, then you would go to Tools> Security> Permissions . Choose the respective groups and assign the jcr:read/ jcr:write/jcr:all or neccssary permission in respective content path like /content/siteA. This way you can keep the users from one site accessing ...

Hi Keerthi,   Glob pattern is allowed as described here: https://sling.apache.org/apidocs/sling9/org/apache/sling/api/resource/observation/ResourceChangeListener.html#PATHS

Still getting the same issue. Is there a way to check cloud manager Java version?  

Hello,   We have upgrade all the junit versions in pom.xml and it worked absolutely fine in local server but when deployed in cloud manager with latest (2023.1) version, the build fails with below error: 15:31:46,075 [main] [ERROR] COMPILATION ERROR : 15:31:46,076 [main] [INFO] ---------------------...

you might be hitting the same issue as discussed here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/gson-version-update-to-2-8-9-issue/m-p/458126

Yes this seems to be a permissions issue, you do not have right permission to see the nodes in publish. Please check if you have jcr:read or not on /conf and if it still doesn't work add jcr:all to /conf.