Make WordPress Core

Changes between Version 21 and Version 31 of Ticket #52920


Ignore:
Timestamp:
05/17/2021 03:09:30 PM (3 years ago)
Author:
gziolo
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #52920

    • Property Keywords needs-dev-note added
  • Ticket #52920 – Description

    v21 v31  
    2020New filters are introduced that are context-aware:
    2121- `allowed_block_types_all`
    22 - `allowed_block_types_{$editor_name}`
    2322- `block_categories_all`
    24 - `block_editor_preload_paths_{$editor_name}`
    2523- `block_editor_settings_all`
    26 - `block_editor_settings_{$editor_name}`
    27 
    28 In the case where there are two filters for a general use case that covers any editor type and a specific one, I followed #46187 and the implementation for `render_block` + `render_block_{$block_name}`. @johnbillion shared more examples in https://core.trac.wordpress.org/ticket/46187#comment:9:
    29 
    30 > This is a fairly common pattern in core, see for example: `gettext/gettext_{$domain}`, `plugin_action_links/plugin_action_links_{$plugin_file}`, `manage_posts_columns/manage_{$post_type}_posts_columns`, etc. The dynamically named filter should come after the generic one.