On this page
On LogicWeb shared hosting, MultiPHP INI Editor is the reliable way to change PHP settings. A php.ini file dropped in public_html is usually ignored by LiteSpeed lsphp. A .user.ini file can act as a per-directory override for some SAPIs, while a system-wide php.ini belongs on a VPS you control, not on shared hosting without root.
When upload_max_filesize is raised without a matching post_max_size, large uploads still fail. Set both values together. Prefer the panel over files in the document root so changes stick across deploys and account moves.
php -i | grep -E ‘memory_limit|upload_max|Loaded Configuration’That command shows which configuration file PHP loaded and which limits won. If three places set memory_limit differently, this output ends the guesswork. Paste it in a ticket when something still looks wrong after you save MultiPHP INI.
Why a php.ini in public_html usually fails
On this stack, LiteSpeed does not treat a php.ini in the document root as the main config for your site. MultiPHP INI does. Git deploys that commit a php.ini into a theme will keep losing that fight. Keep runtime limits in the panel, not in the repo, unless you run a VPS where you own the PHP stack and reload it yourself.
OPcache revalidate tweaks are not a substitute for page caching when you want WordPress to feel faster. Leave display_errors off on production and log errors instead so visitors never see stack traces.
What MultiPHP INI controls on shared hosting
Open MultiPHP INI Editor in cPanel, pick the domain, and edit the directives you need. Common ones include memory_limit, upload_max_filesize, post_max_size, and max_execution_time. For most admin screens, sixty seconds is enough; large backups sometimes need one hundred twenty. Setting max_execution_time to zero is rarely a good idea on shared hosting.
AutoSSL and Let’s Encrypt continue to work the same way after you change PHP limits. WP Toolkit remains available on WordPress accounts and does not replace MultiPHP INI for core PHP directives.
When .user.ini still matters
Some PHP SAPIs read .user.ini for a subset of settings in a directory tree. That can help for a single app folder, and it can also confuse you when the panel and the file disagree. If a setting never applies, check MultiPHP INI first, then confirm with the grep above. On a VPS with php-fpm you may edit a different pool config and reload the service; that path does not apply to shared accounts without root.
Nameservers stay ns1.logicweb.com and ns2.logicweb.com while you tune PHP. Hosting and VPS keep the same price at renewal, with a thirty-day money-back window if the plan is not the right fit.
Tagged
Was this article helpful?
Be the first to rate this article.
