Unable to create directory

The answer is yes. I have ftp access and have changed the directory permissions to 777.

Which directory? I’m guessing you changed wp-content to 777?

Hi doodlebee,

Yes I changed wp-content, and uploads (which I had to create manually after adding it to the directory name in options) and any other folder that seemed relevant!

I’ve read your answer to this post and I’m thinking that just having everything in /uploads will suit me, so I’ve switched off the year/month option, as I don’t want to have to manually do this every month.

However I’ve now run into the same? problem as jcwords…

The uploaded file could not be moved to /usr/local/psa/home/vhosts/domain.name/httpdocs/personal/journal/wp-content/uploads.
Warning: Cannot modify header information – headers already sent by (output started at /usr/local/psa/home/vhosts/domain.name/httpdocs/personal/journal/wp-admin/admin-functions.php:1879) in /usr/local/psa/home/vhosts/domain.name/httpdocs/personal/journal/wp-includes/functions.php on line 1219

Not sure what’s going on there?

“headers already sent” usually (not always) means that the file (the file in question seems to be “wp-admin/admin-functions.php” and “wp-includes/functions.php”) has whitespace before or after the code begins or ends.

Like I said, that’s not *always* the issue, but many times it is.

You should be able to keep the monthly archived stuff – you just need the “uploads” folder to be 777. (definitely *NOT* your wp-content directory – change that back ASAP). When you get it to work, you should change it back. it may not be working because of this new error you’re seeing.

You may also want to check your server error logs to see what kind of info you can glean from that – it may have other errors or warnings to tell you about. You can also search (either the forums or google) “headers already sent wp-admin/admin-functions.php:1879” and see if anything comes up.

I had already changed the wp-content file back, but thanks for the reminder ??

I don’t really mind about the monthly archived stuff, as long as this works without having to fiddle with things.

Anyway, not sure why but things seem to be working now… with /wp-content at 755 and /uploads at 777 I *may* try switching monthly archives back on out of curiosity at some point, but now that it’s working I think I’ll leave it alone!

Thanks for your help doodlebee ??

>>/wp-content at 755 and /uploads at 777<<

That is as it should be. All is well with the Force ??

You can try putting the monthly back in (or just go yearly – I upload images so infrequently that I use yearly) – it shoudl owrk now that you’ve accessed the uploads folder.

Once you’ve uploaded an image with your admin panel, you need to change the permissions on your uploads folder *back* to 755 – WP only needs to access it once. If you leave it at 777, you’re opening up a bitty security hole.

Oh yeah, and mark this thread as resolved, too ??

When I change the uploads folder back to 755 – even after a successful upload – I get problems again!

Haven’t yet tried putting archive folders back on – will report back when I have.

No, back to where I started…
/wp-content = 755
/uploads = 777
…but when the “Organize my uploads into month- and year-based folders” option is selected I get:

Unable to create directory /usr/local/psa/home/vhosts/domain.name/httpdocs/personal/journal/wp-content/uploads/2007/03. Is its parent directory writable by the server?

Fortunately I’m happy with everything going into uploads, otherwise I’d be pretty unhappy!

I’m having the same problem but running in a Windows environment, and therefore cannot use the CHMOD command. Can anyone suggest how I can change the folder permissions?
cheers, Warren

Hi all,

please check with your provider “first” that safe_mode = off for PHP for your domain!!!

You can check this with phpinfo in a php-file.

Most trouble comes from that.

see you
Gordian

Re: pepe, many responsible providers do not allow safe mode to be off. In fact, programs should be written for safe mode so that in shared environments there is less chance of data leakage.

I’m having the same problem as above, in version 2.0-15 of WordPress. I’ve determined that WordPress creates folders as the apache user, but then can’t take advantage of the chmod 777 because the owner is still apache. In order for the permissions to work, I must delete the folder and recreate it with the same permissions so that the owner is now my hosting account (this is a shared environment, so I don’t have access to apache)

I was able to fix this by changing the owner of the uploads directory to www-ddata (though I don’t know if this is te best approach):
sudo chown -hR www-data uploads

Thanks doodlebee, this post really helped me out…and fast.

Ciao.