Following a little 🐛 into a 🐰 hole #952
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR should help illustrating a problem; it's not (primarily meant to be merged)!
I was thinking about #528 and the long thread @mauteri had with Ed on the GatherPress slack, where they talked (among other things) about the default blocks that gets pre-populated when a New Event is created.
After a while .... I asked myself why GatherPress is not using the modal, provided by WP core since 5.8, that allows to select a starter-pattern for
core/post-content
. With an addition (I guess for WP 6.7) a user can now even disable this modal permanently for a given post_type, which would help GatherPress' work on #528.I just wanted to try this fast, and if it could be made compatible with the new
register_block_template()
to create a UI for GatherPress starter-patterns for the post-content.It took me a loooong while to find two weird 🐛s that prevented the modal from appearing.
Bildschirmaufzeichnung.vom.16.10.2024.11.04.03.mp4
Description of the Change
Closes #
How to test the Change
Changelog Entry
Credits
Props @username, @username2, ...
Checklist: