@Vish_dhaliwal- I did those exact steps but I still see all the templates while creating a new experience fragment. The policy is updated in crx (cq:allowedTemplates) but while creating a new xf it is not getting applied.I am using 6.5.0
Hello Community - It looks like cq:allowedTemplates is not working in 6.5.x as expected. We are trying to restrict the templates for experience fragments. Tried updating the property in /content/experience-fragments folder but no luck. We see all static templates as well after updating the property....
@Anderson_Hamer - I am also facing the similar issue. Can you please let me know if making the changes at static template level fix the issues with the allowed Templates policy at /content/experience-fragments level? if so, can you tell me what should I use in static template allowedPath (Regular Ex...
Hello Community - We are using HTL Use-API to get the cookie value from the script and printing the value in the component. For some reason, it is not working as expected and it retains the previous selected value. AEM document says "Use-API" could be slower. Is there any way to use the return value...
@Vijayalakshmi_S - Thank you so much for your inputs. The issue is resolved. It looks like the deleted bundle reference was still in the registry. Whenever I delete any bundle from the console and verify the packages used by the bundles by using depfinder, I could see the deleted bundle reference wa...
Hello Community - I have some issues with the bundles which is causing the issues with authoring the components in the project. The bundle has several sling models and servlets in it. If I install the same bundle in my local, I am able to successfully activate the bundles, activate the models and se...
I am using RTE, Image and also Layoout Container. The issue is intermittent. Moreover, when the resizing us not applied, I could see the offset and width values are stored as “NaN” in the JCR for the viewport.