Descrizione
You may have many custom blocking plugins installed, but you may not want (or need) to enable them for all of your posts and pages. This plugin allows you to disable unwanted custom block plugins for each post or page.
Filtering the activation of custom block plugins will allow you to speed up editing in the block editor and use different custom blocks that cause conflicts.
For example, if you use Jetpack plugin, but you don’t need Jetpack custom blocks and you want to clean up your editing screen.
plugin load filter is recommended for speeding up and controlling the dynamic stopping of plugins on the front side.
For more detailed information, there is an introduction page.
Screenshot
Filter setting. 
Setting of each post
Installazione
- Upload the
block-editor-assets-filterfolder to the/wp-content/plugins/directory. - Activate the plugin through the
Pluginsmenu in WordPress - Set up from
block-editor-assets-filterto be added to the Settings menu of Admin mode.
Usage
-
Open the settings page.
- The filter list for the “enqueue_block_editor_assets” action hook at the start of the block editor run is displayed
-
Select the action hook defaults.
- Select ‘add’ for the filter to be activated and ‘remove’ for the filter to be deactivated
-
You can specify whether to set the default or re-set for each Post ID.
-
Note
- Custom blocks loaded without using ‘enqueue_block_editor_assets’ action hook cannot be filtered
Recensioni
Non ci sono recensioni per questo plugin.
Contributi e sviluppo
“Block editor assets filter” è un software open source. Le persone che hanno contribuito allo sviluppo di questo plugin sono indicate di seguito.
Collaboratori
Traduci “Block editor assets filter” nella tua lingua.
Ti interessa lo sviluppo?
Esplora il codice segui il repository SVN, segui il log delle modifiche tramite RSS.
Changelog (registro delle modifiche)
0.9.2
- 2020-9-28
- fix : php warning in action_posts function
0.9.1
- 2020-9-24
- Fixed the use of hardcoats such as wp-content in program.
- Fix sanitization esc_html -> sanitize_text_field
- Use namespaces to avoid class name conflicts.
0.9.0
- 2020-9-23