Hi @ViaVu, Please refer this if it helps: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-change-aemaacs-environment-indicator/m-p/645515 https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-environment-indicator-in-aemaacs/m-p/564028

Hi @AadhiraRa, By default, the Dispatcher only considers the path and extension when creating a cache key, so different Sling selectors can end up being cached as the same file. To fix this, you need to update your Dispatcher configuration so that selectors are included when generating the cache ent...

Hi @ReneDa, This meta tag comes from the page tags set in Page Properties (Basic tab). When a page has cq:tags assigned, the default Page component (both foundation and Core Components) will automatically render a <meta name="keywords" content="..."> element in the page head. The values are taken ...

Hi @jayv25585659, Yes, technically it is possible to do a redirect from a Sling Model, but it’s not recommended and generally considered bad practice.  Here is ehy:  Sling Models are meant to represent content, provide data for the view, or encapsulate business logic for rendering. Redirecting is ...

Hi @SrikanthPo3, I hope you verified the bundle is active?

Hi @Vishal_Kagde, Content Fragment is stored as its own asset in the JCR, which means every translation will indeed have a separate UUID. There isn’t an out-of-the-box “translation link” field, but Adobe provides best practices for associating multilingual fragments: Use Language Root Folders Plac...

Hi @jayv25585659, Please encode them in one string.   Then in your config.prod.json (or config via config.pipeline), you can map: { "myList": "$[env:MY_LIST;default=foo,bar]" }  

Hi @SHIBANI06, If you are planning to reduce the number of Publishers and Dispatchers in Production, there are a few important points to consider before scaling down: Traffic & Load Analysis Check your traffic patterns (page views, concurrent users, API calls) for the remaining 8 sites. Run load ...

Hi @khalidmo, Since this is AEM 6.5 On-Prem (Classic) but deployed on Azure, you should aim for cloud-ready infrastructure: 1. Core AEM Setup Author Tier (for Assets) Clustered (Cold standby or TarMK/Document Node Store depending on scale). If asset-heavy → use Document Node Store backed by Azure...

Hi @robertol6836527, In AEM on-premise, the license validity and expiration are not exposed directly in the Author UI. The license details are stored in the license.properties file located in the AEM installation directory. A typical perpetual (enterprise) license looks like this: license.customer....