I am running into this everywhere. It seems like this editor ACL is a bit "static" as to what it chooses to include in user.ini, and if multiple domains hit the same root, doesnt work in a per-domain manner anyways if they are all in the same root (ie, multisite). So far its wrecked up an install/requirements on every account on our server in some way or another. Is there a way to shut off the use of user.ini without hacking around and which will persist through updates? We are using FPM if that matters.
EDIT: it seems like it could be related to this: MultiPHP INI Editor file name .user.ini instead of php.ini
The reason im asking is that last week all some Newrelic schemas got nuked. There is no reason newrelic stuff cant be set in user.ini, htaccess, or even at php runtime, right? Also things like max_input_nesting_level or max_file_uploads dont work anymore which is a massive issue for ecom apps that had been stable for years.
EDIT: it seems like it could be related to this: MultiPHP INI Editor file name .user.ini instead of php.ini
The reason im asking is that last week all some Newrelic schemas got nuked. There is no reason newrelic stuff cant be set in user.ini, htaccess, or even at php runtime, right? Also things like max_input_nesting_level or max_file_uploads dont work anymore which is a massive issue for ecom apps that had been stable for years.
Last edited: