WordPress plugin intelligence profile

Custom PHP Settings

This plugin makes it possible to override php settings.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 6.8
Current version2.4.1
WordPress coverageTested up to WordPress 6.8
Minimum stackWP 4.1.0 · PHP 5.6
Directory statusactive
Last directory update20 Nov 202511mo ago
Active installations10K+Adoption metric — not a quality score
WordPress.org rating4.4 / 5 from 15 ratings
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Custom PHP Settings version 2.4.1 as active, updated 11mo ago and tested up to WordPress 6.8.

Overview

About this plugin

This plugin can be used to customize php settings for you WordPress installation.

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

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. 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. cache_ttl.

ini file is blocked by your webserver. If you are running NGINX this can be done by adding:

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:

ini> order allow,deny deny from all </Files>

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.

ini file, by WordPress itself, a plugin or in some other way.

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

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

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.

htaccess file:

# BEGIN CUSTOM PHP SETTINGS PRO php_value variables_order EPCS <-- Remove # END CUSTOM PHP SETTINGS PRO

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:

org/support/plugin/custom-php-settings/

You can also try contacting me on slack.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • apache
  • apache2
  • htaccess
  • php
  • settings
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 6.8

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 6.8.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to6.8
Minimum requirementsWordPress 4.1.0 · PHP 5.6
Update activity20 Nov 202511mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.