Themes
All themesNo clustered themes yet.
Market
Conditional Blocks matters only if the evidence supports a paid workflow around protecting form submissions and lead routing, not a list of isolated fixes. The current commercial thesis is: Businesses lose leads when forms, spam controls, email delivery, or CRM handoffs fail. The entry wedge is to verify lead capture end to end and show where submissions, notifications, or integrations break.
Commercial opportunities need traceable source links before they are treated as build-worthy.
77.7% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Build a lead capture reliability plugin for marketing teams, agencies, and lead-generation site owners: Businesses lose leads when forms, spam controls, email delivery, or CRM handoffs fail. The first wedge is to verify lead capture end to end and show where submissions, notifications, or integrations break.
The unmet need is not the individual complaint. It is the recurring business workflow: Businesses lose leads when forms, spam controls, email delivery, or CRM handoffs fail. Current stage: commercial watchlist.
No clustered themes yet.
Pain still appears around compatibility, missing feature despite praise for quality, easy.
Pain still appears around support, missing feature despite praise for easy, reliable.
Pain still appears around compatibility, missing feature despite praise for easy, reliable.
Owned praise to avoid copying: reliable, performance.
Owned praise to avoid copying: easy, quality.
With Block Visibility enabled on WordPress 6.9.4, the post editor fails to load and throws a JavaScript TypeError.
Block Visibility — Conditional Visibility Control for the Block Editor · The editor has encountered an unexpected error. mixed Plugin disables post editing when MailPoet 5.13 and 5.13.1 is installedMailPoet 5.13 and Block Visibility together blanked the post editor on multiple sites until MailPoet released a fix.
Block Visibility — Conditional Visibility Control for the Block Editor · all I get is a blank page instead of the gutenberg editor complaint [Feature request] User defined breakpoints[Feature request] User defined breakpoints: users show compatibility, missing feature, support pain that may indicate a product gap.
Responsive Visibility — Show or Hide Blocks by Device, Custom Breakpoints & Conditions · [Feature request] User defined breakpoints It would be useful to have my own breakpoints. mixed Store “core/interface” is already registered errorStore “core/interface” is already registered error: users show bugs, compatibility, support pain that may indicate a product gap.
Wicked Block Conditions · Store “core/interface” is already registered error I have just this plugin installed and I’m getting this error: data.min.js?ver=fe6c4835cd00e12493c3:2 Store “core/interface” is already registered. mixed Does it work on multisite?Does it work on multisite?: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Wicked Block Conditions · Hi @leninzapata , Yes, it works on multisite. mixed Block conditions gone on 6.3Block conditions gone on 6.3: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Wicked Block Conditions · Block conditions gone on 6.3 The block conditions panel isn’t showing in the block options sidebar after upgrading to WordPress 6.3. complaint User defined functionsUser defined functions: users show missing feature, support pain that may indicate a product gap.
Wicked Block Conditions · All works as expected. complaint Greenshift blocks compatibility in site editorVisibility controls do not work on Greenshift blocks in the site editor, and another user seconded the compatibility request.
Block Visibility — Conditional Visibility Control for the Block Editor · Can you please make this plugin compatible with greenshift blocks, so that it work in site editor too? complaint Blocks remain hidden after disabling “Hide Block” on WordPress 6.9Block Visibility leaves blocks permanently hidden on the front end after users turn hiding off because stale WordPress 6.9 metadata remains in the block.
Block Visibility — Conditional Visibility Control for the Block Editor · leaves the block permanently hidden on the frontend complaint Caching affecting block visibilityBlock Visibility cannot work with certain page caching because dynamic visibility rules are served as static cached content and support says there is no workaround.
Block Visibility — Conditional Visibility Control for the Block Editor · Unfortunately there is no workaround. Block Visibility will not work with certain types of caching mixed Page/Post conditions?Page/Post conditions?: users show bugs, missing feature, support pain that may indicate a product gap.
Wicked Block Conditions · Widget Options has the option to show/hide on certain pages/posts. mixed Blocks display default name in List View when plugin is activeBlocks display default name in List View when plugin is active: users show bugs, compatibility, setup pain that may indicate a product gap.
Visibility Controls for Editor Blocks · IMO there is no conflict with another plugin or anything, I’m testing on WordPress 6.8.1 with only “Visibility Controls for Editor Blocks” plugin enabled. mixed Frontend indicator for Block Visibility usageMultiple users need a frontend/admin indicator to find blocks using visibility rules because auditing many pages manually is difficult.
Block Visibility — Conditional Visibility Control for the Block Editor · I currently have to either: Manually check each page/post in the editor Disable the plugin temporarily mixed Integration with ACF Repeater fieldsThe user wants Block Visibility to recognize ACF repeater subfields for conditional display rules, but support says it is a known limitation with no active feature work.
Block Visibility — Conditional Visibility Control for the Block Editor · the plugin does not recognize these fields. It does find the repeater field, but not the sub fields. complaint It this compatible with WordPress 7.0It this compatible with WordPress 7.0: users show compatibility, support pain that may indicate a product gap.
Wicked Block Conditions · It this compatible with WordPress 7.0 I just wanted to check if anyone has tested this with WordPress 7.0 RC4? complaint Conditions on Custom HTML isn’t savedConditions on Custom HTML isn’t saved: users show bugs pain that may indicate a product gap.
Wicked Block Conditions · Conditions on Custom HTML isn’t saved For some reason, they disappear after it’s saved. mixed About the internationalization of the pluginAbout the internationalization of the plugin: users show bugs, support pain that may indicate a product gap.
Wicked Block Conditions · Here are some useful links about this: Internationalizing JavaScript Internationalization in WordPress 5.0 Hope it helps! mixed php 8.1php 8.1: users show compatibility, support pain that may indicate a product gap.
Wicked Block Conditions · php 8.1 Please fix some Deprecated warnings in php 8.1. mixed How does the “Check a Query String Value” condition work?How does the “Check a Query String Value” condition work?: users show support, setup pain that may indicate a product gap.
Wicked Block Conditions · How does the “Check a Query String Value” condition work? complaint Compare ACF date field to Today’s dateCompare ACF date field to Today’s date: users show support pain that may indicate a product gap.
Block Visibility — Conditional Visibility Control for the Block Editor · The page I need help with: [ log in to see the link] I have classes listed for registration, and I want certain things on the page to be hidden after the registration_end_date (ACF field) has passed. complaint Duplicate “Hide” and “Hide block” options in Block Toolbar (WP 7.0)Duplicate “Hide” and “Hide block” options in Block Toolbar (WP 7.0): users show missing feature pain that may indicate a product gap.
Block Visibility — Conditional Visibility Control for the Block Editor · Duplicate “Hide” and “Hide block” options in Block Toolbar (WP 7.0) With Block Visibility active on WP 7.0, Block Toolbar Dropdown shows two hide options — “Hide” (new core 7.0 block visibility feature) and “Hide block” (from plugin). complaint Hiding “Display conditions” by role, extending with custom conditionsHiding “Display conditions” by role, extending with custom conditions: users show missing feature pain that may indicate a product gap.
Wicked Block Conditions · Hiding “Display conditions” by role, extending with custom conditions Hi guys Great plugin. question Use parent taxonomy as conditionThe user requests visibility rules that can match posts assigned to child terms of a selected parent taxonomy term.
Block Visibility — Conditional Visibility Control for the Block Editor · one could test the visibility not only for one or more certain terms, baut also if the current term of the post is a child of another term complaint Block visiblity on mobile device taking time to show up in mobile deviceDynamic block visibility conflicts with caching so mobile users briefly see desktop or duplicate hero content, and the plugin also lacks geolocation targeting.
Block Visibility — Conditional Visibility Control for the Block Editor · Block Visibility is not designed to work with caching plugins mixed Error on gravity forms blockError on gravity forms block: users show bugs pain that may indicate a product gap.
Wicked Block Conditions · Error on gravity forms block Hi Team, I was using this plugin on one of my sites and it was working fine everywhere but on Gravity Forms Block. mixed wp.compose.withState is deprecated since version 5.8. Please use wp.element.useSwp.compose.withState is deprecated since version 5.8. Please use wp.element.useS: users show support pain that may indicate a product gap.
Wicked Block Conditions · The page I need help with: [ log in to see the link] wp.compose.withState is deprecated since version 5.8. mixed Can’t open the media modal if plugin is activeThe media modal would not open while Block Visibility was active, and disabling the plugin restored it.
Block Visibility — Conditional Visibility Control for the Block Editor · When the block visibility plugin is active i can’t open the media modal editing posts or pages. complaint Problem with Fluent Support pluginBlock Visibility rules for logged-in users appear to make a Fluent Support portal act as if the user is logged out.
Block Visibility — Conditional Visibility Control for the Block Editor · the site behaves as if not logged in — and I am asked (by Fluent Forms) to login. But I am logged in. complaint Your User -> Author User not work for custom user rolesA Block Visibility user needs the Author User condition to work with custom user roles for custom post type templates.
Block Visibility — Conditional Visibility Control for the Block Editor · Can you please make it also work for custom user roles like in my case? complaint Very difficult to Understand How to UseThe reviewer said Block Visibility was too difficult to use out of the box, and the response pointed them to documentation dismissively.
Block Visibility — Conditional Visibility Control for the Block Editor · it is very difficult to use question Apply to Menu ItemsThe user wants category-based visibility rules for main menu items, but the provided guidance addresses Navigation blocks rather than the specific menu-item use case.
Block Visibility — Conditional Visibility Control for the Block Editor · I’m trying to show/hide a main menu item. (Not a menu on an archive page). Is this possible? question Resetting a WordPress Template and Block VisibilityResetting a block template removes an ACF-based visibility rule, forcing the user to re-add the rule set each time.
Block Visibility — Conditional Visibility Control for the Block Editor · I therefore have to re-add the rule set every time I reset my template. mixed Does not support taxonomiesThe reviewer thinks Block Visibility lacks taxonomy support and is useless for their use case, though a commenter says taxonomy rules are available under location settings.
Block Visibility — Conditional Visibility Control for the Block Editor · I realized that it does not support the taxonomies. For me it is useless. question ACF Fields on term template are not working ?Block Visibility could not evaluate ACF fields attached to terms for template block visibility, which support confirmed is a plugin limitation.
Block Visibility — Conditional Visibility Control for the Block Editor · this is a limitation of Block Visibility, not a bug praise Amazing, Highly Useful, PracticalAmazing, Highly Useful, Practical: users show compatibility, missing feature pain that may indicate a product gap.
Block Visibility — Conditional Visibility Control for the Block Editor · Block Visibility adds this function as an easy click-click option within the WordPress editor. praise UsefulUseful: users show support, setup pain that may indicate a product gap.
Block Visibility — Conditional Visibility Control for the Block Editor · Useful It is useful, easy to install, use, setup. praise works wellworks well: users show support, setup pain that may indicate a product gap.
Responsive Visibility — Show or Hide Blocks by Device, Custom Breakpoints & Conditions · works well Installed with no faults and does the job! praise So many possibilitiesSo many possibilities: users show missing feature, pricing pain that may indicate a product gap.
Block Visibility — Conditional Visibility Control for the Block Editor · The free version is very generously featured! praise Simple and lightSimple and light: users show missing feature pain that may indicate a product gap.
Osom Block Visibility · Simple and light I sense it light. praise Flexible & elegantFlexible & elegant: users show setup pain that may indicate a product gap.
Wicked Block Conditions · Nevertheless, the UI is simple and compact.