Masoud Rozati

The issue with single configuration root in JMX console is pretty confusing for administrators; specially when one of applications uses the legacy configuration, which simply overwrites the newer one: https://github.com/Netcentric/accesscontroltool/blob/develop/accesscontroltool-bundle/src/main/java/biz/netcentric/cq/tools/actool/impl/AcInstallationServiceImpl.java#L131...

The issue is caused in [container.html#L17](https://github.com/adobe/aem-core-wcm-components/blob/master/content/src/content/jcr_root/apps/core/wcm/components/container/v1/container/container.html#L17) where the property `layout` is literally compared to the constant _name_ `RESPONSIVE_GRID` instead of constant value `responsiveGrid` So, a quick solution is changing it...

yes, the problematic call comes from "profile" store in AEM product: `/libs/granite/contexthub/components/stores/profile/store.profile.js` imho we don't need this store at all. In asset share we already have a call to `/libs/granite/security/currentuser.json`...

Actually I didn't file a daycare ticket yet, because I believe the profile contexthub store is designed to be used only on author instance. Denying user to have access to...

This issue is fixed in Core Components 2.26.0 https://github.com/adobe/aem-core-wcm-components/commit/d844a0eab1566c3d8bf0cc8ed2973fb6f81e3e63#diff-39c3b2acc1becfa7dd6ac3bb4de392f0383fd437729e709e63a7f4f771308aa5 which is available from AEM 2024.8.17465

The issue is still reproducible in the latest AEMaaCS version 2023.1.10675 with Carousel. The workaround with "switching to preview mode and back" or re-laoding the page is quite annoying for...