Block Logic – Full Block Display Control vs Ele Conditions for Elementor

Block Logic adds a “Block Logic” field to the “Advanced” section of the block editor (i.e Gutenberg), that lets you show or hide any block based on conditions. You can use WordPress’ Conditional Tags or any general PHP code. Show or hide blocks based on User role User login status Post status Date and time The result of a custom PHP function Features Show or hide any block using conditions Combine conditions with “and” or “or” operators. See FAQ Writing Logic Code Full flexibility: use any condition you want (you can extend base functionality with filters) Limitations Does not work with the Classic Block, Widget Block or Widget Area Block [‘core/freeform’, ‘core/legacy-widget’, ‘core/widget-area’], as the those blocks do not support block attributes. Does also not work with the HTML Block [‘core/html’] inside the Widget Screen, as this one also does not support block attributes there. Configuration Just activate the plugin. The “Block Logic” textbox will then appear in the “Advanced” section of the Gutenberg editor. Breaking changes since 2.0.0 Since version 2.0.0 the code does not get eval’d directly, but there is a whitelist of allowed functions that can be extended via a filter. Upgrade Notice When upgrading to version 2.x you will need to update your logic. No return is allowed anymore and no semicolons in code as only expressions are evaluated. See FAQ Section Writing Logic Code.

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: ⚡ Triggers & Actions (client-side, no page reload) Attach one or more trigger → action pairs to any element. 10 trigger types: Click — user clicks the element Hover — user hovers over the element Delay on load — fires after X milliseconds from page load Scroll into view — fires once when the element enters the viewport Time on page — fires after X seconds the visitor has been on the page Exit intent — fires when the cursor moves toward closing the tab First visit — fires only on the visitor’s very first page load (localStorage) Nth visit — fires on the Nth page load (visit counter in localStorage) A/B Group A / B — fires for visitors randomly assigned to group A or B (persists via localStorage) 9 action types: Show — make the target element visible Hide — hide the target element Toggle — toggle visibility on each trigger Add / Remove / Toggle Class — apply a CSS class (great for CSS animations) Scroll To — smooth-scroll the page to the target element Focus — set browser focus on the target (input fields, etc.) Close Others in Group — hide all siblings sharing a CSS class (accordion pattern) 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. 🎛 Display Conditions (server-side, evaluated at render time) Show or hide elements based on variables, rules, and time windows. Multiple conditions per element with AND / OR logic. Built-in variables include: user_role, is_logged_in, user_id, post_type, post_status, post_age_days, post_word_count, post_has_thumbnail, cart_count, cart_total, current_hour, current_day, current_month, current_year, utm_source, utm_medium, utm_campaign, utm_content, utm_term, and more. Condition types: Simple — compare a variable to a value using ==, !=, >, =, <=, contains, starts_with, ends_with, empty, not_empty Time interval — show element only between two times of day (supports cross-midnight ranges) Date/datetime interval — show element only within a date or datetime window Custom variables — register your own variables via the eleconditions_vars filter in your theme’s functions.php. 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. Developer-friendly Zero dependencies beyond Elementor Fully filterable variable system No inline styles injected into saved content — everything is evaluated at render Note: Requires the free Elementor plugin.