isaacchapman

The Htaccess Secure Files plugin can only be activated on Apache web servers with mod_rewrite enabled, and will automatically raise an error upon activation if this is not the case.
The Htaccess Secure Files plugin allows for setting files to be accessible only to visitors who have a specified IP address or <a title="WordPress role or capbility" href="https://codex.wordpress.org/Roles_and_Capabilities" rel="nofollow ugc">WordPress role or capability</a>. By using <a title=".htaccess files" href="http://en.wikipedia.org/wiki/Htaccess" rel="nofollow ugc">.htaccess files</a> to secure the content instead of a separate directory outside the web root, WordPress’s native media library functionality can be used to upload secure files and link to them from within the visual editor.
By default all built-in WordPress roles will be allowed to access content that is marked as secure. The Settings -> Secure Files admin screen controls which roles, capabilities, and IP addresses are allowed to view or download secured files. If a custom role or capability is desired, there are several <a title="WordPress plugins" href="https://wordpress.org/extend/plugins/search.php?q=roles+capabilities" rel="ugc">WordPress plugins</a> capable of creating and editing roles and capabilities.
Any visitor that matches any selected role, capability, or IP address will be allowed to access secured files.
This plugin works by creating a .htaccess files in the directory of each secured file. If you manually edit the .htaccess file and it becomes corrupt (a 500 Internal Server Error is the most likely symptom), I recommend deleting the .htaccess file and then edit and save each secured item in the media library.

Htaccess Secure Files

Allows securing files in WP's media library to be only accessible to users with specific roles, capabilities, or IP addresses.

antonioandra.de

WP htaccess Control should now really be called WP htaccess and Rewrite Control. It provides an interface to customize the htaccess file generated by WordPress but also its permalinks (author, category, archives, pagination and custom taxonomies). Have a look at the screenshot for a clearer idea of the available options.
Features:
<ul>
<li>Customizing the htaccess file generated by WordPress;</li>
<li>Removing any custom taxonomy’s slug base from permalinks;</li>
<li>Removing the category base from permalinks;</li>
<li>Removing the author base from permalinks;</li>
<li>Customizing the Author Permalink Base;</li>
<li>Customizing Paginated Permalinks (translate the “page” word on permalinks to your own language);</li>
<li>Customization (and canonization) of the Search Permalink Base;</li>
<li>Creation of Category, Author, Tag and Custom Taxonomy based archives (ex: “http://your-site.com/category/stories/2010/12”, “http://your-site.com/author/admin/2010/12/page/2” and “http://your-site.com/tag/wordpress/2010/12”), this will also work if you’ve removed the base slug;</li>
<li>Maintenance mode.</li>
</ul>
Easy to use “Suggested htaccess” rules:
<ul>
<li>Jim Morgan’s htaccess;</li>
<li>Disable directory browsing;</li>
<li>Disable and redirect image hotlinking;</li>
<li>Disable and redirect file hotlinking;</li>
<li>Force canonical url (WWW or non-WWW);</li>
<li>Limit maximum file upload size;</li>
<li>Protect wp-config.php file from access;</li>
<li>Protect .htaccess file from access;</li>
<li>Protect comments.php from spam bots coming from nowhere;</li>
<li>Set 500 error page;</li>
<li>Set 403 error page;</li>
<li>Use mod_gzip if available;</li>
<li>Use mod_deflate if available;</li>
<li>Set admin email on server generated error pages;</li>
<li>Disable ServerSignature on server generated error pages.</li>
</ul>
POT file is included, translations are welcome.
<h3>Known Issues</h3>
I still haven’t tested this under WordPress multisite, issues have however been reported.
<h3>Additional Credit</h3>
Removal of the category base is based on iDope’s WP No Category Base but extended so that it works with category archives (ie.: “http://example.com/my-category/2010/12”).
Search redirection is based on Mark Jaquith’s Nice Search but extended so that it works with custom search base (ie.: “http://example.com/search-base/search-term”).
<h3>Stable Versions</h3>
For WordPress versions above 3.9 use the plugin version 3.4.
For WordPress versions above 3.4 use the plugin version 3.3.
For WordPress versions prior to 3.4 use the plugin version 2.7.2.1.

WP htaccess Control

Interface to customize the permalinks (author, category, archives and pagination) and htaccess file generated by WordPress.

Htaccess Secure Files vs WP htaccess Control