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.

Freemius

cyclonecode

This plugin can be used to customize php settings for you WordPress installation.
The plugin will modify either the .htaccess file or .user.ini file in order to change the current php settings directly from within the settings page.
Since the configuration file needs to be modified this file must be writable for this plugin to work as expected.
<h4>Apache module</h4>
When PHP is running as an Apache module the .htaccess file will be used to set customized settings; make sure so that this file exists and is writable by the webserver.
<h4>CGI/Fast-CGI</h4>
If instead PHP is running in CGI/Fast-CGI mode then a custom INI file will be used. The name of this file depends on the value of user_ini.filename in the php configuration, by default it is .user.ini. 
You can check the name of you custom INI file in the PHP Information table. The custom INI file should be placed under the root folder and most be writable by the webserver.
Notice that there is also a User INI file cache TTL value in the information table, this value tells how long the custom INI file will be cached before it gets reloaded. 
For instance, if this value is set to 300 then any changes to your custom INI file will not be reflected for up to 5 minutes. The name for this setting in the php configuration is user_ini.cache_ttl.
One important thing is to make sure that your <code>.user.ini</code> file is blocked by your webserver. If you are running NGINX this can be done by adding:
<pre><code>location ~ /\.user\.ini {
 deny all;
}
</code></pre>
to your server configuration. The same thing using Apache is done by adding the following to the configuration if not already done:
<pre><code><Files .user.ini>
order allow,deny
deny from all
</Files>
</code></pre>
<h4>Available Settings</h4>
The settings table will display all non-system php settings that can be customized by the plugin. All modified settings will be displayed in red in this table.
Some settings might be displayed in red because they are changed somewhere else, perhaps through a customized php.ini file, by WordPress itself, a plugin or in some other way. 
For instance if you have enabled WP_DEBUG in your wp-config.php file the error_reporting setting will turn red.
If you have questions or perhaps some idea on things that should be added you can also try <a href="https://join.slack.com/t/cyclonecode/shared_invite/zt-6bdtbdab-n9QaMLM~exHP19zFDPN~AQ" rel="nofollow ugc">slack</a>.
<h4>Multiple Configurations</h4>
The premium version adds support for creating multiple named configurations which all can hold their own custom PHP settings. 
You will then be able to easily switch between the different configurations entries applying them to you configuration file.
<h4>Environment Variables</h4>
In the premium version, when running PHP as an apache module and using an .htaccess file for configuration, you are able 
to add custom environment variables. These will be accessible by using the super global $_SERVER array. 
In order for this to work you will need to have the mod_env module enabled in your apache setup.
<h4>Resources</h4>
A complete list of settings that can be modified can be found here: <a href="http://php.net/manual/en/ini.list.php" rel="nofollow ugc">List of php.ini directives</a> 
Notice that directives marked as <code>PHP_INI_SYSTEM</code> can not be modified.
<h3>Warning</h3>
Make sure you know how a value should be configured and what different settings do before changing anything. 
This is important since some settings might render your page inaccessible, depending on what value you are using. 
A good example of this is the variables_order configuration:
<blockquote>
Sets the order of the EGPCS (Environment, Get, Post, Cookie, and Server) variable parsing. For example, if variables_order is set to “SP” then PHP will create the superglobals $_SERVER and $_POST, but not create $_ENV, $_GET, and $_COOKIE. Setting to “” means no superglobals will be set.
</blockquote>
If this value would be configured to EPCS then no $_GET superglobal would be set which would make your page inaccessible.
Another example is setting the post_max_size to a very low value so that no form data is sent to the server, which in turn would result in that form data is never saved.
If you by mistake changed some value and your site is now inaccessible you could simply manually remove everything from between the plugin markers in your .htaccess file:
<pre><code># BEGIN CUSTOM PHP SETTINGS PRO
php_value variables_order EPCS <-- Remove
# END CUSTOM PHP SETTINGS PRO
</code></pre>
If you are running PHP in CGI/Fast-CGI mode then instead remove everything between the plugins markers in your .user.ini file:
<pre><code>; BEGIN CUSTOM PHP SETTINGS
php_value variables_order EPCS <-- Remove
; END CUSTOM PHP SETTINGS
</code></pre>
<h3>Support</h3>
If you run into any trouble, don’t hesitate to add a new topic under the support section: 
<a href="https://wordpress.org/support/plugin/custom-php-settings/" rel="ugc">https://wordpress.org/support/plugin/custom-php-settings/</a>
You can also try contacting me on <a href="https://join.slack.com/t/cyclonecode/shared_invite/zt-6bdtbdab-n9QaMLM~exHP19zFDPN~AQ" rel="nofollow ugc">slack</a>.

Custom PHP Settings

Thanks for the awesome plugin. Now I no need to modify the php.ini file manually! Timesaver! Nearly 99% works.

No need to modify the php.ini file manually!

This plugin makes it possible to override php settings.

Htaccess Secure Files vs Custom PHP Settings