Block Control

Descrizione

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)
* Login status
* Date (start and end date)
* User roles
* Page types
* Posts of the current post type

Screenshot

  • Block Control settings in the block's sidebar

Installazione

  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, your friendly neighborhood WordPress plugin shop from southern Germany.

Contributing

You can contribute to the code on GitHub.

Recensioni

30 Agosto 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. 👏🏻
28 Agosto 2019
I've used this plugins on two websites now. It works just great. The visibility option for different devices is very useful.
Leggi tutte le recensioni di 2

Contributi e sviluppo

“Block Control” è un software open source. Le persone che hanno contribuito allo sviluppo di questo plugin sono indicate di seguito.

Collaboratori

“Block Control” è stato tradotto in 2 lingue. Grazie ai traduttori per i loro contributi.

Traduci “Block Control” nella tua lingua.

Ti interessa lo sviluppo?

Esplora il Codice segui il Repository SVN iscriviti al Log delle Modifiche. Puoi farlo tramite RSS con un lettore di feed.

Changelog (registro delle modifiche)

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