Block Visibility — Conditional Visibility Control for the Block Editor
Block Visibility — Conditional Visibility Control for the Block Editor is needs configuration with Simply Static. Recommended setup: Simply Static Studio.
About this Plugin
Easily create dynamic content in WordPress that will increase conversions, enhance the user experience, and improve your workflow.
Static WordPress Challenge
Blocks render with the visibility state determined during the static build. Time-, query-string-, user-role/member-, WooCommerce-, EDD-, ACF-, and other request-dependent conditions will not vary per visitor after export; use Static Studio or another live/proxied origin for dynamic evaluation, or rebuild when scheduled visibility changes.
Frequently Asked Questions
Is Block Visibility — Conditional Visibility Control for the Block Editor compatible with Simply Static?
Block Visibility — Conditional Visibility Control for the Block Editor works with Simply Static but needs some configuration. We recommend using Simply Static Studio for the best experience.
Which Simply Static product works best with Block Visibility — Conditional Visibility Control for the Block Editor?
Based on our analysis, Block Visibility — Conditional Visibility Control for the Block Editor works best with Simply Static Studio. Simply Static is for basic static sites, Simply Static Pro adds support for search, forms, and multilingual sites, and Simply Static Studio adds AJAX proxy and REST API support for supported integrations.
Does Block Visibility — Conditional Visibility Control for the Block Editor affect static build times?
Block Visibility — Conditional Visibility Control for the Block Editor has approximately 40,000 active installs. Plugins with complex shortcodes or dynamic blocks may add minor overhead to the static generation pass.
What configuration does Block Visibility — Conditional Visibility Control for the Block Editor need for Simply Static?
Blocks render with the visibility state determined during the static build. Time-, query-string-, user-role/member-, WooCommerce-, EDD-, ACF-, and other request-dependent conditions will not vary per visitor after export; use Static Studio or another live/proxied origin for dynamic evaluation, or rebuild when scheduled visibility changes.
How often is this compatibility data updated?
All plugins are re-scanned monthly. Scans run five analysis passes including an AI classifier. The last tested date at the top of this page reflects the most recent scan.