Davis Simiyu Wanyonyi

Menu Visibility Control is a lightweight, privacy-friendly WordPress plugin that lets you decide exactly who sees each menu item, directly inside the WordPress menu editor.
No settings pages. 
No lock-in. 
No performance overhead.
Everything is managed where it belongs: Appearance → Menus.
<h3>👁️ Visibility Options Per Menu Item</h3>
You can control visibility based on:
<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>
All conditions are optional and safely combined.
<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 Appearance → Menus</li>
<li>Works with any theme or page builder</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>
Unlike large menu or membership plugins, this plugin:
<ul>
<li>Uses only WordPress core hooks</li>
<li>Stores minimal metadata</li>
<li>Is compatible with caching, multilingual sites, and block themes</li>
<li>Does not track users or collect data</li>
</ul>
It does one thing — and does it well.
<h3>Support</h3>
Need help or want to share feedback?
<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>
This plugin is licensed under the GPL v2 or later.
You are free to use, modify, and redistribute it under the same license.
Code is Poetry. ❤️

Menu Visibility Control

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

Tessa (they/them), AuRise Creative

Contact Form 7 is an excellent WordPress plugin and one of the top choices of free WordPress plugins for contact forms. Controller Fields makes it even more awesome by adding dynamic content capabilities. This plugin provides new form tags for select fields, checkboxes, and radio buttons so you can use them to control the display of other fields and content. Some examples might include:
<ul>
<li>Hiding or revealing additional form fields based the current value in a dropdown</li>
<li>Hiding or revealing content when users click a checkbox</li>
<li>Hiding or revealing information based on which radio button is currently selected</li>
<li>Controllers and controlled fields can be nested</li>
</ul>
The possibilities are endless!
<h4>View Demo</h4>
<a href="https://wordpress.org/plugins/controller-fields-for-contact-form-7/?preview=1" rel="ugc">Preview this plugin</a> in the WordPress Playground, a sandbox environment where you can explore the features of this plugin, both in the WordPress backend as an admin user and on the frontend.
<h4>WHAT DOES IT DO?</h4>
This plugin creates three (3) new form tags for controlling the appearance of other form tags (aka “controller”) and a special form tag generator button to output the HTML needed to wrap the controllable form tags inside.
<h4>HOW TO USE IT</h4>
After installing and activating the plugin, you will have four (4) new buttons at the top when creating or editing a Contact Form 7 form: select controller, checkbox controller, radio controller, and controlled form tag wrapper. Most of the options in their tag generators will be familiar to Contact Form 7 users but there have been some upgrades.
Id Attribute
The frontend script relies on unique IDs for the controller form tags, so be sure to always set one!
Options
There are three (3) ways you can define your options. The first method is simply typing your options with each one on a new line, e.g.:
<pre>Apples
Bananas
Dragonfruit</pre>
The second method is similar, but it allows you more control over the value and label by using <code>|</code> to separate them, e.g.:
<pre>fruit_1 | Apples
fruit_2 | Bananas
fruit_3 | Dragonfruit</pre>
The third method is dynamic in that you can use a shortcode to populate your options with two important provisions:
<ol>
<li>The shortcode should NOT include the normal square brackets (<code>[</code> and <code>]</code>). So, instead of <code>[my_shortcode key='value']</code> you would use <code>my_shortcode key='value'</code>.</li>
<li>Any parameters in the shortcode must use single quotes. That is: <code>my_shortcode key='value'</code> and not <code>my_shortcode key="value"</code></li>
</ol>
Shortcodes used here should return a string value with the option or option group HTML.
Default value
This field can take static text or a shortcode. If using a shortcode, the same syntax applies from the options field. However, this field also has a few more needs:
<ol>
<li>The text/shortcode must first have apostrophes converted to it’s HTML entity code, <code>'</code></li>
<li>After that, it must be URL encoded so that spaces become <code>%20</code> and other non-alphanumeric characters are converted.</li>
</ol>
Placeholder
Only available for the select controller form tag, this field can take static text or a shortcode. If using a shortcode, the same syntax applies from the options field. However, this field also has a few more needs:
<ol>
<li>The text/shortcode must first have apostrophes converted to it’s HTML entity code, <code>'</code></li>
<li>After that, it must be URL encoded so that spaces become <code>%20</code> and other non-alphanumeric characters are converted.</li>
</ol>
Read Only Attribute
Simply check this box if you do not want to let users edit this field. It will add the <code>readonly</code> attribute to your form field.
Disabled Attribute
Simply check this box if you do not want to submit this field in the form. It will add the <code>disabled</code> attribute to your form field.

Controller Fields for Contact Form 7

Hide or display content in your forms created in Contact Form 7 based on user selections!

Menu Visibility Control vs Controller Fields for Contact Form 7