Custom PHP Settings vs .htaccess Site Access Control

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. Apache module 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. CGI/Fast-CGI 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 .user.ini file is blocked by your webserver. If you are running NGINX this can be done by adding: location ~ /\.user\.ini { deny all; } to your server configuration. The same thing using Apache is done by adding the following to the configuration if not already done: order allow,deny deny from all Available Settings 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 slack. Multiple Configurations 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. Environment Variables 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. Resources A complete list of settings that can be modified can be found here: List of php.ini directives Notice that directives marked as PHP_INI_SYSTEM can not be modified. Warning 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: 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. 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: # BEGIN CUSTOM PHP SETTINGS PRO php_value variables_order EPCS <-- Remove # END CUSTOM PHP SETTINGS PRO If you are running PHP in CGI/Fast-CGI mode then instead remove everything between the plugins markers in your .user.ini file: ; BEGIN CUSTOM PHP SETTINGS php_value variables_order EPCS <-- Remove ; END CUSTOM PHP SETTINGS Support If you run into any trouble, don’t hesitate to add a new topic under the support section: https://wordpress.org/support/plugin/custom-php-settings/ You can also try contacting me on slack.

Using the password protection will give you extra security layer of protection from brute force hacking attacks. Additionally, it’s also an easy way to password protect your entire site, without needing to create separate WordPress users for each visitor. When you enable the password protection, the user won’t be able to see anything – not even see the protected page – until he/she inserts the username/password. You can password protect the whole website, including the administrator pages; you can password protect the administrator pages; or you can password protect the WordPress login page. Free plugin options include: Enabling/disabling the password protection to wp-login.php, WordPress admin pages. Note that you’ll be asked to re-type the .htaccess username/password you created before enabling any of the settings – to ensure that you wouldn’t enable the password protection without even knowing the password yourself! Modifying the existing users: you can change any .htaccess user’s password and remove the users. Adding one .htaccess user. Premium plugin options: Create/modify an unlimited number of .htaccess users; Protect your whole site, making it accessible to only those who have the .htaccess user. If you have any other suggestions, please let us know! You can contact us via http://www.wpsos.io/wordpress-plugin-htaccess-site-access-control/ For more information and support, check out: http://www.wpsos.io/wordpress-plugin-htaccess-site-access-control/