The customer wants to:
- hide a single CMS element for specific categories,
- without having to maintain multiple nearly identical layouts.
The request clearly focuses on a more granular layout configuration that can be flexibly adapted to the category context.
Current situation (as of Shopware 6 standard):
- CMS elements are hard-coded into the layout.
- While a layout can be assigned to multiple categories, individual elements cannot be shown or hidden depending on the category.
- Although the Rule Builder offers controllable visibility (via CMS extensions), the active category is not available as a condition in the rule context.
- Therefore, it is technically impossible to control element visibility contextually at the category level.
Impact / UX limitations:
- For shops with many categories, this limit leads to high maintenance effort, as layouts have to be duplicated.
- Changes to the main layout then have to be manually transferred to all duplicates → error-prone and confusing.
- The lack of category context in the CMS is increasingly perceived as a restriction, especially in larger catalog structures.
The customer wants to:
- hide a single CMS element for specific categories,
- without having to maintain multiple nearly identical layouts.
The request clearly focuses on a more granular layout configuration that can be flexibly adapted to the category context.
Current situation (as of Shopware 6 standard):
- CMS elements are hard-coded into the layout.
- While a layout can be assigned to multiple categories, individual elements cannot be shown or hidden depending on the category.
- Although the Rule Builder offers controllable visibility (via CMS extensions), the active category is not available as a condition in the rule context.
- Therefore, it is technically impossible to control element visibility contextually at the category level.
Impact / UX limitations:
- For shops with many categories, this limit leads to high maintenance effort, as layouts have to be duplicated.
- Changes to the main layout then have to be manually transferred to all duplicates → error-prone and confusing.
- The lack of category context in the CMS is increasingly perceived as a restriction, especially in larger catalog structures.