Differences

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

Link to this comparison view

Both sides previous revision Previous revision
litespeed_wiki:php:per-user-php-ini [2019/08/29 21:02]
Jackson Zhang
litespeed_wiki:php:per-user-php-ini [2019/08/30 16:02] (current)
Lisa Clarke [cPanel MultiPHP INI Editor Support] Copyedited
Line 6: Line 6:
  
 =====  Supports cPanel MultiPHP INI Editor out of the box ===== =====  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 logs in to cPanel and edits PHP settings through ​cPanel'​s ​[[https://​documentation.cpanel.net/​display/​82Docs/​MultiPHP+INI+Editor+for+cPanel|MultiPHP INI Editor]] (**cPanel > Home > Software > MultiPHP INI Editor**), the editor ​will save changes to three files in ''​/​home/​$USER/​public_html/​''​the ''​php.ini'' ​file, the ''​user.ini'' ​file, and the ''​.htaccess'' ​file. 
  
 For example: For example:
Line 78: Line 78:
   zlib.output_compression = Off   zlib.output_compression = Off
  
-Why the same changes are being saved to three different files at the same time? It is because ​of different ​php handler ​will use different files to apply the settings. ​User may change handler ​sometimes ​and three files keeping the same changes ​will make sure cPanel MultiPHP INI Editor settings will apply regardless of handler change.+You probably noticed that the same changes are being saved to three different files at the same time. This is because different ​PHP handlers ​will use different files to apply the settings. ​A user may change ​the handler ​at some point, ​and the three files will be udated accordingly to ensure the cPanel MultiPHP INI Editor settings will continue to apply.
  
-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.  ​+Apache SuPHP uses php.ini. ​
  
-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.+Apache PHP CGI and PHP-fpm ​use .user.ini
  
-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+CloudLinux mod_lsapi for Apache uses .htaccess.  
 + 
 +LiteSpeed uses .htaccess. ​  
 + 
 +LiteSpeed is compatible with cPanel MultiPHP INI Editor out of the box with no extra configuration required. Please also keep in mind that you cannot manually change settings ​in any of the files through SSH. You must use cPanel MultiPhP INI Editor GUI to make any changes for your test. 
 + 
 +If at any time you explicitly want to apply ''​/​home/​$USER/​public_html/​php.ini'', ​regardless of the cPanel ​default multi-file implementation,​ you will need to use ''​PHP_INI_SCAN_DIR''​ to manually set it up as instructed ​later in this wiki. Howeverthis is not recommendedand you are encouraged to just use cPanel MultiPHP INI Editor.
  
 ===== 1. Define PHPRC or PHP_INI_SCAN_DIR for a domain on cPanel server ===== ===== 1. Define PHPRC or PHP_INI_SCAN_DIR for a domain on cPanel server =====
  • Admin
  • Last modified: 2019/08/30 16:02
  • by Lisa Clarke