Skip to content

Feaure/nested elements#74

Merged
dmolineus merged 16 commits into
developfrom
feaure/nested-elements
Jun 5, 2026
Merged

Feaure/nested elements#74
dmolineus merged 16 commits into
developfrom
feaure/nested-elements

Conversation

@dmolineus

Copy link
Copy Markdown
Member

No description provided.

cboelter and others added 4 commits April 15, 2026 09:25
… grid field only on old start / stop elements, change original nested element to get working with separator elements

# Conflicts:
#	.phpcq.lock
# Conflicts:
#	.phpcq.lock
#	.phpcq.yaml.dist
#	composer.json
@dmolineus dmolineus self-assigned this Apr 15, 2026
@dmolineus

Copy link
Copy Markdown
Member Author

@cboelter Thanks for your contribution. I had a look at this again and I realized that the origin twig template was incomplete. It did not iterate over the grid.

I intended to remove all grid separator elements. So the grid wrapper assumes that each child is a new column. As a result of this, each column containing more than one element has to be wrapped by the contao group content element.

This is currently missing in the migration script, probably because of a misunderstanding of the goal that i had in mind.

@dmolineus

Copy link
Copy Markdown
Member Author

I also changed the configuration which enabled the migration. Following the symfony bundle guidlines I added a bundle configuraiton for it.

@cboelter

Copy link
Copy Markdown
Contributor

@dmolineus thanks for your Feedback und code fixes :-) should I add it to the migration or will you do?

@dmolineus

Copy link
Copy Markdown
Member Author

Would be great if you can provide the migration. Not sure how to detect/handle nested grids.

@cboelter

Copy link
Copy Markdown
Contributor

I will try to provide a changed migration in the next week :-) I'm not really sure that we have to detect nested grids. The Migration currently detects all start / stop groups and changes them, so also nested groups should be migrated correctly?!?!

@dmolineus

Copy link
Copy Markdown
Member Author

I will try to provide a changed migration in the next week :-) I'm not really sure that we have to detect nested grids. The Migration currently detects all start / stop groups and changes them, so also nested groups should be migrated correctly?!?!

You're probably right. Every content between a start/separator/stop element belongs to a group element (if multiple elements exist) or can exist as single element. This way it doesn't matter if an element is a nested grid or not.

@cboelter

Copy link
Copy Markdown
Contributor

Perfect 😊 I was not able to change migration, I will do in the first week of may. Have to recover from my small accident first 🙄

@dmolineus

Copy link
Copy Markdown
Member Author

Fine, gonna have to take a look at the accordion bundle. Get well soon

dmolineus and others added 4 commits April 29, 2026 11:30
- Deprecates `bs_gridStart`, `bs_gridSeparator`, and `bs_gridStop`, recommending `bs_grid_wrapper` instead.
- Adds `enable_legacy_elements` configuration to toggle legacy elements.
- Updates documentation and adds guardrails for deprecated elements.
@dmolineus dmolineus merged commit 55181ea into develop Jun 5, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants