
Block Logic adds a "Block Logic" field to the block editor, that lets you show or hide any block based on conditions.
| Author: | landwire (profile at wordpress.org) |
| WordPress version required: | 6.5 |
| WordPress version tested: | 6.9 |
| Plugin version: | 2.1.5 |
| Added to WordPress repository: | 15-01-2020 |
| Last updated: | 05-01-2026 |
| Rating, %: | 100 |
| Rated by: | 13 |
| Plugin URI: | |
| Total downloads: | 5 419 |
| Active installs: | 300+ |

Click to start download
|
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.
Screenshots

The 'Block logic' field at work in the block editor.
FAQ
Writing Logic Code
Make good use of WP’s own conditional tags. Use operators to combine conditions. See Supported functions and globals section for allowed functions. Functions are extendable via filters.
-
Operators
! (not) to reverse the logic, eg !is_home() is TRUE when this is NOT the home page.
|| (or) to combine conditions. X || Y is TRUE when either X or Y is true.
&& (and) to make conditions more specific. X && Y is TRUE when both X and Y are true.
-
WordPress Conditional Checks
is_home() — just the main blog page
!is_page('about') — everywhere except this specific WP page
is_user_logged_in() — shown when a user is logged in
is_category(array(5,9,10,11)) — category page of one of the given category IDs
is_single() && in_category('baked-goods') — single post that’s in the “baked-goods” category
current_user_can('administrator') — admin-only blocks
strpos($_SERVER['HTTP_REFERER'], "google.com") !== false — blocks to show when clicked through from Google
is_category() && in_array($cat, get_term_children(5, 'category')) — category page that’s a descendant of category 5
in_array(77, get_post_ancestors($post)) — WP page that is a child of page 77
is_page('home') || $post->post_parent == 13 — home page or the page that’s a child of page 13
-
WordPress Post & Term Checks
has_term('special-offer', 'category', $post) — post has a specific category term
get_post_meta(get_the_ID(), 'featured', true) == 'yes' — check a meta field value
get_post_type() == 'product' — current post type is a WooCommerce product
is_sticky() — sticky posts only
has_post_thumbnail() — only posts/pages with a featured image
get_the_category() — fetch post categories (can be used in expressions)
get_the_tags() — fetch post tags
-
WooCommerce-Specific Checks
WC()->cart && WC()->cart->get_cart_contents_count() > 0 — cart has at least one item
WC()->cart && WC()->cart->total > 50 — cart total is more than $50
is_product() && get_post_meta(get_the_ID(), '_sale_price', true) !== '' — product has a sale price
is_product_category('shoes') && WC()->cart — category page “shoes” and cart exists
is_user_logged_in() && WC()->cart && WC()->cart->get_cart_contents_count() > 0 — logged-in user and cart has items
-
ACF Checks (Read-only)
get_field('featured') == true — ACF field “featured” is true
get_sub_field('discount') > 0 — ACF subfield “discount” has a value
get_row() > 0 — there are ACF repeater rows
get_field_object('product_info')['value'] !== '' — check ACF field object value
-
PHP Helpers
in_array('baked-goods', wp_get_post_categories($post)) — category array check
strpos(get_permalink($post), 'sale') !== false — check if permalink contains “sale”
empty(get_post_meta(get_the_ID(), 'stock', true)) — post has no stock meta
count(WC()->cart->get_cart()) > 1 — more than 1 item in cart
time() > strtotime('2026-01-01') — check current timestamp
number_format(WC()->cart->total, 2) — format cart total
round(get_post_meta(get_the_ID(), 'rating', true)) > 4 — rating is greater than 4
Supported functions and globals
Block Logic comes with a set of safe WordPress, WooCommerce, ACF, and PHP helper functions, as well as selected globals and superglobals. These can be used in block logic expressions to control the display of blocks dynamically.
-
Allowed Superglobals
-
Allowed WordPress Globals
-
Allowed WordPress Functions
-
ACF Functions
-
WooCommerce Functions
-
PHP Helpers
Extending the list of allowed functions
Block Logic provides four filters that developers can use to safely extend which functions, globals, and superglobals are available inside block logic expressions.
-
Add custom functions
- Use the
block_logic_allowed_functions filter to make additional functions available in block logic expressions.
-
Example
add_filter('block_logic_allowed_functions', function($allowed) {
$allowed[] = 'my_cart_has_items';
return $allowed;
});
function my_cart_has_items() {
return WC()->cart && WC()->cart->get_cart_contents_count() > 0;
}
-
Usage in a block logic field:
my_cart_has_items()
-
Add extra superglobals
- Use the
block_logic_allowed_superglobals filter to allow additional superglobals like $_SESSION.
-
Example:
add_filter('block_logic_allowed_superglobals', function($allowed) {
$allowed[] = '_SESSION';
return $allowed;
});
-
Usage in a block logic field:
!empty($_SESSION['special_offer'])
-
Add extra WordPress globals
- Use the
block_logic_allowed_globals filter to allow extra global variables.
-
Example:
add_filter('block_logic_allowed_globals', function($allowed) {
$allowed[] = 'my_global_data';
return $allowed;
});
// Somewhere in your theme or plugin
$GLOBALS['my_global_data'] = ['foo' => 'bar'];
-
Usage in a block logic field:
$post->ID == my_global_data['foo']
-
Add completely custom globals
- Use the
block_logic_extra_globals filter to allow any additional global variable in block logic expressions.
-
Example:
add_filter('block_logic_extra_globals', function($allowed) {
$allowed[] = 'my_custom_flag';
return $allowed;
});
// Initialize the global somewhere
$GLOBALS['my_custom_flag'] = true;
-
Usage in a block logic field:
$my_custom_flag && is_user_logged_in()
ChangeLog
2.1.5
Raised version to show updated readme.txt
2.1.4
Raised version to show updated readme.txt
2.1.3
Raised version to show updated readme.txt
2.1.2
Raised version to show updated readme.txt
2.1.1
Raised version to show updated readme.txt
2.1.0
- added filters to extend the functionality
- updated README for new plugin version
2.0.0
- totally reworked and removed all directly evalled code
1.0.8
- recompiled assets to remove console.log
1.0.7
- added logic indicator to mark blocks that have logic applied
1.0.6
- added check for Classic Block, Widget Block or Widget Area Block [‘core/freeform’, ‘core/legacy-widget’, ‘core/widget-area’], as those do not support block attributes
- added limitations to plugin description
- updated dev dependencies
1.0.5
- added check for Classic Block and disabled display of settings there
1.0.0
- Initial Release of the plugin