Abhishek Kumar

<p>RenderWhen for Blocks adds conditional visibility to every block in the WordPress block editor. Decide who sees what, and when, with a panel that reads exactly how you’d say it out loud:</p>
<blockquote>
<p><em>Show this block when the user is logged in.</em><br />
  <em>Show this block when the date is between March 1 and March 31.</em><br />
  <em>Show this block when the device is mobile.</em></p>
</blockquote>
<p>RenderWhen is built around two ideas that set it apart from other visibility plugins:</p>
<ul>
<li><strong>Server-side rendering only.</strong> When a block is hidden by a condition, it is not rendered into the page output at all. No CSS <code>display: none</code>, no DOM bloat, no leaked content in view-source. Search engines, screen readers, and your page weight all benefit.</li>
<li><strong>Public Conditions API.</strong> The three built-in conditions are registered through the same public API your plugin or theme can use to add your own. No hacks, no internal-only code paths.</li>
</ul>
<p>In the editor, a subtle dashed border marks every block that carries a visibility rule, so a rule-bearing block never disappears from the published page as a surprise. A “Preview as audience” sidebar lets you simulate a logged-out visitor, a specific role, or a different device class right in the editor — blocks whose rule would hide them fade out with a clear badge, no save-and-reload cycle required.</p>
<h4>Built-in conditions (v1.0)</h4>
<ul>
<li><strong>User state</strong> — show to logged-in users, logged-out users, or specific roles</li>
<li><strong>Date range</strong> — show between two datetimes, timezone-aware</li>
<li><strong>Device type</strong> — show on desktop, tablet, or mobile</li>
</ul>
<h4>Designed for</h4>
<ul>
<li>Agencies and freelancers building client sites who want a clean, predictable visibility tool</li>
<li>Developers who need an extension point, not another walled garden</li>
<li>Anyone who cares about page weight and SEO hygiene</li>
</ul>
<h4>What this plugin deliberately does NOT do</h4>
<p>It does one thing well rather than ten things adequately. Out of scope in v1.0:</p>
<ul>
<li>Multi-condition AND/OR groups (planned for v1.1)</li>
<li>URL / cookie / referrer / geolocation conditions</li>
<li>WooCommerce, ACF, or membership integrations</li>
<li>A settings dashboard</li>
</ul>
<p>If you need those today, <a href="https://wordpress.org/plugins/conditional-blocks/" rel="ugc">Conditional Blocks</a> and <a href="https://wordpress.org/plugins/block-visibility/" rel="ugc">Block Visibility</a> are excellent and well-established choices.</p>
<h4>For developers</h4>
<p>Register a custom condition in three steps. Implement the interface, add it to the registry, ship.</p>
<pre><code>add_action( 'renderwhen_register_conditions', function ( $registry ) {
    $registry->register( new My_Plugin\\Conditions\\Country_Condition() );
} );
</code></pre>
<p>Your condition class implements <code>RenderWhen\Conditions\Interface_Condition</code>:</p>
<pre><code>namespace My_Plugin\Conditions;

use RenderWhen\Conditions\Interface_Condition;

class Country_Condition implements Interface_Condition {
    public function get_id(): string {
        return 'country';
    }

    public function get_label(): string {
        return __( 'Visitor country', 'my-plugin' );
    }

    public function get_schema(): array {
        return array(
            'type'       => 'object',
            'properties' => array(
                'countries' => array(
                    'type'  => 'array',
                    'items' => array( 'type' => 'string' ),
                ),
            ),
        );
    }

    public function evaluate( array $settings, array $context ): bool {
        $current = my_plugin_detect_country();
        return in_array( $current, $settings['countries'] ?? array(), true );
    }
}
</code></pre>
<p>The full set of public filters:</p>
<ul>
<li><code>renderwhen_register_conditions</code> — register your conditions here</li>
<li><code>renderwhen_evaluate_{condition_id}</code> — last-mile override of any condition’s result</li>
<li><code>renderwhen_render_block_hidden</code> — fires when a block is hidden, useful for cache busters and SEO tools</li>
<li><code>renderwhen_device_type</code> — swap in your own device detection</li>
</ul>
<p>The plugin is developed openly on GitHub. Issues, PRs, and architecture discussions welcome: https://github.com/abhishekfdd/renderwhen</p>


RenderWhen for Blocks

Show or hide any block when conditions match. Developer-first API and true server-side rendering — hidden blocks never reach the browser.

Fernando Tellado

Ayuda WordPress

