500 Fixed by Patching Grav

What is your assessment of this solution?

A 500 error is thrown when cache/compiled/ is not writable.

Instead of a 500 error, which presents without explanation, the problem could be added to the issues list, making the easier to address.
You can see it running here (image attached)

This is the php that detects the issue, when inserted at line 393 in vendor/rockettheme/toolbox/File/src/File.php

$dirParent = substr($dir,0, strrpos($dir,’/’,-2)+1);
$fileowner=posix_getpwuid(fileowner ($dirParent));
if (trim($fileowner[‘name’])!== trim($phpaccount)) :
//add to issues list

A better fix might be to include cache/compiled/ in the download instead of creating it with php when Grav first runs…

Is this helpful? Grav

exec’ing server binaries (which potentially don’t exists, like on Windows) is a dangerous solution, not to mention potentially slow. I don’t think this is the best solution to the problem. However, if you did come up with a better solution, a PullRequest on the toolbox project would be appreciated: https://github.com/rockettheme/toolbox

Regarding including this folder in the package, the problem is the cache/ folder is often cleared out completely including all sub folders (including cache/compiled/) so the folder does not to be recreated when missing. The fundamental problem is that your files including cache/ folder are owned by a different user than your webserver/php process. So this is where the conflict happens. We have provided some steps to address this in the Permissions Troubleshooting Docs.