- Some of them point to some memory/time limits imposed by the hosting, killing scripts exceeding them. You could try to move some modules/blocks out form their place to "alleviate" a bit Moodle installation requeriments and, if it success, move them back later...
- Others point to some miss-configured .htaccess files + php running in cgi mode. Examine if you have some sort of .htaccess file and, if possible, rename it (to disable it) and try again.
- And some of them point to the possibility of switching from PHP4 to PHP5, by creating one simple .htaccess file in the root moodle folder:
To switch from php4 to php 5 you can
i) change all .php files to suffix .php5 which is worse than placing a php.ini in every folder
or ii) add the line, AddType x-mapp-php5 .php, to a .htaccess in your root directory. The good news is it applies to all sub-directories
This seems to avoid server 500 errors, unlike a .htaccess with the line, php_flag register_globals off
Such a shame that 1and1 tech support couldn't have told me of this!
I don't know if (ii) will help but you can try it easily.
Ciao
That third .htaccess tip worked a treat, install went fine and now php is reported as version 5.1.4. Will report back if any of the other errors I got before present themselves, but hopefully that is the answer. Should Moodle be expecting php version 5 or is that just the way 1&1 configures itself? Looking back I see that our cheap testbed uses version 5 point something and it worked there.
