Sunday 15 May 2011

Wordpress: Unable to upload file to an existing directory -


CentOS 6
WP 3.5.1

I have a WP site that works fine Was not suddenly allowing files to be uploaded:
- Media Uploader: Unable to create directory is it worth writing by its parent directory server?
- Browser Uploader: Error saving media attachment.

06 folder already exists and I'm uploading without problems. I have encountered this common problem after the installation of WP or after a change in usually a month, but never with any existing folder

I have wp-content, uploads, 2013, 01, 02, has tried to allow 777. .., 06, the establishment of the owner: Apache group: Apache but no way! The reason I have read is that SELinux may be but # getenforce = disable

but the most strange thing is now that I realized that this is the problem in my local host!
OS X 10.6.8 - XMP 1.7.3

In Open: < Pre> chown -r www-data: www-data wp-content / upload chmod -r w + g wp-content / uploads

CentOS is not familiar with taste All can be wrong.

Edit:

With some excerpts from reading around, I think this is an estimate that this is a server problem, so far- As the WordPress framework is not happening with PHP in some OS environments, it seems that some others have had problems creating new 'month' folders in some server setups. WordPress users / groups want to create a new folder under www-data or apache (which also applies the correct procedure nickname for Linux), but it may sometimes fail.

Some more suggestions:

1) In the WordPress admin panel - & gt; Settings - & gt; Media, check that you expect this to be the ' Store Store in this folder ', perhaps it's obviously the ' app / wp-content / uploads ' Also try giving 'pathname'.

2) Look at some old (successfully) uploaded files, and see who owns them. Some people have not informed the owner of ' any ', which would obviously be a problem.

3) Arrange a few more ' arrange your folders in a month and year based folders , obviously this will prevent WordPress from creating new folders based on time. ..

Also, if you find a solution, remember to switch back permissions on 755. 777 Safety can be in danger.

No comments:

Post a Comment