“People won't change until the pain of not changing is greater than the pain changing brings.” -Just B. Jordan
OK; I've conceded that I'm never going to get to the bottom of my 500 errors when clearing cache on a shared server, as described in excruciating detail
here. So I've bit the bullet, and subscribed to a VPS service, where I have control over what gets logged, and what doesn't. The downside, of course, is that I also have to manage the server. Well; I cut my teeth on a PDP-11 running BSD 4.3 in the Seventies, how hard can this be?
It's hard. But, I'm learning. I've got LAMP up and running, and I've ported my site from the shared server to a test environment on my VPS, and it's working. Not surprisingly, when I ported my board to a test environment there, I can clear the cache without triggering 500 errors. Which only substantiates the conjecture that the shared server was resource constrained. Now, my resources are fixed, and can be fully monitored.
But...
All the uploaded files on my shared server had 644 permissions - and, so they do after porting. However, any newly uploaded files have 666 permissions (which, includes world-writeable). For a time, I thought this had something to do with my server configuration, but it doesn't. I've placed
this sample code from W3 Schools directly within my phpBB root, and when I use it to upload a file, the permissions are 644. What explains this difference? Is there something configurable with phpBB, that would set the permissions for new uploads to match that of legacy uploads?