Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
litespeed_wiki:php:per-user-php-ini [2019/08/29 20:44]
Jackson Zhang
litespeed_wiki:php:per-user-php-ini [2019/08/29 21:00]
Jackson Zhang [8 Supports MultiPHP INI Editor for cPanel out of the box]
Line 132: Line 132:
   * For native LSWS installs, these variables ($VH_ROOT, $VH_NAME, $VH_USER, etc.) need to be inside of a Virtual Host External App Environment Section, and not inside the general Server External App Environment Section. This is because the variables are expanded on start up, so the VH_* variables cannot be expanded during server level configurations.   * For native LSWS installs, these variables ($VH_ROOT, $VH_NAME, $VH_USER, etc.) need to be inside of a Virtual Host External App Environment Section, and not inside the general Server External App Environment Section. This is because the variables are expanded on start up, so the VH_* variables cannot be expanded during server level configurations.
  
-===== 8 Supports MultiPHP INI Editor ​for cPanel ​out of the box =====+===== 8 Supports ​cPanel ​MultiPHP INI Editor out of the box =====
 When a user login to cPanel and edit his own php settings through [[https://​documentation.cpanel.net/​display/​82Docs/​MultiPHP+INI+Editor+for+cPanel|cPanel MultiPHP INI Editor]] (cPanel >> Home >> Software >> MultiPHP INI Editor), cPanel MultiPHP INI Editor will save changes to three files in /​home/​$USER/​public_html/: ​  ​php.ini file, the user.ini file, and .htaccess file.  When a user login to cPanel and edit his own php settings through [[https://​documentation.cpanel.net/​display/​82Docs/​MultiPHP+INI+Editor+for+cPanel|cPanel MultiPHP INI Editor]] (cPanel >> Home >> Software >> MultiPHP INI Editor), cPanel MultiPHP INI Editor will save changes to three files in /​home/​$USER/​public_html/: ​  ​php.ini file, the user.ini file, and .htaccess file. 
  
Line 209: Line 209:
 For Apache SuPHP, it will use php.ini. For Apache PHP CGI and PHP-fpm, it will use .user.ini. For CloudLinux mod_lsapi for Apache, it will use .htaccess. LiteSpeed will use settings in .htaccess.  ​ For Apache SuPHP, it will use php.ini. For Apache PHP CGI and PHP-fpm, it will use .user.ini. For CloudLinux mod_lsapi for Apache, it will use .htaccess. LiteSpeed will use settings in .htaccess.  ​
  
-LiteSpeed will be compatible with cPanel MultiPHP INI Editor out of box without extra configuration required. ​Howeverif you explicitly want to apply /​home/​$USER/​public_html/​php.ini regardless of the cpanel default multi-files implementation,​ you will need to use ''​PHP_INI_SCAN_DIR''​ to manually set up as instructed earlier in this wiki, but it is not recommended to do so and you are encouraged to just use cPanel MultiPHP INI Editor ways of implementation. ​+LiteSpeed will be compatible with cPanel MultiPHP INI Editor out of box without extra configuration required. ​Please also keep in mind that you can not manually change settings in one file through ssh access and you will need to use cPanel MultiPhP INI Editor GUI to make any changes for your test. 
 + 
 +If in any situation, you explicitly want to apply /​home/​$USER/​public_html/​php.ini regardless of the cpanel default multi-files implementation,​ you will need to use ''​PHP_INI_SCAN_DIR''​ to manually set up as instructed earlier in this wiki, but it is not recommended to do so and you are encouraged to just use cPanel MultiPHP INI Editor ways of implementation. ​
  
 ===== Troubleshoot ===== ===== Troubleshoot =====
  • Admin
  • Last modified: 2020/01/01 15:13
  • by George Wang