muis IT

<p>Role Base Access Manager: Media Protector</p>
<p>WordPress plugin to assign access roles to individual files.</p>
<p>This simple plugin allows administrators (anyone with access to the edit-post form for attachments/media) to set access based on roles.<br />
The plugin provides a ‘Security’ meta-box on the right hand side where you can type in role names and select them (much like you add tags<br />
to regular posts). Whenever a visitor wants to download or view a file or image from the uploads directory, his/her current roles are checked<br />
against the configured roles.</p>
<p>This plugin tries to look for originals of resized and rescaled images by making a rough search in the meta data table. This allows you to<br />
mark the original image of a blog entry for specific access and have all thumbnails and other derived images be protected as well. Please note<br />
that this plugin does not clean up after you. If for some reason left-over thumbnails remain in the upload directory, the plugin cannot find<br />
them in the database and will allow access.</p>
<h3>Roles</h3>
<p>This plugin works based on role access management. That means it will try to match the specified roles on the media with the available roles of a user. However, the capabilities system of <code>WordPress</code> is cumulative: an <code>Administrator</code> has more privileges as an <code>Editor</code>, but at least the<br />
same. Usually, people only have one Role in this system. As this plugin does not check on capabilities, but on roles, you will need to specify<br />
<em>all</em> the roles that should have access to this file (including the ‘administrator’ role).</p>
<p>Alternatively, you can add secondary roles to a User, allowing <code>Administrator</code> to also be a <code>Subscriber</code>. In this way, you only need to add the<br />
    Subscriber role to media files to allow it to be downloaded by all registered members. However, adding secondary roles is a manual task. If you have many users and few files, it can be easier to specifiy all roles with the media. If you have many files and few users, you had better use secondary role assignments. If you have many files and many users, you should look into a way to automatically assign roles to people using some sort of on-boarding method. If you need a plugin for that, send me a message.</p>
<h3>Redirections</h3>
<p>The plugin works by inserting a redirection script in your <code>.htaccess</code> file on activation. This does not work properly for <code>NGinX</code>, in which<br />
case you have to insert a redirection manually. Freely copied from the [https://wordpress.org/plugins/aam-protected-media-files/](AAM Protected Media Files) description:</p>
<pre><code>`
</code></pre>
<p>location ~* ^/wp-content/uploads/ {<br />
   rewrite (?i)^(/wp-content/uploads/.*)$ /index.php?rbam-media=1 last;<br />
   return 307;<br />
}<br />
    `</p>
<p>The plugin will try to read the accessed file from the original request and apply role based access management on it.</p>


Role Based Access Manager: Media Protector

Role Based Access Management for Media files (attachments).

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.

Role Based Access Manager: Media Protector vs Menu Visibility Control