I'm not sure if this is a new behavior or not, and it makes sense, but I noticed that when I enter custom php.ini configuration directives for a website, in the ISPConfig interface, the directives are written to the site's PHP-FPM pool configuration file with the php_admin_ prefix. For example, if I enter the following in the site's "Custom php.ini settings" field Code: display_errors=On the following results in /etc/php5/fpm/pool.d/web1.conf: Code: php_admin_flag[display_errors] = On Does this occur because the "admin" account created the website in question? Or is that irrelevant here? If so, what is the preferred method for specifying custom php.ini directives such that they are not prepended with php_admin_? I ask because I need to allow site-owners/end-users to override certain php.ini defaults at run-time (for example, via the error_reporting() function). Thanks for any help. ISPConfig 188.8.131.52p1 with nginx-1.1.19 and PHP-FPM.