Large images will not upload, a plugin warns that PHP is outdated, an import stops halfway: most of these problems come from PHP settings rather than broken code. ISPmanager lets you choose a PHP version per site and adjust the key limits.
Choosing the PHP version
Open Sites (or WWW domains), edit your domain and look at the PHP block, which lists the versions installed on the server. New sites should use a current, supported release for speed and security fixes. For an older site, first check which versions your CMS, theme and plugins support. Back up files and database before switching, then test the home page, admin area, contact form and checkout; rolling back takes seconds in the same form. Upgrading one major version at a time is safer than jumping several at once, because deprecation warnings give you a chance to fix code before it breaks.
Handler modes and why they matter
PHP can run as an Apache module, as CGI/FastCGI, or through PHP-FPM, usually alongside Nginx. Which modes exist depends on the server, and the panel default is normally the right choice. The mode decides where custom settings can live: php_value lines in .htaccess only work with the Apache module and cause a 500 error otherwise, while CGI and PHP-FPM setups can usually read a .user.ini file in the site root.
Settings you will change most often
| Setting | Controls |
|---|---|
upload_max_filesize | maximum size of one uploaded file |
post_max_size | size of the whole form request; keep it larger |
memory_limit | memory available to one script |
max_execution_time | how many seconds a script may run |
max_input_vars | number of form fields, important for big menus |
date.timezone | Asia/Tashkent for Uzbekistan |
display_errors | keep off on a live site |
Which values you may change, and how high, depends on your hosting plan. Set limits slightly above real needs rather than as high as possible. A huge memory_limit, for instance, lets one buggy script consume far more resources and slow down every site on your account, while a value just above what the heaviest page needs keeps problems contained and easier to spot.
Example: an online store import
An appliance store in Fergana importing a 40 MB CSV catalogue on misol.uz hits "file exceeds the allowed size", and smaller files time out after a minute. Raising upload_max_filesize, post_max_size and max_execution_time fixes both. If the panel does not expose a setting and the site runs under CGI or PHP-FPM, try:
; .user.ini (site root)
upload_max_filesize = 64M
post_max_size = 64M
max_execution_time = 300
memory_limit = 256M
date.timezone = Asia/Tashkent
The file is re-read after a server-defined cache period, usually a few minutes, and values above your plan's limits are ignored.
Verifying the change
Create a temporary file with a random name such as info-7f3k.php:
<?php
phpinfo();
Open it in the browser and read the "Local Value" column for each setting, then delete the file because it reveals server details. Over SSH, php -v works too, but the command-line PHP version may differ from the one serving your site.
If the site breaks after a change
Revert the last change first: switch back to the previous version or remove the php_value lines. Then check the site error log in ISPmanager, which usually names the file and line. A common cause is an old plugin calling a function removed in newer PHP, so update or replace it. If you are unsure what your plan allows, ask sayt.uz support through a ticket.