I just found and solved a very peculiar issue. I installed a copy of Winter CMS (based on Laravel) but immediately started getting an error about a directory needing to be present and writable.
Long story short, Winter CMS does some fancy checking of paths against PHP’s open_basedir setting, which I discovered is used here. And normally this would not be a problem – unless the value for that setting is malformed.
Using dd() and ini_get(), I discovered that my open_basedir string value ends in a null byte (“\x00”), and this is what’s throwing off the code. I dug into the CMS library, wrapped “ini_get(‘open_basedir’)” with a call to rtrim(), and magically the issue was gone.
However, this is obviously not a long-term solution because the next time the library code is updated, my change will go away.
So I am just asking if the code that sets the open_basedir value for each account can be updated to NOT add a null byte at the end of the string?