<p>Widget Visibility Control lets you decide exactly where each widget appears on your site. Show widgets only on specific pages, hide them for logged-out users, display different content for different categories – all without writing a single line of code.</p>
<h4>Looking for Widget Visibility and Scheduling?</h4>
<p>This plugin gives you control over where your widgets appear:</p>
<ul>
<li><strong>Page targeting</strong> – Show widgets on the front page, blog page, specific pages, or 404 error page</li>
<li><strong>Content targeting</strong> – Display widgets only on certain categories, tags, or custom taxonomies</li>
<li><strong>Cascading taxonomy selector</strong> – Quickly find terms in sites with many taxonomies (WooCommerce friendly)</li>
<li><strong>Include child terms</strong> – Match child terms automatically for hierarchical taxonomies</li>
<li><strong>User targeting</strong> – Show different widgets to logged-in users vs. visitors</li>
<li><strong>Role-based display</strong> – Target specific user roles (administrators, editors, subscribers, etc.)</li>
<li><strong>Author pages</strong> – Control visibility on author archive pages</li>
<li><strong>Date archives</strong> – Target daily, monthly, or yearly archives</li>
<li><strong>Post type support</strong> – Works with custom post types and their archives</li>
<li><strong>Time scheduling</strong> – Schedule widgets to appear only during specific date and time ranges. Perfect for promotional banners, seasonal offers, holiday announcements, flash sales, event countdowns, and time-limited content</li>
</ul>
<h4>Multiple Conditions</h4>
<p>Create sophisticated visibility rules by combining multiple conditions:</p>
<ul>
<li>Use <strong>OR logic</strong> – Show if ANY condition matches</li>
<li>Use <strong>AND logic</strong> – Show only if ALL conditions match</li>
<li>Mix and match – Create exactly the rules you need</li>
</ul>
<h4>Built for Performance</h4>
<ul>
<li>Minimal database queries with intelligent caching</li>
<li>Only loads assets where needed (widget screens)</li>
<li>Clean, optimized code following WordPress standards</li>
</ul>
<h4>Why Choose This Plugin?</h4>
<ul>
<li><strong>Lightweight</strong> – Focused functionality without unnecessary features</li>
<li><strong>All features included</strong> – No premium version required</li>
<li><strong>Jetpack Compatible</strong> – Migrate from Jetpack Widget Visibility without reconfiguring anything</li>
<li><strong>Independent Storage</strong> – Your rules are stored separately, safe from Jetpack changes</li>
<li><strong>Block Editor Ready</strong> – Works with both classic widgets and block-based widgets</li>
<li><strong>Privacy Focused</strong> – No external connections, no tracking, no data collection</li>
<li><strong>Safe by design</strong> – No PHP eval, no arbitrary code execution; rules are stored as structured data</li>
</ul>
<h4>Coming from Jetpack?</h4>
<p>If you’ve been using Jetpack just for widget visibility and want to reduce your site’s load, this plugin can help:</p>
<ul>
<li><strong>No configuration needed</strong> – Your existing visibility rules are automatically imported on activation</li>
<li><strong>Same familiar interface</strong> – The visibility panel works as you’re used to</li>
<li><strong>Keep or clean legacy data</strong> – Choose to maintain Jetpack compatibility or clean up completely</li>
<li><strong>No disruption</strong> – Your widgets will continue working as before</li>
</ul>
<h4>Coming from Widget Logic?</h4>
<p>Widget Logic has been closed on the WordPress plugin directory. Widget Visibility Control is a safe, maintained alternative:</p>
<ul>
<li><strong>No PHP eval</strong> – Visibility rules are stored as structured data, not as executable PHP code</li>
<li><strong>Assisted import</strong> – On detection of Widget Logic data, an importer translates the most common conditional tags (is_home, is_page, is_category, is_user_logged_in…) into proper visibility rules. Works with data from both Widget Logic 5.x and 6.x</li>
<li><strong>You decide what’s tricky</strong> – For rules we can’t translate automatically, the importer asks per widget whether to import as always visible, always hidden, or skip</li>
<li><strong>Original data preserved</strong> – Your Widget Logic data stays in the database until you choose to clean it up</li>
</ul>
<h4>Coming from Widget Options?</h4>
<p>If you only use Widget Options for visibility and want a lighter, focused plugin without the pro upsells:</p>
<ul>
<li><strong>No pro version</strong> – All features included in the free plugin</li>
<li><strong>Visibility-first</strong> – We do one thing well: show/hide widgets based on pages, content, users, roles, and schedule</li>
<li><strong>Compatible interfaces</strong> – Works in the block-based widget editor, the classic widget editor, and the Customizer</li>
<li><strong>Quick try</strong> – Install alongside Widget Options to compare; switch when you’re ready</li>
</ul>
<h4>Developer Friendly</h4>
<ul>
<li>Follows WordPress Coding Standards</li>
<li>Fully translatable with complete i18n support</li>
<li>Action and filter hooks for customization</li>
<li>Clean uninstall – removes only its own data</li>
</ul>
<h3>Support</h3>
<p>Need private support or custom development?</p>
<p>Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just <a href="mailto:widget-visibility-control@ayudawp.com" rel="nofollow ugc">contact me</a> and tell me what you need.</p>
<p>Need help or have suggestions?</p>
<ul>
<li><a href="https://servicios.ayudawp.com" rel="nofollow ugc">Official website</a></li>
<li><a href="https://wordpress.org/support/plugin/widget-visibility-control/" rel="ugc">WordPress support forum</a></li>
<li><a href="https://www.youtube.com/@AyudaWP" rel="nofollow ugc">YouTube channel</a></li>
<li><a href="https://ayudawp.com" rel="nofollow ugc">Documentation and tutorials</a></li>
</ul>
<p>Love the plugin? Please <a href="https://wordpress.org/support/plugin/widget-visibility-control/reviews/#new-post" rel="ugc">leave us a 5-star review</a> and help spread the word!</p>
<h3>About AyudaWP</h3>
<p>We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.</p>


Widget Visibility Control

Lightweight conditional widget visibility. Show or hide widgets by page, post type, category, user role, login status, and schedule.

RenderWhen for Blocks vs Widget Visibility Control