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.

dudaster

Ele Conditions for Elementor turns static Elementor elements into interactive, context-aware components — without writing a single line of code.
There are two independent systems, both accessible from the Advanced tab of any widget, section, or container:
<h4>⚡ Triggers & Actions (client-side, no page reload)</h4>
Attach one or more trigger → action pairs to any element.
10 trigger types:
<ul>
<li>Click — user clicks the element</li>
<li>Hover — user hovers over the element</li>
<li>Delay on load — fires after X milliseconds from page load</li>
<li>Scroll into view — fires once when the element enters the viewport</li>
<li>Time on page — fires after X seconds the visitor has been on the page</li>
<li>Exit intent — fires when the cursor moves toward closing the tab</li>
<li>First visit — fires only on the visitor’s very first page load (localStorage)</li>
<li>Nth visit — fires on the Nth page load (visit counter in localStorage)</li>
<li>A/B Group A / B — fires for visitors randomly assigned to group A or B (persists via localStorage)</li>
</ul>
9 action types:
<ul>
<li>Show — make the target element visible</li>
<li>Hide — hide the target element</li>
<li>Toggle — toggle visibility on each trigger</li>
<li>Add / Remove / Toggle Class — apply a CSS class (great for CSS animations)</li>
<li>Scroll To — smooth-scroll the page to the target element</li>
<li>Focus — set browser focus on the target (input fields, etc.)</li>
<li>Close Others in Group — hide all siblings sharing a CSS class (accordion pattern)</li>
</ul>
Target selector: leave empty to act on the element itself, or enter any CSS selector to act on another element anywhere on the page.
Hide Initially: a dedicated switcher that hides the element on load independently of triggers — useful for elements revealed by a trigger.
<h4>🎛 Display Conditions (server-side, evaluated at render time)</h4>
Show or hide elements based on variables, rules, and time windows. Multiple conditions per element with AND / OR logic.
Built-in variables include: <code>user_role</code>, <code>is_logged_in</code>, <code>user_id</code>, <code>post_type</code>, <code>post_status</code>, <code>post_age_days</code>, <code>post_word_count</code>, <code>post_has_thumbnail</code>, <code>cart_count</code>, <code>cart_total</code>, <code>current_hour</code>, <code>current_day</code>, <code>current_month</code>, <code>current_year</code>, <code>utm_source</code>, <code>utm_medium</code>, <code>utm_campaign</code>, <code>utm_content</code>, <code>utm_term</code>, and more.
Condition types:
<ul>
<li>Simple — compare a variable to a value using ==, !=, >, <, >=, <=, contains, starts_with, ends_with, empty, not_empty</li>
<li>Time interval — show element only between two times of day (supports cross-midnight ranges)</li>
<li>Date/datetime interval — show element only within a date or datetime window</li>
</ul>
Custom variables — register your own variables via the <code>eleconditions_vars</code> filter in your theme’s <code>functions.php</code>.
ACF support — pick any ACF field from a searchable dropdown; the value is fetched at render time.
User meta — condition on any WordPress user meta key for the current visitor.
Debug mode — shows a red-bordered overlay with the evaluated variable values, visible only to editors and administrators.
<h4>Developer-friendly</h4>
<ul>
<li>Zero dependencies beyond Elementor</li>
<li>Fully filterable variable system</li>
<li>No inline styles injected into saved content — everything is evaluated at render</li>
</ul>
Note: Requires the free <a href="https://wordpress.org/plugins/elementor/" rel="ugc">Elementor</a> plugin.

Ele Conditions for Elementor

Add interactive triggers and conditional display logic to any Elementor element — show, hide, toggle on click, scroll, exit intent, and more.

Block Control vs Ele Conditions for Elementor