Simon Kraft

Matthias Kittsteiner

epiphyt

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:
<ul>
<li>Device types (desktop, mobile, screen reader)</li>
<li>Login status</li>
<li>Date (start and end date)</li>
<li>User roles</li>
<li>Page types</li>
<li>Posts of the current post type</li>
<li>Feeds</li>
<li>Page number in numbered pages (in archives and search results)</li>
</ul>
Additionally, you can set an inline formatting to display certain text only for screen readers.
<h4>Contribution</h4>
Feel free to contribute. The code is available at <a href="https://github.com/epiphyt/block-control" rel="nofollow ugc">GitHub</a>.
<h4>Documentation</h4>
You can find the documentation for BLock Control at <a href="https://docs.epiph.yt/block-control/" rel="nofollow ugc">docs.epiph.yt</a>.

Block Control

I've used this plugins on two websites now. It works just great. The visibility option for different devices is very useful.

It works just smoothly

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. 👏🏻

Nice little helper plugin

Block Control allows you to take control of all the blocks on your website. Tailor a unique experience for your visitors.

Jonathan Horowitz

Content Visibility for Divi Builder allows Sections and Modules to be displayed/hidden based on the outcome of a PHP boolean expression.
This plugin is for both the standalone Divi theme (or child themes thereof) and the Divi Builder plugin, version 3 or higher!
<h3>Developer Filters</h3>
<h4>Expression Validation Filters</h4>
The following filters allow developers to customize expression validation behavior. Add these filters in your theme’s functions.php or in a custom plugin.
<code>content_visibility_for_divi_builder_blocked_functions</code>
Filter the array of blocked function names. Functions in this list will cause an expression to fail validation. All comparisons are case-insensitive.
Example – allow <code>file_get_contents</code> (blocked by default):
<pre><code>add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) {
 return array_diff( $functions, array( 'file_get_contents' ) );
} );
</code></pre>
Example – block an additional function:
<pre><code>add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) {
 $functions[] = 'my_dangerous_function';
 return $functions;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_tokens</code>
Filter the array of allowed PHP token types (T_* constants). Tokens not in this list will cause an expression to fail validation. This is an advanced filter – consult the PHP tokenizer documentation before modifying.
Example – allow the T_VARIABLE token type (blocked by default, use with caution):
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_tokens', function( $tokens ) {
 $tokens[] = T_VARIABLE;
 return $tokens;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_chars</code>
Filter the array of allowed single-character tokens. Characters not in this list (such as <code>=</code>, <code>;</code>, <code>{</code>, <code>}</code>, <code>`</code>, <code>@</code>, <code>&</code>, <code>|</code>, <code>~</code>, <code>^</code>) will cause an expression to fail validation.
Example – allow the <code>&</code> character for bitwise operations:
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_chars', function( $chars ) {
 $chars[] = '&';
 return $chars;
} );
</code></pre>
<code>content_visibility_for_divi_builder_allowed_callables</code>
Filter the array of callables (function names and <code>Class::method</code> static-method entries) the validator considers known-safe. Anything not on the allowlist (and not on the <code>blocked_functions</code> denylist) is treated as an “Unknown callable” error. Names are normalized (leading <code>\</code> stripped, <code>namespace\</code> keyword prefix stripped, lowercased) before comparison, so <code>\My\Namespace\Class::method</code>, <code>My\Namespace\Class::method</code>, and <code>namespace\My\Namespace\Class::method</code> all match the same allowlist entry. The default list ships with WordPress conditional tags (<code>is_user_logged_in</code>, <code>current_user_can</code>, <code>is_admin</code>, etc.). The Expression Validation tab’s content scanner generates a ready-to-paste snippet for this filter pre-populated with every custom callable currently in your content.
Example – allowlist a theme helper and a static service method:
<pre><code>add_filter( 'content_visibility_for_divi_builder_allowed_callables', function( $callables ) {
 $callables[] = 'mytheme_should_be_visible';
 $callables[] = 'MyTheme\Visibility\Service::checkUser';
 return $callables;
} );
</code></pre>

Content Visibility for Divi Builder

Thanks for maintaining this plugin. It works great. Some examples in the documentation would make the use at the beginning easier :)

Great PlugIn


I found this addon to be very useful in putting up content for a persons website. It allows you to create PHP functions or use inherent true/false functions that you can then control what content shows based on that. I find it useful in having one content being shown before a certain date and another block being set to show after a certain date. Allowing you to schedule content changes within the website.


Block Control vs Content Visibility for Divi Builder