Forum Moderators: coopster
fopen is not actually disabled, but merely restricted. In particular, when running in safe mode, PHP,
Checks whether the directory in which you are about to operate has the same UID (owner) as the script that is being executed.
Now here's where I get a bit confused, since I have never had to deal with a server running in safe mode, but I think it goes sort of like this. Since the PHP process is usually "owned" by the user "nobody", this must be the user who owns the directory as well. So you would have to set the owner to "nobody" (see the man page for "chown" [hmug.org]). The problem is that a server with safe_mode in effect restricts use of the php chown [php.net] function and, probably has other restrictions in effect that prevent you from beign able to work around it (i.e., you probably don't have the rights to use the chown shell command).
Like I say, take the above with a grain of salt, since I've never actually dealt with it, so I've never paid much attention to it and my knowledge (or lack thereof) is purely theoretical.
Good luck and hopefully someone with more knowledge will chime in.
The first user-contributed note on the manual page has a fetchURL function - you could try that...
Checks whether the directory in which you are about to operate has the same UID (owner) as the script that is being executed
I had once the same problem the answer lies in ownership
Although if you are using fopen as a constructing tool
(I mean once in the process of installing new files and processing some modifications for ex) then ask the admin to open the door for having one shot at it (in my case they did it)
Otherwise It seems that there is no back door
Although I would be interested in knowing how dmorison solution does