wpseek.com
A WordPress-centric search engine for devs and theme authors



wp_allowed_block_metadata_collection_roots › WordPress Filter Hooks

Since6.7.2
Deprecatedn/a
› apply_filters( 'wp_allowed_block_metadata_collection_roots', $collection_roots )
Parameters:
  • (string[]) $collection_roots List of allowed metadata collection root paths.
    Required: Yes
Defined at:
Codex:

Filters the root directory paths for block metadata collections.

Any block metadata collection that is registered must not use any of these paths, or any parent directory path of them. Most commonly, block metadata collections should reside within one of these paths, though in some scenarios they may also reside in entirely different directories (e.g. in case of symlinked plugins).

Example:

  • It is allowed to register a collection with path WP_PLUGIN_DIR . '/my-plugin'.
  • It is not allowed to register a collection with path WP_PLUGIN_DIR.
  • It is not allowed to register a collection with path dirname( WP_PLUGIN_DIR ).

The default list encompasses the wp-includes directory, as well as the root directories for plugins, must-use plugins, and themes. This filter can be used to expand the list, e.g. to custom directories that contain symlinked plugins, so that these root directories cannot be used themselves for a block metadata collection either.



Related Functions: wp_register_block_metadata_collection, wp_register_core_block_metadata_collection, get_block_metadata_i18n_schema, get_allowed_block_template_part_areas, wp_allowed_protocols, get_allowed_block_types


Related Hooks: rest_block_directory_collection_params, block_type_metadata_settings, rest_comment_collection_params, allowed_block_types_all, allowed_redirect_hosts

Source 

$collection_roots = apply_filters( 'wp_allowed_block_metadata_collection_roots', $collection_roots );