Block Visibility vs Content Visibility for Divi Builder

Easily create dynamic content in WordPress that will increase conversions, enhance the user experience, and improve your workflow. With this no-code solution, control which blocks are visible on your website and who can see them. Schedule content to show or hide at a specific time. Display exclusive promotions to your customers or members. Restrict blocks to specific user roles, screen sizes, query strings, WooCommerce products, EDD downloads, ACF fields, WP Fusion tags, and more. Block Visibility is built exclusively for the WordPress Editor (Gutenberg) and is designed to work with any WordPress block. This includes blocks natively provided by WordPress, third-party blocks, and even block-based widgets. Create Conditional Blocks in Seconds! Work directly in the WordPress Editor with blocks you’re already familiar with. There is no external editor or new interface to learn. In seconds, you can transform static blocks into conditional and personalized content. It takes just 3 simple steps: Create your content using any WordPress block. Select the desired visibility conditions. Save the page/post and marvel at the results! Packed With Features Visibility Controls determine whether a block should be visible to users on the front end of your website. Features include: Hide blocks from all users. Schedule when content should be visible using a start and end date/time. Conditionally display blocks based on screen size (Desktop, Tablet, Mobile, and more) Only show blocks to logged-in users. Only show blocks to logged-out users. Only show blocks to users with specific roles (Administrator, Subscriber, Customer, Member, etc.) Only show blocks to specific users. Great for personalization. Show or hide dynamic blocks based on URL query strings. Great for marketing campaigns! Show or hide blocks based on their location and “attributes” of their location (post type, taxonomy, archive, etc.) Display blocks based on a website visitor’s referral source (domain/URL). Support for all post and user metadata (custom fields). Display blocks based on HTML cookies. WooCommerce: Show or hide blocks based on products, cart contents, customer purchase history, and more. Advanced Custom Fields (ACF): Control the visibility of block content based on ACF fields. Easy Digital Downloads: Show or hide blocks based on downloads, cart contents, customer purchase history, and more. WP Fusion: Combine Block Visibility with the power of WP Fusion to conditionally show or hide content based on data from your favorite CRM or marketing automation platform. PLUS: Powerful Settings allow you to customize Block Visibility to your needs or those of your clients. Visibility Presets allow you to control multiple blocks at once. Globally disable any visibility control. Restrict visibility controls to specific block types. Set permissions so only certain users have access to visibility conditions. Configure up to 4 different breakpoints to optimize the screen size controls. Disable contextual indicators and other plugin utilities. Customize the contextual indicator color to enhance theme compatibility. Enable Full Control Mode 🚀 (See the FAQs). Remove all plugin settings on uninstall. Why Do I Need This? While there are countless applications for conditional blocks, here are a few examples to get you started: Use as a content management tool. Hide new blocks while working on them, but keep the page published. Temporarily hide seasonal content on your website rather than having to delete it. Schedule time-sensitive promotional content or event information to display automatically. Show or hide specific content on desktops, tablets, or mobile devices. Restrict content so it’s only visible to your customers, members, or subscribers. Display messaging to logged-out users, encouraging them to subscribe to your blog. Create unique marketing campaigns using query string parameters to display personalized messaging (See it in action) Conditionally display elements in the Site Editor using advanced visibility logic. Increase visitor engagement and conversions with dynamic content and personalization. Why Choose Block Visibility? 1. Easy to Use Block Visibility is the easiest way to create conditional blocks in WordPress. All with no code and just a few clicks! 2. A Balance of Power and Simplicity Block Visibility is for you whether you’re building a sophisticated time-based promotional campaign for your customers or need to hide a few blocks on mobile. Don’t need certain functionality? Toggle it off in the plugin settings. 3. Helpful Support and Continuous Development Block Visibility is designed, developed, and supported by Nick Diego with contributions from the broader Block Visibility community. Have an idea for additional block logic? Let us know in the plugin support forum. Knowledge Base (Documentation) Support Forum For an unbiased review, the plugin was featured on WordPress Tavern. Plays nice with others Block Visibility is designed to work with any block and is tested with these top block libraries and plugins. Compatibility + Direct Integration WooCommerce Advanced Custom Fields Easy Digital Downloads WP Fusion Stay Connected Stay up-to-date on Block Visibility using the links below. The plugin is also being developed transparently on GitHub, so give it a star and follow along! 😉 Plugin Website Knowledge Base YouTube Channel Follow on Twitter View on GitHub

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! Developer Filters Expression Validation Filters The following filters allow developers to customize expression validation behavior. Add these filters in your theme’s functions.php or in a custom plugin. content_visibility_for_divi_builder_blocked_functions 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 file_get_contents (blocked by default): add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) { return array_diff( $functions, array( 'file_get_contents' ) ); } ); Example – block an additional function: add_filter( 'content_visibility_for_divi_builder_blocked_functions', function( $functions ) { $functions[] = 'my_dangerous_function'; return $functions; } ); content_visibility_for_divi_builder_allowed_tokens 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): add_filter( 'content_visibility_for_divi_builder_allowed_tokens', function( $tokens ) { $tokens[] = T_VARIABLE; return $tokens; } ); content_visibility_for_divi_builder_allowed_chars Filter the array of allowed single-character tokens. Characters not in this list (such as =, ;, {, }, `, @, &, |, ~, ^) will cause an expression to fail validation. Example – allow the & character for bitwise operations: add_filter( 'content_visibility_for_divi_builder_allowed_chars', function( $chars ) { $chars[] = '&'; return $chars; } ); content_visibility_for_divi_builder_allowed_callables Filter the array of callables (function names and Class::method static-method entries) the validator considers known-safe. Anything not on the allowlist (and not on the blocked_functions denylist) is treated as an “Unknown callable” error. Names are normalized (leading \ stripped, namespace\ keyword prefix stripped, lowercased) before comparison, so \My\Namespace\Class::method, My\Namespace\Class::method, and namespace\My\Namespace\Class::method all match the same allowlist entry. The default list ships with WordPress conditional tags (is_user_logged_in, current_user_can, is_admin, 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: add_filter( 'content_visibility_for_divi_builder_allowed_callables', function( $callables ) { $callables[] = 'mytheme_should_be_visible'; $callables[] = 'MyTheme\Visibility\Service::checkUser'; return $callables; } );