-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Block Hooks: Apply to Post Content (on frontend and in editor) #7898
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
ockham
wants to merge
20
commits into
WordPress:trunk
from
ockham:update/apply-block-hooks-to-post-content-and-editor
Closed
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
0711c61
Block Hooks: Apply to Post Content (on frontend)
ockham b40dd94
Solve by using a default instead
ockham 20a5470
Insert hooked block into editor
ockham 90abff4
Update PHPDoc
ockham 0b844b3
Set ignoredHookedBlocks in REST API response
ockham 838a75e
Also apply to pages
ockham 6793b55
Update PHPDoc
ockham 2958c64
Tweak PHPDoc
ockham 74b39fa
More PHPDoc tweaking
ockham 007d7a4
Temporarily remove filter
ockham 1d98a27
Bail early if no content is given
ockham c6c8481
Revert "Bail early if no content is given"
ockham f29b288
Tighten checks
ockham a5cb598
Add since PHPDoc
ockham 886d375
Update ignoredHookedBlocks post meta on save
ockham 89b835d
Add back check for post_type
ockham e14db01
Tweak @since PHPDoc
ockham 7635d23
Tweak param description
ockham 2b7d36a
Add comments to clarify removal/re-adding of `the_content` filter
ockham a7693b0
Add test case for context set to null
ockham File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Also apply to pages
- Loading branch information
commit 838a75e7350f6d69183fa1eb522dbd88645f13d2
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about synced patterns
wp/block? Should it be extensible? These post types are special do maybe it’s fine as is but a filter here could be useful.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good point. I guess the
wp_blockpost type should map tocore/block.A filter might make sense here 👍 Something to map post types to block types. (I wonder if we already have a function or data structure to do that somewhere 🤔 )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've finally tested this with a synced pattern, and it's currently not inserting hooked blocks.
Simply adding
elseif ( 'wp_block' === $post->post_type ) { $wrapper_block_type = 'core/block'; }didn't do the trick, so I'll have to look into this a bit more. However, since this PR has been open for a while and seems to be ready otherwise, I'll merge it and tackle synced patterns in a follow-up 😊There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fair. It was also discussed in https://github.com/WordPress/wordpress-develop/pull/7898/files#r1867470796 to add support for every post type. The challenge with Patterns is that they are handled out of the box if they come from files bundled from the theme or when registered with PHP. The last missing puzzle would be a synced version of the pattern.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update: Support for synced patterns was implemented in WordPress/gutenberg#68058 and #8015, respectively.
I've filed a Trac ticket for other CPTs (and filterable post type -- block type mappings): https://core.trac.wordpress.org/ticket/62715