{"id":393025,"date":"2026-10-28T19:42:01","date_gmt":"2026-10-28T19:42:01","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/diginex-limit-booster\/"},"modified":"2026-10-28T19:41:24","modified_gmt":"2026-10-28T19:41:24","slug":"diginex-limit-booster","status":"publish","type":"plugin","link":"https:\/\/cl.wordpress.org\/plugins\/diginex-limit-booster\/","author":23577994,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.0","stable_tag":"1.0.0","tested":"7.1.4","requires":"5.8","requires_php":"7.4","requires_plugins":null,"header_name":"DigiNex Limit Booster","header_author":"DigiNex","header_description":"Writes the PHP limits you need (memory, execution time, input time, input vars, upload size) to .user.ini and a safe .htaccess block on request, and verifies the result with a real HTTP self-test.","assets_banners_color":"182443","last_updated":"2026-10-28 19:41:24","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/diginex.gr","rating":0,"author_block_rating":0,"active_installs":0,"downloads":87,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.0":{"tag":"1.0.0","author":"diginex","date":"2026-10-28 19:41:24","revision":3771488}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3771488,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3771488,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3771488,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3771488,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3771488,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[1329,289319,16981,249846,159633],"plugin_category":[],"plugin_contributors":[284432],"plugin_business_model":[],"class_list":["post-393025","plugin","type-plugin","status-publish","hentry","plugin_tags-htaccess","plugin_tags-max-input-vars","plugin_tags-memory-limit","plugin_tags-php-limits","plugin_tags-upload-size","plugin_contributors-diginex","plugin_committers-diginex"],"banners":{"banner":"https:\/\/ps.w.org\/diginex-limit-booster\/assets\/banner-772x250.png?rev=3771488","banner_2x":"https:\/\/ps.w.org\/diginex-limit-booster\/assets\/banner-1544x500.png?rev=3771488","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/diginex-limit-booster\/assets\/icon.svg?rev=3771488","icon":"https:\/\/ps.w.org\/diginex-limit-booster\/assets\/icon.svg?rev=3771488","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>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 <strong>checks that the change really took effect<\/strong>.<\/p>\n\n<p><strong>What it sets<\/strong><\/p>\n\n<ul>\n<li><code>memory_limit<\/code> 256M<\/li>\n<li><code>max_execution_time<\/code> 180<\/li>\n<li><code>max_input_time<\/code> 180<\/li>\n<li><code>max_input_vars<\/code> 3000<\/li>\n<li><code>upload_max_filesize<\/code> 64M<\/li>\n<li><code>post_max_size<\/code> 64M<\/li>\n<\/ul>\n\n<p><strong>How it works<\/strong><\/p>\n\n<ul>\n<li><strong>.user.ini<\/strong> \u2013 writes a managed block for PHP-FPM \/ FastCGI \/ CGI hosts. This is the only way to change <code>max_input_time<\/code> and <code>max_input_vars<\/code>, because PHP reads them before WordPress starts.<\/li>\n<li><strong>.htaccess<\/strong> \u2013 adds a protected <code>php_value<\/code> block for Apache mod_php and LiteSpeed, guarded by <code>IfModule<\/code> so it cannot break other setups. Skipped on Nginx.<\/li>\n<li><strong>Real self-test<\/strong> \u2013 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 <code>.htaccess<\/code> is restored automatically.<\/li>\n<li><strong>Diagnostics<\/strong> \u2013 PHP SAPI, <code>user_ini.filename<\/code>, <code>user_ini.cache_ttl<\/code> and the loaded <code>php.ini<\/code>, plus a ready-made block for your hosting panel's PHP INI editor when the host locks the values.<\/li>\n<li><strong>Clean removal<\/strong> \u2013 only the plugin's own blocks are ever touched, and they are removed when you click \"Remove plugin settings\" or delete the plugin.<\/li>\n<\/ul>\n\n<p>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 <strong>Tools \u2192 DigiNex Limit Booster<\/strong>.<\/p>\n\n<p>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.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>Go to <strong>Tools \u2192 DigiNex Limit Booster<\/strong>.<\/li>\n<li>Click <strong>Apply settings<\/strong> and check the \"HTTP self-test\" row.<\/li>\n<li>If some values stay low, wait for the time shown in <code>user_ini.cache_ttl<\/code> (usually 5 minutes) and click <strong>Run self-test again<\/strong>.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"the%20values%20are%20still%20low%20after%20applying.%20why%3F\"><h3>The values are still low after applying. Why?<\/h3><\/dt>\n<dd><p>Your host locks them (for example with <code>php_admin_value<\/code> in the PHP-FPM pool) or has disabled per-directory INI files. No plugin can override that. Copy the block from <strong>Settings for the hosting panel<\/strong> into your hosting panel's PHP INI editor, or send it to your host.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20nginx%3F\"><h3>Does it work on Nginx?<\/h3><\/dt>\n<dd><p>Yes, through <code>.user.ini<\/code> when PHP runs as PHP-FPM, which is the usual Nginx setup. <code>.htaccess<\/code> is skipped because Nginx does not read it.<\/p><\/dd>\n<dt id=\"which%20files%20does%20it%20change%3F\"><h3>Which files does it change?<\/h3><\/dt>\n<dd><p>The <code>.user.ini<\/code> and <code>.htaccess<\/code> files in your WordPress folder (and in the site root, if WordPress lives in a subfolder). Only the block between <code>BEGIN DigiNex Limit Booster<\/code> and <code>END DigiNex Limit Booster<\/code> is written or removed.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20i%20delete%20the%20plugin%3F\"><h3>What happens when I delete the plugin?<\/h3><\/dt>\n<dd><p>Its blocks are removed from both files and its saved report is deleted. Files that become empty are deleted.<\/p><\/dd>\n<dt id=\"can%20i%20change%20the%20values%3F\"><h3>Can I change the values?<\/h3><\/dt>\n<dd><p>Yes, with the <code>dxlb_targets<\/code> and <code>dxlb_minimums<\/code> filters, for example in a small must-use plugin:<\/p>\n\n<pre><code>add_filter( 'dxlb_targets', function ( $t ) { $t['memory_limit'] = '512M'; return $t; } );\n<\/code><\/pre><\/dd>\n<dt id=\"does%20it%20send%20data%20anywhere%3F\"><h3>Does it send data anywhere?<\/h3><\/dt>\n<dd><p>No. The self-test is a request from your site to your own site.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First wordpress.org release, formerly \"DigiNex Server Limits Fix\".<\/li>\n<li>Settings are applied only when you click \"Apply settings\", never on activation and never at runtime.<\/li>\n<li>File changes use the WordPress filesystem API.<\/li>\n<li>The self-test checks all six limits and can be run again at any time.<\/li>\n<li><code>.htaccess<\/code> is skipped on web servers that do not read it.<\/li>\n<li>Cleans up blocks left by the older \"Server Limits Fix\" plugin.<\/li>\n<\/ul>","raw_excerpt":"Write PHP memory, execution time, input vars and upload limits to .user.ini and .htaccess, then verify the real values with a self-test.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/393025","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=393025"}],"author":[{"embeddable":true,"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/diginex"}],"wp:attachment":[{"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=393025"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=393025"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=393025"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=393025"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=393025"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/cl.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=393025"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}