WordPress.org

1. dknippling
   Member
   Posted 2 years ago #

   I installed WordPress at my site using my host's download program.

   I logged into the Admin panel using Firefox 3.5.3 and WordPress 2.8.4, went to Media | Add New. I arrived at the Flash Uploader and clicked Select Files, which opened a browser-type window.

   I selected a JPEG about 36K. The browser-type window disappeared.
   A bar stating "crunching" appears for a brief moment in the Add New area. It disappears, leaving image information but no images or thumbnails. When I enter the URL for the image in a new browser window, the message 403 Forbidden appears, with "Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request."

   The same thing happens when I try the Browser uploader.

   I have checked my permissions for the folders all the way down to the file level; the permissions are set to 755 for public_html, blog (the blog subdomain and the main folder I used for the WordPress install),
   and wp-content folders. The permission is set to 777 for the uploads
   folder. The year/month structure folders are set to 777. I have pictures saved both in the uploads and 2009/10 folders. I have used the Settings | Miscellaneous folder to turn off the year/month structure. The store uploads in the folder option is set to wp-content/uploads (default).

   The upload folder, when I view it from my host, appears to contain three images files per image, or three different sizes. The permissions for the images are all set to 666. I am able to view the images via my host.

   I have deactivated all plugins and widgets; I am using the default theme. I have tried all the steps in the sticky.

   Any advice?

2. Shane G
   Member
   Posted 2 years ago #

   Hi,

   Check with these options:

   - Assign 766 recursive permissions to wp-content directory. If you do not have an access of SSH then you can contact hosting service provider to grant the permissions.

   - Disable all the plugins and enable it one by one to find out the culprit.

   - Add this code in htaccess:

   <IfModule mod_security.c>
   SecFilterEngine Off
   SecFilterScanPOST Off
   </IfModule>

   Thanks,

   Shane G.

3. dknippling
   Member
   Posted 2 years ago #

   Hi Shane G,

   I don't know how to do a recursive permission change, so I manually set the path wp-content/uploads to 766.

   I turned on the month/date setting in the Settings | Permalinks and Settings | Miscellaneous folders. The month/date folders were set to 777 and gave me error messages when I tried to set to 766, so I left them.

   Does that suffice for the permissions?

   I have no plugins installed, and no widgets active.

   I added the code in htaccess (in the public_html folder, couldn't find any other). After that didn't work (same error as below), I added code to the htaccess file per the following message:

   "If your .htaccess file were writable, we could do this automatically, but it isn’t so these are the mod_rewrite rules you should have in your .htaccess file. Click in the field and press CTRL + a to select all.

   <IfModule mod_rewrite.c>
   RewriteEngine On
   RewriteBase /
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteRule . /index.php [L]
   </IfModule>"

   --Note: The htaccess file is set for permission 666 at the moment; I played with giving it 777 and 766 permissions, but it did not changes the result.

   Result:

   Unable to create directory /home/deannakn/public_html/blog/wp-content/uploads/2009/10. Is its parent directory writable by the server?

   Which at least is a new error message :)

   --Note: I played with setting the permissions of wp-content/uploads folders to 777. I now no longer have the error message "unable to create directory..." but am back to the original error of not seeing images.

4. dknippling
   Member
   Posted 2 years ago #

   Okay - issue resolved. The protection had been set at the server host site to prevent anyone from hotlinking to images, including yours truly. The host server site kindly corrected the issue for me, so I am unable to provide a blow-by-blow description.

   She confirmed this was not a permissions issue.

Topic Closed

This topic has been closed to new replies.