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.

jojaba

<p>This plugin makes it possible to restrict the access of posts contained in categories by setting a password and giving the impacted categories. The content and the excerpt of these posts are replaced by a password form that the user can fill out to get access. The WordPress generated feeds are modified (the description is replaced by a sentence that you can define).</p>
<p>Here’s the list of the settings (see screenshots for further infos):</p>
<ul>
<li>Choose between session or cookie authentication</li>
<li>Set the password</li>
<li>Check the categories that has to be protected</li>
<li>Check the users granted to access the categories without password</li>
<li>Tell if the excerpt should be displayed or not in resources listing</li>
<li>Display a custom excerpt before password field</li>
<li>Set the info message that display before the password form</li>
<li>Set the placeholder in password field</li>
<li>Set the error message when typing the wrong password</li>
<li>Set the valdation button text</li>
<li>Set the text replacing the feed item description of protected posts</li>
<li>You can style the form using the available classes</li>
</ul>
<p>Availabe languages : English (1.5), French (1.5), Simplified Chinese (thanks to Changmeng Hu, 1.4), German (1.4).</p>
<p>This plugin uses php Sessions (more secure) or a Cookie (less secure) to keep in mind the authenticated users. The password is crypted before it is stored. The regular feed content is filtered to avoid content display of restricted categories posts.</p>


Access Category Password

protection type COOKIE is insecure.

If User set browser COOKIE, he can access protected posts.
---
protection type がCOOKIEの場合は安全面に問題があります。

ある名称のCOOKIEをブラウザに埋め込めば保護された投稿にアクセス可能で、それはとても簡単にできます。

The protection type "COOKIE" is deprecated as insecure.

Protects posts in categories by setting a unique Password for all restricted categories.

JVM Protected Media vs Access Category Password