cobyR
May 18, 2025, 11:13am
1
Atomik, V. 9.4.1. I cannot use containers in composer templates and use “setup on child pages”. On save, nothing there.@VisualNotes found how to use predefined css classes for containers, it would great to use containers in composer templates.
There is a github issue on this, which you can add your thoughts to:
opened 11:46AM - 10 Apr 25 UTC
Type:Enhancement
Affects:Content Creators
Product Areas:Page Defaults
Enhancement:Level Of Effort:3
### Affected Version of Concrete CMS
9.x
### Description
Concrete version 9.3… .9
When editing a page type default, specifically adding a new block, I always use the “setup on child pages” function to propagate this new addition to the children using that page type.
However, when a newly added block is inside a container, like so:
this function does nothing.
It seems Concrete ignores the container structure when setting the blocks up on the child pages, or rather ignores blocks within them and sets up nothing.
### How to reproduce
1. Create a page type default and create a child page using that page type.
2. Go back to edit the page type default, add a new container somewhere in the template and insert a block into the container.
3. On that block click on "Setup on child pages".
4. The block never appears on the child.
### Possible Solution
Make sure that if a new block is added to a page type default and the "Setup on child pages" is called, the block is copied over to the children including a container it sits within.
Alternatively, add a "Setup to child pages" to the container level, so the whole container could be pushed to the children, including all its blocks.
### Additional Context
_No response_
cobyR
May 20, 2025, 9:17am
3
Thanks John for mentioning the already existing Github issue.
This has been an issue as far back as Concrete CMS v8.x, it’s giving me issues with multiple v8.x sites right now. Rather annoyed it hasn’t been fixed all this time as to me it defeats the point of Page Types.
1 Like