So I’ve spent the last hour trying to find out why I was getting a 500 error, nothing in the logs or anything.
Turns out I had managed to delete the cache directory.
So, I’m suggesting Kirby throws an error if the cache directory, or any other directory is missing, instead of a 500 error.
Hm, HTTP 500 is strange, that shouldn’t happen. I will look into this.
I just checked this. Kirby already throws an error, but if you don’t have debugging enabled, it won’t be visible and PHP will just die with HTTP 500.
Kirby 2.4 will have an improved debugging view that will display the error with debugging enabled or at least an error page without details in case it is not enabled. I consider this fixed with that new debugging view.