Title: Block Inserter Filter Author: jgorres Published: September 28, 2026 Last modified: September 28, 2026 --- Search plugins ![](https://ps.w.org/block-inserter-filter/assets/banner-772x250.png?rev=3717356) ![](https://ps.w.org/block-inserter-filter/assets/icon-256x256.png?rev=3717356) # Block Inserter Filter By [jgorres](https://profiles.wordpress.org/jgorres/) [Download](https://downloads.wordpress.org/plugin/block-inserter-filter.2.1.4.zip) * [Details](https://twd.wordpress.org/plugins/block-inserter-filter/#description) * [Reviews](https://twd.wordpress.org/plugins/block-inserter-filter/#reviews) * [Installation](https://twd.wordpress.org/plugins/block-inserter-filter/#installation) * [Development](https://twd.wordpress.org/plugins/block-inserter-filter/#developers) [Support](https://wordpress.org/support/plugin/block-inserter-filter/) ## Description Block Inserter Filter lets administrators hide individual Gutenberg blocks from the block inserter for the whole site — Core blocks, theme blocks and blocks of any plugin — without writing any code. It controls what editors can _insert_; it does not touch existing content and has no effect on the front end. #### Features * Clear admin screen under “Settings Hide Blocks”. * Works with every registered block type: Core, theme and plugin blocks. * Group blocks either by block category (as in the editor) or by namespace. * Embed variations (YouTube, Reddit, Vimeo, TikTok, Bluesky, …) can be hidden individually. * Live search across all blocks and embed variations. * “Toggle all” per group. * Protection list: core blocks (paragraph, heading, list, image, group, columns) are always available as a safety net and cannot be hidden. * Existing content using hidden blocks remains visible — only the insertion of new instances is blocked. * No external dependencies, no tracking, no front-end database load. #### Optional GenerateBlocks integration GenerateBlocks is not required. If it is installed, the plugin adds a few conveniences: * GenerateBlocks and GenerateBlocks Pro blocks are listed in separate groups. * GenerateBlocks Pro blocks are marked with a Pro badge. * Core blocks that GenerateBlocks Pro replaces with an extended variant are hidden automatically while Pro is active and reappear when it is deactivated. #### Security Defense in depth: capability check (`manage_options`), nonce validation, whitelist sanitization on save, consistent output escaping. ## Installation 1. Upload the plugin folder to `wp-content/plugins/` or install the ZIP via Plugins Add New Upload Plugin. 2. Activate the plugin under Plugins. 3. Configure the plugin under Settings Hide Blocks. ## FAQ ### Will existing posts that use hidden blocks be destroyed? No. Content remains intact and renders normally on the front-end. Only inserting new instances from the block inserter is blocked. ### Why can’t I hide “Paragraph” or “Image”? These blocks are hard-protected as a safety net — without them the editor would be practically unusable. If you really need to remove them, use the `allowed_block_types_all` filter in your theme or in a custom plugin. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Block Inserter Filter” is open source software. The following people have contributed to this plugin. Contributors * [ jgorres ](https://profiles.wordpress.org/jgorres/) [Translate “Block Inserter Filter” into your language.](https://translate.wordpress.org/projects/wp-plugins/block-inserter-filter) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/block-inserter-filter/), check out the [SVN repository](https://plugins.svn.wordpress.org/block-inserter-filter/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/block-inserter-filter/) by [RSS](https://plugins.trac.wordpress.org/log/block-inserter-filter/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 2.1.4 * Plugin header: removed `Tested up to` (declared in `readme.txt` only) and `Author URI`, as requested by the WordPress.org plugin review. No code changes. #### 2.1.3 * Translations: the plugin package no longer ships any translation files (`.po`,`. mo`, `.l10n.php`), as requested by the WordPress.org plugin review. All languages, including German and British English, are provided through translate.wordpress. org language packs. Only the `.pot` template remains in `languages/`. #### 2.1.2 * Fix: after saving, the settings page showed two success notices — WordPress core adds “Settings saved.” itself for pages under Settings when `updated=1` is present. The plugin’s own notice is removed. #### 2.1.1 * UI: each group header shows how many blocks of that group are currently hidden(“ N hidden”), updated live while ticking checkboxes or using “Toggle all”. * UI: “Toggle all” is only shown while a group is expanded and is aligned with the second column of the block list; the per-group “Save” button is left-aligned. * UI: the intro text no longer contains a hard line break. * Translations: German (`de_DE`) and British English (`en_GB`) ship with the plugin; further languages (es_ES, fr_FR, it_IT, ja, nl_NL, pl_PL, pt_BR, ru_RU) are maintained in the development repository and submitted through translate.wordpress.org, where language packs are generated. #### 2.1.0 * UI: block groups (category view, namespace view) and the embed variations section are now accordions. All groups start collapsed; a click on the group header opens it. The header is a real button with `aria-expanded` / `aria-controls`, so it works with keyboard and screen readers. Checkboxes in collapsed groups are still submitted with the form. * UI: while searching, groups with matches open automatically; clearing the search collapses them again. #### 2.0.0 * **Rename:** the plugin is now “Block Inserter Filter” (slug, folder, main file and Text Domain `block-inserter-filter`). The previous name “Block Filter for GenerateBlocks” was misleading — the plugin filters any Gutenberg block, GenerateBlocks is only an optional integration. WordPress deactivates the plugin during the folder change; reactivate it under Plugins. * **Prefix:** all globals renamed from `jg_gbbf_` / `JG_GBBF_` / `.jg-gbbf-*` to` jgor_bif_` / `JGOR_BIF_` / `.jgor-bif-*`. A one-shot migration on `admin_init` copies the settings from the previous option keys (`jg_gbbf_*`, or `gbba_*` from versions before 1.5.0) to `jgor_bif_hidden_blocks` and `jgor_bif_hidden_embed_variations` and removes the old keys; Multisite networks get a network-wide sweep. No data loss. * Settings page slug is now `jgor-bif-hide-blocks` (`options-general.php?page=jgor- bif-hide-blocks`). * Uninstall removes the current keys, both legacy key families and the migration sentinels. * Internationalisation: the source language of all user-facing strings, the Plugin Name and the Description is now English. A German (`de_DE`) translation is provided in `languages/` (`.pot`, `.po`, `.mo`, `.l10n.php`). WordPress 6.7 and newer load the bundled files automatically via the `Domain Path` header; WordPress. org language packs take precedence once they exist. * Housekeeping: JS global `jgorBifEditorData`, console output removed from `admin. js`, unused localisation removed, tabs instead of spaces in the class files, `. distignore` added for SVN exports. * Fix: when another plugin sets `allowed_block_types_all` to `false` (no blocks allowed at all), that restriction is now passed through unchanged instead of being replaced by the full block registry minus the hidden blocks. * Removed the `all_plugins` display-name override on `wp-admin/plugins.php`. The plugin is now listed under its real name everywhere. * Fix: the plugin’s own editor script no longer runs on the plugin’s settings page, so icons of hidden embed variations render correctly there. * Uninstall: the catch-all `LIKE 'gbba_%'` cleanup was removed; the two known legacy option keys are still deleted by name. The generic four-letter prefix could have matched options of other plugins. * Multisite: `get_sites()` calls now pass `number => 0`, so networks with more than 100 sites are fully migrated and cleaned up. * Declared compatibility with WordPress 7.1 (`Tested up to`). #### 1.5.1 * Declared compatibility with WordPress 7.0 (`Tested up to`). No code changes. #### 1.5.0 * Refactor: prefix scheme corrected to `jg_gbbf_` / `JG_GBBF_` / `.jg-gbbf-*`. The previous code prefix was `gbba_` / `GBBA_` (from the original plugin slug` generateblocks-bloecke-ausblenden`), which no longer matched the current slug` gb-block-filter`. All globals — constants, classes, top-level functions, options, asset handles, CSS classes, body classes — are renamed accordingly. * Class files in `includes/` renamed from `class-gbba-*.php` to `class-jg-gbbf-*. php`. * Migration: one-shot routine on `admin_init` copies the two existing options ` gbba_hidden_blocks` and `gbba_hidden_embed_variations` to `jg_gbbf_hidden_blocks` and `jg_gbbf_hidden_embed_variations` (only when the new key is still empty, to preserve any value written between the update and the first admin page load). Legacy keys are deleted afterwards. Multisite installations get an additional network sweep from the main site so subsites are migrated even if no admin visits them. * Uninstall: `uninstall.php` now removes both prefix families (`gbba_*` and `jg_gbbf_*`) plus the network-wide sweep sentinel, so no leftover rows remain even if the plugin is deleted right after the update. #### 1.4.1 * Plugin Check compliance fix: shortened the 1.4.0 Upgrade Notice text to stay under the `upgrade_notice_limit` of 300 characters. No code or behavioural changes. #### 1.4.0 * **Rename:** plugin slug, folder name, main file and Text Domain changed to `gb- block-filter`; the displayed Plugin Name is now “Block-Filter für GenerateBlocks”. Existing settings (hidden blocks, hidden embed variations) are preserved because the option names (`gbba_*` prefix) remain unchanged. WordPress may auto-deactivate the plugin during the slug change — reactivate it manually under Plugins. * The plugin overview screen (`wp-admin/plugins.php`) showed the plugin as “GenerateBlocks– Block-Filter (Zusatz)” via a scoped `all_plugins` filter, so it sorted directly under “GenerateBlocks”. (Removed again in 1.6.0.) * `uninstall.php`: now also removes the second option `gbba_hidden_embed_variations`( added in v1.1.0 but previously not cleaned up); adds a defensive `LIKE 'gbba_%'` cleanup that covers any future plugin options and `_transient_gbba_*` / `_transient_timeout_gbba_*` entries. Multisite loop preserved. * `readme.txt`: Installation, FAQ and the older Changelog entries (v1.0.0 – v1.3.6) translated to English. Non-standard header fields (`Author`, `Author URI`, `Plugin URI`) removed from the readme header block — they belong in the PHP plugin header only. `Contributors` slug switched to the WordPress.org user name `jgorres`. New `== Upgrade Notice ==` section added. * `Plugin URI` removed from the main PHP file header (no dedicated plugin landing page). * `languages/index.php`, `assets/index.php`, `includes/index.php` and the root ` index.php` now use a proper `defined( 'ABSPATH' ) || exit;` guard instead of the bare “Silence is golden” stub. #### 1.3.10 * Behavior change for Core blocks that GenerateBlocks Pro replaces (currently ` core/heading` and `core/image`): they are now **automatically hidden** from the block inserter as soon as GenerateBlocks Pro is active. The earlier 1.3.9 behavior( Pro active = user may opt in to hiding) was reversed because the Pro variants are meant to fully replace the Core blocks while Pro is loaded. The block-inserter filter (`GBBA_Block_Filter::filter_blocks`) now merges the user-configured hide list with the auto-hidden list returned by `GBBA_Plugin::get_pro_replaced_blocks()` and applies both in one pass. The settings page shows the affected entries as checked + disabled, with the new “Pro-Variante aktiv” badge and a tooltip explaining the auto-hide. As soon as GenerateBlocks Pro is deactivated, the blocks fall back to the regular “geschützt” badge and reappear in the inserter — no manual cleanup needed. * Internal: `get_protected_blocks()` reverted to a thin wrapper around the `PROTECTED_BLOCKS` constant (always full list). The Pro-aware logic now lives exclusively in `get_pro_replaced_blocks()`, which is consumed both by the inserter filter and by the admin renderer. #### 1.3.9 * Feature: when GenerateBlocks Pro is active, the Core blocks `core/heading` and` core/image` are no longer in the protection list and can be hidden from the inserter. They are shown with a new “GB Pro Variante” badge (instead of “geschützt”), with a hover tooltip explaining that GenerateBlocks Pro provides an extended variant of the block. If GenerateBlocks Pro is not active, both blocks remain protected and keep the “geschützt” badge as before, so the editor stays safe to use on installations without the Pro plugin. * Internal: replaced direct uses of `GBBA_Plugin::PROTECTED_BLOCKS` with the new helper `GBBA_Plugin::get_protected_blocks()`, which dynamically removes the Pro- replaced entries from the protection list. `GBBA_Plugin::is_generateblocks_pro_active()` exposes the detection (uses the `GENERATEBLOCKS_PRO_VERSION` constant defined by GB Pro itself, no extra plugin-list lookup). #### 1.3.8 * Critical fix: every block and embed variation is rendered twice in the settings page DOM — once in the category view and once in the namespace view. Both share` name="hidden[]"` (respectively `name="hidden_embed[]"`), and the HTML5 `hidden` attribute hides the inactive view visually but does **not** exclude its inputs from form submission. Toggling checkboxes in only one view therefore caused the other view to silently re-send the old state, which made the “Hide all” / “Show all” toggle look broken: after saving, all checkboxes appeared checked again, even though they had just been unchecked. The admin script now mirrors every checkbox change (manual click or “Toggle all” button) onto the twin checkbox with the same `name`/`value` in the opposite view, so both views stay in sync and only one state is submitted. Existing data is safe; users who experienced wrongly-hidden blocks should open the settings page once after the update, click“ Toggle all” until the affected groups are emptied, save, and reload the editor. #### 1.3.7 * UX: Legacy / render-only blocks are no longer listed in the admin screen. Some plugins (for example GenerateBlocks 2.x for its `generateblocks/container`) keep an old block registered as a pure server-side renderer so that existing posts continue to render after a refactor. Such blocks never appear in the inserter and therefore cannot be hidden in any meaningful way; previously they were listed anyway, leading to duplicate entries (for example two “Container” rows side by side — one being the new Element block, the other the legacy Container renderer). Detection heuristic: empty `attributes` schema combined with no declared block category. Pro blocks are unaffected, because they are consistently registered via `block.json` and therefore always carry both attributes and a category. #### 1.3.6 * Follow-up fix to 1.3.5: `array_map( 'sanitize_text_field', wp_unslash( $_POST[...]))` is now placed directly in the same expression as the `$_POST` access — WPCS evaluates the `InputNotSanitized` sniff line-by-line, so a sanitization step on the following line was not picked up. #### 1.3.5 * Plugin Check compliance: - Removed the superfluous `load_plugin_textdomain()` call in `class-gbba-plugin. php` — WordPress loads translations automatically via the `Domain Path` header since 4.6. - `$_POST['hidden']` and `$_POST['hidden_embed']` are now additionally filtered through `array_map( 'sanitize_text_field', … )` before the whitelist validation( fixes the `InputNotSanitized` warning). - Marked the `do_action( 'enqueue_block_editor_assets' )` call with a clear ` phpcs:ignore` plus explanation — the Core hook is fired deliberately so that other plugins/themes register their block assets. - `uninstall.php`: renamed the local multisite loop variables `$sites` / `$site` to `$gbba_sites` / `$gbba_site` (fixes the `NonPrefixedVariableFound` warning). - `readme.txt`: translated the Short Description and the `== Description ==` block to English; switched the `Contributors` entry to a valid WordPress.org format. #### 1.3.4 * UX: “Settings” link in the WordPress plugins list — direct jump from Plugins to the plugin configuration page. #### 1.3.3 * UX: tighter column grid — minimum column width 280 px (was 340 px). On 1920 px monitors this yields roughly 6 columns, on 1440 px monitors 4 columns. #### 1.3.2 * UX: in the category view, the block namespace (e.g. `core/paragraph`) is no longer shown as a slug tag. It still appears in the namespace view and on embed variations. #### 1.3.1 * Fix: block icons are now reliably rendered. On the settings page, WordPress core blocks are now explicitly registered client-side via `wp.blockLibrary.registerCoreBlocks()`; previously they were loosely loaded but not present in the block-type registry. * Diagnostic hint in the browser console when block icons cannot be resolved. #### 1.3.0 * Block icons are now displayed between the checkbox and the block name on the settings page — also for embed variations. Rendering via `wp.blockEditor.BlockIcon`. The block-editor assets are loaded on the settings page for this purpose. #### 1.2.1 * Fix: blocks without a declared category (for example GenerateBlocks inner blocks such as `loop-item`, `query-page-numbers`, `query-no-results`) no longer end up under “Uncategorized” but in the group of their own namespace. #### 1.2.0 * UX: “Save” button at the end of every group — no more long scrolling needed. * UX: Pro badge only once in the group heading; redundant per-block Pro badges and the intro badge removed. * Statistics: the number of hidden embed variations is now counted and shown in the intro. #### 1.1.0 * GenerateBlocks Free and GenerateBlocks Pro are shown in separate groups (previously combined). * New section: embed variations (YouTube, Reddit, Vimeo, TikTok, Bluesky, …) can now be removed individually from the editor. Technically via `wp.blocks.unregisterBlockVariation()`. * Filter `gbba_embed_variations` for extending the variation list. * The live search now also covers embed variations. #### 1.0.0 * Initial release. ## Meta * Version **2.1.4** * Last updated **18 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.0 or higher ** * Tested up to **7.1.2** * PHP version ** 8.0 or higher ** * Language * [English (US)](https://wordpress.org/plugins/block-inserter-filter/) * Tags * [admin](https://twd.wordpress.org/plugins/tags/admin/)[block-editor](https://twd.wordpress.org/plugins/tags/block-editor/) [blocks](https://twd.wordpress.org/plugins/tags/blocks/)[gutenberg](https://twd.wordpress.org/plugins/tags/gutenberg/) [inserter](https://twd.wordpress.org/plugins/tags/inserter/) * [Advanced View](https://twd.wordpress.org/plugins/block-inserter-filter/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/block-inserter-filter/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/block-inserter-filter/reviews/) ## Contributors * [ jgorres ](https://profiles.wordpress.org/jgorres/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/block-inserter-filter/)