Hi @smacdonald2008I know we can restrict the templates that are available when creating any page in any of the path. My question is regarding restricting the template types when trying to create templates. Lets consider below scenario:/conf/organization/brand-1/template-type/basic-template-type-1/co...

But all the template types from all projects are getting displayed when trying to configure any template. It would have been better if we only see relevant template types when configuring templates.

Hi,I want to restrict template-type to be available in specific project folder under /conf. It should not be available in other folders for creating the templates. How  can I achieve this?Thanks,Rajeev

Hi All,What is the best and most efficient way in osgi code to retrieve all matching nodes(any depth) in current page jcr:content that has resource type ="/abc/test". Any thoughts?Thanks,Rajeev

I don't see cloud services or IMS option in AEM 6.3 to integrate with Adobe Launch. Does AEM 6.3 provides any option to integrate Launch or else the only option is to upgrade to AEM 6.4 or else hardcode the js script in template?

Thanks Arun for the confirmation. We are blocking direct /conf access on dispatcher. I was checking this because OOTB permissions on /conf is set to deny all for everyone.Thanks,Rajeev

Hi All,I am trying to develop site using editable templates. These works fine with logged in user on publish but when trying to access the site using anonymous user, page content is not rendered properly. I found out that on giving read permission for anonymous user on /conf folder resolves this iss...

Scott - I changed it to 0.5.1 .. but somewhere I read that 0.5.24 is stable release.. In future if we try to upgrade it then it would good if this bug is fixed.

Thanks Arun. It is building fine with 0.5.1.Could it be bug in 0.5.24?

I am trying to upgrade content  package plugin from 0.0.24 to 0.5.24. When trying to build code with upgraded version, I am getting below build errors:[ERROR] Filter root's ancestor '/apps' is not covered by any of the specified dependencies.My filter.xml looks like:<?xml version="1.0" encoding="UTF...