- Listing audit
- 49/100
Custom PHP Settings is a WordPress Plugin Directory app by cyclonecode. With a rating of 4.4★ from 15 reviews.
Custom PHP Settings is a WordPress app, with a 4.4 average rating from 15 reviews, as of Sep 11, 2026.
AppRanks verdict
Generated from marketplace data as of Sep 11, 2026
Custom PHP Settings is a WordPress app. It holds a 4.4★ average from 15 reviews on WordPress.
Pros
- No standout positives in the measured data.
Cons
- −Only 15 reviews — the average can still move with a few new ratings
How Custom PHP Settings works
Show full descriptionShow less
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: