DigiNex Limit Booster

开发者	diginex
更新时间	2026年10月29日 03:41
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

下载

1.0.0

详情介绍:

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_limit 256M
max_execution_time 180
max_input_time 180
max_input_vars 3000
upload_max_filesize 64M
post_max_size 64M

How it works

.user.ini – writes a managed block for PHP-FPM / FastCGI / CGI hosts. This is the only way to change max_input_time and max_input_vars, because PHP reads them before WordPress starts.
.htaccess – adds a protected php_value block for Apache mod_php and LiteSpeed, guarded by IfModule so 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 .htaccess is restored automatically.
Diagnostics – PHP SAPI, user_ini.filename, user_ini.cache_ttl and the loaded php.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.

安装:

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.

常见问题:

The values are still low after applying. Why?

Your host locks them (for example with php_admin_value in 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.ini when PHP runs as PHP-FPM, which is the usual Nginx setup. .htaccess is skipped because Nginx does not read it.

Which files does it change?

The .user.ini and .htaccess files in your WordPress folder (and in the site root, if WordPress lives in a subfolder). Only the block between BEGIN DigiNex Limit Booster and END DigiNex Limit Booster is 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_targets and dxlb_minimums filters, 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.

更新日志:

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.
.htaccess is skipped on web servers that do not read it.
Cleans up blocks left by the older "Server Limits Fix" plugin.

DigiNex Limit Booster

标签

下载

详情介绍:

安装:

常见问题:

更新日志: