Hi @HelpTech , No, Sling doesn't support wildcards in path. It is mentioned in the sling documentation as well, that the path attribute accepts only absolute paths. The usage of path based servlets is also discouraged, and it is suggested to use resource based servlets, which provide better security...

Hi @sharaj , When you copy and paste a CF, there's going to be a network call that can be observed in the Dev tools of the browser. Can you share what the network call's response says and the underlying error from error.log file?   Regards,

Hi @s1101v - If I understand your question correctly. The end user browsing the site needs to read some data stored under the /conf/project2?   If yes - you can simply create a system user with a read access to the desired folder and use it to obtain a Service Resource Resolver object that can rende...

Hi @Vignesh_K_S - Ideally, you should be changing your component design. A multifield of 12 fields with about 60 entries is not only going to slow your load time but also difficult to manage it from the authoring perspective. Explore the following options to determine if they can be a good alternati...

Hi @Gunars_V - There's no way to bypass the CUG that has been applied to restrict the asset access. AEM will need a login-token in the headers, to authenticate and determine the user's presence in CUG to serve the asset. So, you will have to rely on solution like Brand portal to get the asset access...

Hi @Tarun_Kumar_ReddyGo , It's the password you get to set during the installation and totally your choice.

Hi @Tarun_Kumar_ReddyGo , What you have are only warnings, and shouldn't block installation. Are you sure the installation didn't proceed? First time installations take quite some time. You would ideally see a /crx-quickstart folder created parallel to your jar. Did you press Ctrl-C by any chance?  ...

I can try few and confirm you. What's your AEM version?

Hi @ShikhaSh1 ,   There are many options as shared in the above responses, but the simplest is to have both versions of the header present on your DOM as part of your single header XF and then hide/show based on the user state as mentioned by @EstebanBustamante .   Regards,

Hi @Amsalek4 - The teaser.html from the core list component is a template that gets called in the list.html. In this case instead of updating the teaser.html from the core component, try overriding the list.html in your custom component, and invoke your custom-teaser template that you create for you...