A common trick I use to gain insight into what certain arrays/object contain is I use a custom write_log function that essentially just prints out info to the php error log in a very clean way. The code can be found here. Usually on my local env, I can do this and see everything. However, in DevKinsta, the string length of the Error Message seems to be getting limited by something. Setting in php.ini? I’m not sure. It will just randomly terminate the string and end with a line that reads “while reading response header from upstream” and some other info about the server:, request:, client: etc.
How can I adjust the settings to give me the full output?
Also, this is the first time I’ve ever seen errors put in the log that start with: "FastCGI sent in stderr: "PHP message:
Indeed you could use php.ini to increase the length of the output of the error with log_errors_max_len though I’m not sure if that’s the exact issue occurring here. There are instructions here on how to edit this. A bit of a tease here but if you’re able to wait just a little bit longer, we’re going to make it much easier to update the php.ini configurations (no exact date, but soon). What’s the error shown in the logs there?
So, I tried this with non success. No value I entered into sites.ini ended up making a difference. I am still getting the same length regardless of what value I enter. I tried like 4-5 different values. And yes, I did restart docker and DevKinsta after each change to the .ini file.
@robruiz We’ll give this a test further and update you. DevKinsta does support the default debug and it’s a main feature of DevKinsta should there should be no issues at all here with that. I’ll let you know!