Description
Themes, page builders and WooCommerce often ask for PHP limits that shared hosting does not give by default: “max_input_vars is too low”, “memory exhausted”, “the uploaded file exceeds upload_max_filesize”. DigiNex Limit Booster raises these limits with the right method for each PHP setup and then checks that the change really took effect.
What it sets
memory_limit256Mmax_execution_time180max_input_time180max_input_vars3000upload_max_filesize64Mpost_max_size64M
How it works
- .user.ini – writes a managed block for PHP-FPM / FastCGI / CGI hosts. This is the only way to change
max_input_timeandmax_input_vars, because PHP reads them before WordPress starts. - .htaccess – adds a protected
php_valueblock for Apache mod_php and LiteSpeed, guarded byIfModuleso it cannot break other setups. Skipped on Nginx. - Real self-test – sends a fresh HTTP request to your site and shows the values PHP actually uses. If the server answers with a 5xx error, the previous
.htaccessis restored automatically. - Diagnostics – PHP SAPI,
user_ini.filename,user_ini.cache_ttland the loadedphp.ini, plus a ready-made block for your hosting panel’s PHP INI editor when the host locks the values. - Clean removal – only the plugin’s own blocks are ever touched, and they are removed when you click “Remove plugin settings” or delete the plugin.
Nothing is written when you activate the plugin, and the plugin never changes PHP limits at runtime. You decide when to apply the settings from Tools DigiNex Limit Booster.
DigiNex Limit Booster is made by DigiNex (https://diginex.gr), an IT and web services company in Greece. It is not affiliated with Diginex Limited or any other company with a similar name.
Installation
- Install and activate the plugin.
- Go to Tools DigiNex Limit Booster.
- Click Apply settings and check the “HTTP self-test” row.
- If some values stay low, wait for the time shown in
user_ini.cache_ttl(usually 5 minutes) and click Run self-test again.
FAQ
-
The values are still low after applying. Why?
-
Your host locks them (for example with
php_admin_valuein the PHP-FPM pool) or has disabled per-directory INI files. No plugin can override that. Copy the block from Settings for the hosting panel into your hosting panel’s PHP INI editor, or send it to your host. -
Does it work on Nginx?
-
Yes, through
.user.iniwhen PHP runs as PHP-FPM, which is the usual Nginx setup..htaccessis skipped because Nginx does not read it. -
Which files does it change?
-
The
.user.iniand.htaccessfiles in your WordPress folder (and in the site root, if WordPress lives in a subfolder). Only the block betweenBEGIN DigiNex Limit BoosterandEND DigiNex Limit Boosteris written or removed. -
What happens when I delete the plugin?
-
Its blocks are removed from both files and its saved report is deleted. Files that become empty are deleted.
-
Can I change the values?
-
Yes, with the
dxlb_targetsanddxlb_minimumsfilters, for example in a small must-use plugin:add_filter( 'dxlb_targets', function ( $t ) { $t['memory_limit'] = '512M'; return $t; } ); -
Does it send data anywhere?
-
No. The self-test is a request from your site to your own site.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“DigiNex Limit Booster” is open source software. The following people have contributed to this plugin.
Contributors
Translate “DigiNex Limit Booster” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.0
- First wordpress.org release, formerly “DigiNex Server Limits Fix”.
- Settings are applied only when you click “Apply settings”, never on activation and never at runtime.
- File changes use the WordPress filesystem API.
- The self-test checks all six limits and can be run again at any time.
.htaccessis skipped on web servers that do not read it.- Cleans up blocks left by the older “Server Limits Fix” plugin.