I suppose there is value to saying to provider X, I don’t have these issues with the same base install with provider Y. Perhaps they would dig a little deeper... perhaps not.
One thing that does come to mind in response to this, if the error_log was successfully created when executing your intentionally-invalid PHP file, is to check whether the error_log file is being created under the /install/ folder when the installation fails.shortmort37 wrote: ↑Wed May 12, 2021 5:47 pm I have E_ALL set in php.ini, and I can force an error message into error_log by calling a php script that loads a nonexistent module. But nothing gets entered by running the install script - nor, in the Apache log for my shared server account.
Say... I know how to throw an error in PHP that gets logged in error_log - invoke a nonexistent module, e.g.,
Code: Select all
asd();