[wp-trac] [WordPress Trac] #59574: Blocks: No toggle shown for hooked blocks added via filter
WordPress Trac
noreply at wordpress.org
Mon Feb 5 20:43:47 UTC 2024
#59574: Blocks: No toggle shown for hooked blocks added via filter
-----------------------------+------------------------------
Reporter: Bernhard Reiter | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version:
Severity: normal | Resolution:
Keywords: | Focuses:
-----------------------------+------------------------------
Comment (by gziolo):
> My plan is to get the PR that sets the `ignoredHookedBlocks` attribute
on newly inserted anchor blocks (based on the non-contextual information
from the block-types endpoint) ready today, and then work on the new
`hooked-blocks` endpoint controller tomorrow, as it can be seen as a
refinement.
I see, so that would be an additional enhancement. That sounds like a good
plan!
What are the reasons the new endpoint is going to work better than
extending existing endpoints that server templates, template parts,
patterns, and navigation to return a custom field that offers hooked
blocks with the `hooked_block_types` filter applied? These endpoints
already have the proper context set when executed from the editor. I don't
know how difficult would it be to process the list of hooked blocks on the
server, but we wouldn't need any additional network requests.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/59574#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list