Howard Miller

You need to get to the bottom of the error 500. Unfortunately, that just means "It's broken". Make sure Debugging is on full and go back to your hosts.

Ok - I don't know anything about your hosting but I assume there's some way to work out how much disk space you have left?

Specifically, files are stored at wherever $CFG->dataroot is pointing to in Moodle's config.php. If Moodle is unable to write to that, weird things will happen. Anyway, it was just a thought.

Unless they change the requirements matrix as well

Now paranoia is setting in

Paul - he's not talking about the version number (the date stamp one). He's talking about 'Version 4.4.7+' or whatever

"Moodle releases new code about every week - the .#'s you see on the end of a version ... like n.n.8"

I'm not sure if that's what you meant but it's not true. The weekly build (I'm reluctant to call it a release) just has a + on the end. Every so often ("usually every 8 weeks"), these are rolled up into a release where the number on the end increases.