landwire

<p>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’ <a href="https://codex.wordpress.org/Conditional_Tags" rel="nofollow ugc">Conditional Tags</a> or any general PHP code.</p>
<h3>Show or hide blocks based on</h3>
<ul>
<li>User role</li>
<li>User login status</li>
<li>Post status</li>
<li>Date and time</li>
<li>The result of a custom PHP function</li>
</ul>
<h3>Features</h3>
<ul>
<li>Show or hide any block using conditions</li>
<li>Combine conditions with “and” or “or” operators. See FAQ Writing Logic Code</li>
<li>Full flexibility: use any condition you want (you can extend base functionality with filters)</li>
</ul>
<h3>Limitations</h3>
<p>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.</p>
<h3>Configuration</h3>
<p>Just activate the plugin. The “Block Logic” textbox will then appear in the “Advanced” section of the Gutenberg editor.</p>
<h3>Breaking changes since 2.0.0</h3>
<p>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.</p>
<h3>Upgrade Notice</h3>
<p>When upgrading to version 2.x you will need to update your logic. No <code>return</code> is allowed anymore and no semicolons in code as only expressions are evaluated. See FAQ Section <strong>Writing Logic Code</strong>.</p>


Block Logic – Full Block Display Control

Works just like widget logic. Excellent plugin and easy to use.

Work With New WordPress Theme Editor

Block Logic adds a "Block Logic" field to the block editor, that lets you show or hide any block based on conditions.

Kaspars

James Collins

<p>Use <a href="https://widgetcontext.com" rel="nofollow ugc">Widget Context</a> to show and hide widgets on certain sections of your site — front page, posts, pages, archives, search, etc. Use targeting by URLs (with wildcard support) for maximum flexibility.</p>
<p><span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/rEHvqsWoXAE?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent" allowfullscreen="true" style="border:0;" sandbox="allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox"></iframe></span></p>
<h4>Premium Support</h4>
<p>Subscribe to our <a href="https://widgetcontext.com/pro" rel="nofollow ugc">Premium Support service</a> and get the PRO 🚀 version of the plugin for free when it’s launched! Your support enables consistent maintenance and new feature development, and is greatly appreciated.</p>
<h4>Contribute</h4>
<ul>
<li>Suggest code improvements <a href="https://github.com/kasparsd/widget-context-wporg" rel="nofollow ugc">on GitHub</a>.</li>
<li>Report bugs and suggestions on <a href="https://wordpress.org/support/plugin/widget-context" rel="ugc">WordPress.org forums</a>.</li>
<li><a href="https://translate.wordpress.org/projects/wp-plugins/widget-context" rel="nofollow ugc">Help translate</a> to your language.</li>
</ul>
<h4>Documentation</h4>
<p>Widget visibility can be configured under individual widget settings under “Appearance <span aria-hidden="true" class="wp-exclude-emoji">→</span> Widgets” in your WordPress administration area or through the widget editing interface in the Customizer.</p>
<h4>Target by URL</h4>
<p>The “Target by URL” is a powerful feature for targeting sections of your website based on the request URLs. It was inspired by a similar feature in the <a href="https://www.drupal.org" rel="nofollow ugc">Drupal CMS</a>.</p>
<p>Use relative URLs such as <code>page/sub-page</code> instead of absolute URLs <code>https://example.com/page/sub-page</code> because relative URLs are more flexible and make the logic portable between different domains and server environments.</p>
<h4>Wildcards</h4>
<p>Use the wildcard symbol <code>*</code> for matching dynamic parts of the URL. For example:</p>
<ul>
<li>
<p><code>topic/widgets/*</code> to match all posts in the widgets category, if your permalink structure is set to <code>/topic/%category%/%postname%</code>.</p>
</li>
<li>
<p><code>page-slug/*</code> to match all child pages of the page-slug parent page.</p>
</li>
<li>
<p>Use a trailing <code>?*</code> to capture URL with all query arguments such as <code>utm_source</code>, etc. For example, for every <code>blog/post-slug</code> also include <code>blog/post-slug?*</code>.</p>
</li>
</ul>
<h4>Exclude by URL</h4>
<p>Specify URLs to ignore even if they’re matched by any of the other context rules. For example, enter <code>example/sub-page</code> to hide a widget on this page even when “All Posts” is selected under “Global Sections”.</p>


Widget Context

Show and hide widgets on specific posts, pages and sections of your site.

Block Logic – Full Block Display Control vs Widget Context