I've noticed a few reports of problems with safe mode.
Mostly we seem to have sympathy - but no solutions. So I will attempt to define the problem and suggest solutions. (though I am not an expert in php/mySQL)
First - here is my description of the problem....
Part 1
I get the error message at the top of the admin screen:
Warning: SAFE MODE Restriction in effect. The script whose uid is 732 is not allowed to access /tmp owned by uid 0 in /usr/local/www/gospelcom/docs/rww/moodle/admin/index.php on line 16
Warning: It appears your server does not support sessions (session.save_path = '/tmp')
Now I suspect that this red comment isa faulty assumption by admin/index.php the folder tmp/ is not writable in safe mode, but sessions seem to be working.
Part 2
Every new folder that is created by moodle has the "wrong" permissions - so the only solution I've found is to rename it, download the contents, then make a new one with owner me - then add group write permission, then upload the files.
I wonder if a way round this (because I guess safe mode servers will be common) is to make a whole load of blank folders (with .htaccess files in all) from the tar file - these will have the user permission so the group write permission can be added. (I keep my files in the moodle tree as ./uploads ). This may prove to be irrelevant or just plain bad sense. Anyone ideas on this?
Another solution to safe mode could always be the use of blob fields instead of files & folders - can they hold files? (not sure I'm a mySQL beginner).
OR
Use one big folder with the correct permissions and do virtual subfolders using database tables.
It is a shame that those of us hosting on safemode servers cannot use moodle as it is right now. (I will also talk with my hosting org)