Title: Block Control Author: epiphyt Published: Agustus 27, 2019 Last modified: Desèmber 14, 2025 --- Nggoléki Plugin ![](https://ps.w.org/block-control/assets/icon.svg?rev=2812545) # Block Control Dening [epiphyt](https://profiles.wordpress.org/epiphyt/) [Ngundhuh](https://downloads.wordpress.org/plugin/block-control.1.5.1.zip) [Live Preview](https://jv.wordpress.org/plugins/block-control/?preview=1) * [Detil](https://jv.wordpress.org/plugins/block-control/#description) * [Mācā ulang](https://jv.wordpress.org/plugins/block-control/#reviews) * [Pemasangan](https://jv.wordpress.org/plugins/block-control/#installation) * [Pangembangan](https://jv.wordpress.org/plugins/block-control/#developers) [Sokong](https://wordpress.org/support/plugin/block-control/) ## Katrangan Have you ever used WordPress’ new block editor Gutenberg and wished for a way to influence, when and to whom blocks are shown? We’ve been in this situation, that’s why we came up with Block Control. This nifty little plugin allows you to control, whether a block should be displayed under certain circumstances or not. And that’s of course true for both WordPress’ default blocks and blocks added by third-party plugins. You can hide blocks based on: * Device types (desktop, mobile, screen reader) * Login status * Date (start and end date) * User roles * Page types * Posts of the current post type * Page number in numbered pages (in archives and search results) Additionally, you can set an inline formatting to display certain text only for screen readers. ## Gambar conto * [[ * Block Control settings in the block’s sidebar ## Pemasangan 1. Upload the plugin files to the `/wp-content/plugins/block-control` directory, or install the plugin through the WordPress plugins screen directly. 2. Activate the plugin through the ‘Plugins’ screen in WordPress 3. Now you can use the “Visibility” panel, Block Control adds to every block withing the Gutenberg editor. ## FAQ ### How do I use Block Control? After you install and activate Block Control, you will find a new panel “Visibility” added to every blocks right hand side sidebar. Open the panel to choose a condition for the display of a given block. Conditional blocks configured this way will only be displayed under certain circumstances chosen by you. Please note, these conditions will only take effect in the front end of your site, not inside the editor itself. ### Does Block Control work with page caching plugins? As Block Control removes content completely from the source code and not just hides it via CSS, it is mostly incompatible to any caching plugin because it may generate different HTML for every user. ### How to disable post type X from showing up? Since version 1.1.0 you can hide blocks based on post type. Since you maybe have post types that don’t make sense in this context, you can use the filter `block_control_ignored_post_types` to remove them. E.g. if your post type slug is called `my_post_type`, you can use it like this: ``` function my_filter_block_control_post_types( $post_types ) { unset( $post_types['my_post_type']; return $post_types; } add_filter( 'block_control_ignored_post_types', 'my_filter_block_control_post_types' ); ``` ### Who are you folks? We are [Epiph.yt](https://epiph.yt/en/), your friendly neighborhood WordPress plugin shop from southern Germany. ### Contributing You can contribute to the code on [GitHub](https://github.com/epiphyt/block-control). ### How can I report security bugs? You can report security bugs through the Patchstack Vulnerability Disclosure Program. The Patchstack team help validate, triage and handle any security vulnerabilities. [Report a security vulnerability.](https://patchstack.com/database/vdp/block-control) ## Mācā ulang ![](https://secure.gravatar.com/avatar/f4943d966cb0b8fc42eb50c9455160228bc6ac7464ed4d54952c441a5843f2e8? s=60&d=retro&r=g) ### 󠀁[Nach stundenlanger Suche endlich gefunden!](https://wordpress.org/support/topic/nach-stundenlanger-suche-endlich-gefunden/)󠁿 [MrRonTour](https://profiles.wordpress.org/mrrontour/) Maret 18, 2026 Ich habe stundenlang gesucht, gebastelt und bin verzweifelt – nur um einen Block aus- oder einzublenden. Unzählige Plugins getestet, Support-Seiten durchforstet, sogar die KI ist an mir verzweifelt. Dieses Plugin macht genau das, was ich brauche. Klare Empfehlung! ![](https://secure.gravatar.com/avatar/ed2c3ccfe9b4cda57477896d9d36272c56305f9391d72522a07a5a5451bf5926? s=60&d=retro&r=g) ### 󠀁[Nice little helper plugin](https://wordpress.org/support/topic/nice-little-helper-plugin/)󠁿 [Bego Mario Garde](https://profiles.wordpress.org/pixolin/) Agustus 30, 2019 Lovely helper plugin lets you select, if you need to be logged in to see a block in a post or page and whether it should be hidden on certain devices. Currently the plugin description may be a little vague (“it does what?”) but the plugin works right out of the box and may be for many a smart solution for a simple task. Well done, Matthias and Simon. 👏🏻 ![](https://secure.gravatar.com/avatar/64c52b6915961058b9d0cd71a67376c9a2d026a627ce4c29697113f721a2bf9c? s=60&d=retro&r=g) ### 󠀁[It works just smoothly](https://wordpress.org/support/topic/it-works-just-smoothly/)󠁿 [Dennis Hipp](https://profiles.wordpress.org/dionysous/) Agustus 28, 2019 I’ve used this plugins on two websites now. It works just great. The visibility option for different devices is very useful. [ Read all 3 reviews ](https://wordpress.org/support/plugin/block-control/reviews/) ## Contributors & Developers “Block Control” is open source software. The following people have contributed to this plugin. Kontributor * [ epiphyt ](https://profiles.wordpress.org/epiphyt/) * [ Matthias Kittsteiner ](https://profiles.wordpress.org/kittmedia/) * [ Simon Kraft ](https://profiles.wordpress.org/krafit/) “Block Control” has been translated into 3 locales. Thank you to [the translators](https://translate.wordpress.org/projects/wp-plugins/block-control/contributors) for their contributions. [Translate “Block Control” into your language.](https://translate.wordpress.org/projects/wp-plugins/block-control) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/block-control/), check out the [SVN repository](https://plugins.svn.wordpress.org/block-control/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/block-control/) by [RSS](https://plugins.trac.wordpress.org/log/block-control/?limit=100&mode=stop_on_copy&format=rss). ## Caathetan Owahan #### 1.5.1 * Fixed: A block with a start date to hide in the future and with an end date will now correctly be hidden between those two dates #### 1.5.0 * Added: Option to hide based on a numbered page (e.g. in archives) #### 1.4.1 * We added an indeterminate visual display of the “All” checkbox, e.g. while selecting posts. * We fixed displaying post type visibility settings inside the site editor. #### 1.4.0 * We added the possibility to hide inline text for everyone but screen readers. #### 1.3.0 * We added the possibility to patterns to hide them by any post type available. * We extended the list of ignored post types with font families and font faces. #### 1.2.0 * We added the option to disable blocks for screen readers. That means that the block is still visible, but will be ignored by screen readers entirely. #### 1.1.12 * We fixed all variants of hide by date setting to be properly checked. #### 1.1.11 * We fixed the hide by date setting if only one of the dates is used. #### 1.1.10 * We fixed the hide by date setting if both settings are in the future or both are in the past. * We improved the settings for hide by date for better accessibility and functionality. #### 1.1.9 * We fixed a problem with some blocks no more saving the visibility settings. #### 1.1.8 * We fixed a problem with broken blocks after updating to version 1.1.7. The editor now doesn’t contain any classes from Block Control anymore. #### 1.1.7 * We fixed compatibility with dynamic blocks. #### 1.1.6 * We improved the ability to use the filter `blockControl.unsupportedBlocks` without needing to load the own JavaScript early. #### 1.1.5 * We added a filter `blockControl.unsupportedBlocks` to filter the list of unsupported blocks. * We disabled Block Control for the SimpleTOC block in order to display it properly in the backend. #### 1.1.4 * We disabled Block Control for the Polylang language switcher in order to display it properly in the backend. #### 1.1.3 * We added full support for WordPress 6.1 (replaced a deprecated function). #### 1.1.2 * We fixed a potential error in blocks in the widget area. #### 1.1.1 * We fixed a dependency problem, which may result in preventing the settings panel to appear. #### 1.1.0 * Since the originally planned Pro version will never be completed, we decided to merge its code into the free version of Block Control. * Hide blocks based on roles * Hide blocks based on dates * Hide blocks based on page types (`is_home`, `is_page`, etc.) * Hide blocks based on posts of the current post type (useful especially for reusable blocks) #### 1.0.4 * We fixed a problem with assets loading in the backend #### 1.0.3 * We fixed a problem while checking for block attributes #### 1.0.2 * We fixed a problem that may load multiple editor scripts in the frontend even if they are not needed there * We fixed a problem where Block Control options won’t be available for certain blocks #### 1.0.1 * We fixed the internationalization for all strings #### 1.0.0 * Initial release ## Community plugin This plugin is developed and supported by a community. [Contribute to this plugin](https://github.com/epiphyt/block-control/) ## Meta * Version **1.5.1** * Last updated **4 wulan sing kepungkur** * Active installations **100+** * WordPress version ** 6.2 or higher ** * Tested up to **6.9.4** * PHP version ** 5.6 or higher ** * Languages * [English (US)](https://wordpress.org/plugins/block-control/), [French (France)](https://fr.wordpress.org/plugins/block-control/), [German](https://de.wordpress.org/plugins/block-control/), and [Swedish](https://sv.wordpress.org/plugins/block-control/). * [Translate into your language](https://translate.wordpress.org/projects/wp-plugins/block-control) * Tags * [block](https://jv.wordpress.org/plugins/tags/block/)[block-editor](https://jv.wordpress.org/plugins/tags/block-editor/) [conditional](https://jv.wordpress.org/plugins/tags/conditional/)[gutenberg](https://jv.wordpress.org/plugins/tags/gutenberg/) [visibility](https://jv.wordpress.org/plugins/tags/visibility/) * [Nonton lanjutan](https://jv.wordpress.org/plugins/block-control/advanced/) ## Peringkat 5 out of 5 stars. * [ 3 5-star reviews ](https://wordpress.org/support/plugin/block-control/reviews/?filter=5) * [ 0 4-star reviews ](https://wordpress.org/support/plugin/block-control/reviews/?filter=4) * [ 0 3-star reviews ](https://wordpress.org/support/plugin/block-control/reviews/?filter=3) * [ 0 2-star reviews ](https://wordpress.org/support/plugin/block-control/reviews/?filter=2) * [ 0 1-star reviews ](https://wordpress.org/support/plugin/block-control/reviews/?filter=1) [Your review](https://wordpress.org/support/plugin/block-control/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/block-control/reviews/) ## Kontributor * [ epiphyt ](https://profiles.wordpress.org/epiphyt/) * [ Matthias Kittsteiner ](https://profiles.wordpress.org/kittmedia/) * [ Simon Kraft ](https://profiles.wordpress.org/krafit/) ## Sokong Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/block-control/)