Davis Simiyu Wanyonyi

<p><strong>Menu Visibility Control</strong> is a lightweight, privacy-friendly WordPress plugin that lets you decide exactly <strong>who sees each menu item</strong>, directly inside the WordPress menu editor.</p>
<p>No settings pages.<br />
No lock-in.<br />
No performance overhead.</p>
<p>Everything is managed where it belongs: <strong>Appearance <span aria-hidden="true" class="wp-exclude-emoji">→</span> Menus</strong>.</p>
<h3>👁️ Visibility Options Per Menu Item</h3>
<p>You can control visibility based on:</p>
<ul>
<li>👥 Everyone</li>
<li>🔒 Logged-in users</li>
<li>🚪 Logged-out users</li>
<li>🧩 Specific user roles (Administrator, Editor, Subscriber, etc.)</li>
<li>📱 Device type (Desktop / Tablet / Mobile)</li>
<li>📄 Specific pages (auto-detected list)</li>
</ul>
<p>All conditions are optional and safely combined.</p>
<h3>💡 Perfect For</h3>
<ul>
<li>Membership and community websites</li>
<li>Client dashboards and intranets</li>
<li>Multi-role WordPress sites</li>
<li>Sites with mobile-specific navigation</li>
<li>Blogs that need different menus for visitors vs members</li>
</ul>
<h3>🔧 Key Features</h3>
<ul>
<li>Native integration with <strong>Appearance <span aria-hidden="true" class="wp-exclude-emoji">→</span> Menus</strong></li>
<li>Works with <strong>any theme or page builder</strong></li>
<li>Role-based menu visibility</li>
<li>Device-based menu visibility</li>
<li>Page-specific menu visibility</li>
<li>Auto-hidden UI (only shows options when enabled)</li>
<li>Secure (nonces, sanitization, strict validation)</li>
<li>Performance-optimized (runs only during menu rendering)</li>
<li>100% free, open-source, and donation-supported</li>
</ul>
<h3>🧠 Why Use Menu Visibility Control?</h3>
<p>Unlike large menu or membership plugins, this plugin:</p>
<ul>
<li>Uses <strong>only WordPress core hooks</strong></li>
<li>Stores <strong>minimal metadata</strong></li>
<li>Is compatible with caching, multilingual sites, and block themes</li>
<li>Does not track users or collect data</li>
</ul>
<p>It does one thing — and does it well.</p>
<h3>Support</h3>
<p>Need help or want to share feedback?</p>
<ul>
<li>Visit the <a href="https://wordpress.org/support/plugin/menu-visibility-control/" rel="ugc">support forum</a></li>
<li>Leave a <a href="https://wordpress.org/support/plugin/menu-visibility-control/reviews/#new-post" rel="ugc">review</a></li>
<li>Support development via <a href="https://knowledge.buzz/donate" rel="nofollow ugc">donation</a></li>
</ul>
<h3>License</h3>
<p>This plugin is licensed under the <strong>GPL v2 or later</strong>.</p>
<p>You are free to use, modify, and redistribute it under the same license.</p>
<p>Code is Poetry. ❤️</p>


Menu Visibility Control

Control WordPress menu item visibility based on login status, user roles, device type, or specific pages — lightweight and theme-agnostic.

Super Interactive

<h4>How to use</h4>
<p>You can place conditional content between <code>if</code> <a href="https://codex.wordpress.org/Shortcode" rel="nofollow ugc">shortcodes</a>, and use its attributes to define conditions. The content between the shortcodes will only be displayed if all defined conditions are met.</p>
<h4>Defining conditions</h4>
<p>Conditions are defined by setting the attributes of the shortcode in the following format:</p>
<pre><code>[if <type>=<condition>]
 Conditional content
[/if]
</code></pre>
<p>A basic example:</p>
<pre><code>[if qs="product-type:shoes"]
 Thank you for buying shoes
[/if]
</code></pre>
<p>The text in this example will only be displayed if the current URL has a GET paramater of “product-type” with the value “shoes”.</p>
<p>Available condition types are:</p>
<ul>
<li>
<p><strong><code>qs</code></strong> – Match on the key/value pair of the defined query string/GET parameter. Query string conditions are formatted like this:</p>
<pre><code>[if qs="<qskey>:<qsvalue>"] … [/if]

qskey is the name of the query string variable and `qsvalue` the value to test for. For example, the condition `qs="product-type:2"` will match `?product-type=2`.
</code></pre>
</li>
<li>
<p><strong><code>referrer</code></strong> – To check on the current referrer. The condition will be true if <code>HTTP_REFERER</code> contains <code><value></code>. The match doesn’t need to be exact, so if a user arrives from google and <code><value></code> is set to “google.com” the condition will be true.</p>
</li>
<li>
<p><strong><code>role</code></strong> – Matches the current user’s role. The match needs to be exact so “admin” will not match “administrator”. Use <code>role</code> with and empty value if you want to match users that are not logged in.</p>
</li>
</ul>
<h4>Examples</h4>
<p>Display content based on query string:</p>
<p>[if qs=”utm_source:partner-site”]<br />
     This content is only displayed if the current URL contains a GET paramater ‘utm_source’ with value ‘partner-site’<br />
    [/if]</p>
<p>Display content based on referrer:</p>
<pre><code>[if referrer="www.google.com"]
 This content is only displayed if the referring URL contains 'www.google.com'
[/if]
</code></pre>
<p>Display content based on user role:</p>
<pre><code>[if role="editor"]
 This content is only displayed if the user is logged in with the role 'editor'
[/if]
</code></pre>
<p>Setting multiple conditions and combining condition types:</p>
<pre><code>[if referrer="www.example.com" qs="utm_source:partner-site"]
 This content is displayed to users coming from example.com who clicked on a link originating from our RSS feed.
[/if]
</code></pre>
<h4>Matching with `exact` or `contain`</h4>
<p>By default query string conditions are matched on the exact value as defined in the shortcode. For looser ‘wildcard’ matching you can add a <code>match</code> attribute with the value <code>contain</code>:</p>
<pre><code>[if qs="product-type:cashmere-" match="contain"]
 Good choice! Cashmere is a wonderful fabric.
[/if]
</code></pre>
<p>This will match both <code>?product-type=cashmere-sweater</code> and <code>?product-type=cashmere-coat</code></p>
<h4>Matching on multiple values</h4>
<p>You can have a condition match on multiple values by using the semicolon as a seperator when defining allowed values. Example:</p>
<pre><code>[if qs="product-type:shoes;coat"]
  This text is displayed for people who bought either a nice pair of shoes or a great fashionable coat.
[/if]
</code></pre>
<h4>Nesting `if` statements</h4>
<p>You can nest statements but you have to use iteration. This has to do with the limitations of the built-in shortcode API.</p>
<pre><code>[if qs="tonight:the-night"]

  Tonight's the night.

  [if2 qs="future:beautiful"]

    We create our own destiny every day we live.

  [/if2]

  [if2 qs="future:platic"]

    I see sheets of plastic in your future.

  [/if2]

[/if]
</code></pre>
<p>You can nest up to if4 (4 levels).</p>


WordPress Conditional Content

heya,
I really liked your plugin. I think you should upgrade it to the latest version of WordPress. and keep updating. It is a nice plugin.
Cheers!



Impressed

haven't see that Kinda plugin at org. Easy to use and handy Plugin.
You should keep update this.
Thanks :)

Great Job!

Allows you to use shortcodes as if statements in your content to display text only if certain conditions are met.

Menu Visibility Control vs WordPress Conditional Content