Any ideas? The code seems fine, as it works a treat when I run it locally (on WAMPServer), but as soon as I try to run it on the server I get this horrid error. I'm guessing some weird permission problem that I have no idea how to get around.

Just guessing. I would like to give read, write and execute permissons to everybody (user, group and others) to images/profile where the image has to be moved. Give 777 permissions first, then, if it works, try to raise the security level.

*facepalm*...for the love of...okay, so there's me thinking that some subdirectories inherited permissions. Works an absolute treat. '757' turned out to be the magic number there.

Cheers for pointing out the obvious. I have my little moments.

On my servers I usually just run apache as apache:apache and chown my public html directories to user:apache, chmod it to g+rxs and everything works fine.

Correct, that's also what I do, although the +s permissions could be sometimes dangerous.
However, if we are talking about public servers like astahost, the user can only use ftp clients, so he connot directly access the +s option. And the users which have ssh access here are probably jailed in a rsh sheel, i'm event not sure chmod is allowed in a restricted shell command line.

great guys
Problem With Move_uploaded_file()

I had this problem and 757 sure solved it. But do you know anyways to handle security with this kind of a breach

-reply by ulta coder