Joris van Montfort

<p>Protect access to all your media files and implement your own custom file access rules using a hook. Works for apache with mod rewrite or nginx with some custom configuration. No Multisite support. This plugin is more or less a development tool for defining your own custom file access rules.</p>
<p>For nginx you will need to modify the config file as nginx does not handle .htacess files. Add the following code:</p>
<pre><code>location ~ "^/wp-content/uploads/(.*)$" {
    rewrite ^/wp-content/uploads(/.*\.\w+)$ /index.php?jvm_protected_media_file=$1;
}
</code></pre>
<h3>Hooks</h3>
<p>Without a custom hook all file access will be disabled. The user will see the 404 page for all requested files. Adding a hook is needed to handle your own file access rules. A simple example that could go into your functions.php:</p>
<pre><code>function my_file_access_rule($file_info) {
    // Implement your own logic here
    $userHasAccess = true;

    if($userHasAccess) {
        // Send the file output if users has access to the file
        JVM_Protected_Media::send_file_output($file_info['path']);
    }
}

add_action( 'jvm_protected_media_file', 'my_file_access_rule');
</code></pre>
<p>The jvm_protected_media_file action has one parameter with the following file information:</p>
<pre><code>Array
(
    [id] => id_of_the_file
    [url] => full/url/to/your/file
    [path] => full/path/to/your/file
    [is_resized_image] => bool (true if the requested file is a image thumbnail or resized version of an image)
)
</code></pre>
<h3>Actions</h3>
<p>Available actions:</p>
<ul>
<li>jvm_protected_media_loaded (fires as soon as the plugin is loaded)</li>
<li>jvm_protected_media_file (fires when a file is requested)</li>
</ul>
<h3>Functions</h3>
<p>To send the output of a file to you can call:</p>
<pre><code>JVM_Protected_Media::send_file_output($fullPathToFile)
</code></pre>


JVM Protected Media

Restrict access to all your media files and implement your own custom file access rules.

edward_plainview

<p>Prevent password resets or changes to specific users or user roles. User-specific exceptions to the sweeping user roles can be set. The user’s password is then protected from modification:</p>
<ul>
<li>In the user’s profile editor</li>
<li>Using the password reset link in the login window</li>
</ul>
<p>The settings are available to either the super admin on the network, or normal admins on a single installation. If you wish to hide the settings completely, put the following in your wp-config.php:</p>
<pre><code>define( 'PLAINVIEW_PROTECT_PASSWORDS_HIDE', true );
</code></pre>
<p>Requires PHP 5.4.</p>


Plainview Protect Passwords

I love that is works well with network sites so I don't have to replicate my settings across each of my sites. 

The only issue I ran into is that only network roles are added to the network settings. Maybe it's by design, but it would be awesome if it picked up the roles from the sites because that is where plugins like User Role Editor and WooCommerce have registered them. In order to protect these I would have to modify the settings for each of my network sites separately. Annoying but totally doable. 

Thanks for the quick and easy solution today!

Gets the job done

Selectively protect passwords from being reset or modified.

JVM Protected Media vs Plainview Protect Passwords