2.5 image upload

Adding the ‘SetEnvIfNoCase Request_URI ^/wp-admin/async-upload.php$ MODSEC_ENABLE=Off’ line to .htaccess DOES WORK if PERMALINKS is turned OFF, otherwise I′m back to square one. This is really annoying, since I use wp more as a cms than a blog.

Anyhow: 2.5 is really awesome and I think that it is the next natural step from 2.3.3. When posting to multiple sites the media uploader will save me huge amounts of time – If it worked, that is ;).

update:
I put the .htaccess file with “SetEnvIfNoCase Request_URI ^/wp-admin/async-upload.php$ MODSEC_ENABLE=Off” in /wp-admin instead of / and tried the media uploader, and to my big surprise, it worked even with permalinks turned on! This is indeed a happy moment. ??

1) OS your WP 2.5 install is on
FreeBSD 5.3

2) Version and type of webserver
MySQL 5.0.45
Apache, not sure what v. and don’t have the energy or time to find out ??

3) Version of php
4.4.8

4) Do you have an .htaccess file at wp-admin/.htaccess
Yes

5) Do you have .htaccess elsewhere
No

6) Are you password protecting the entire wp-admin directory, or does your host or cpanel have this turned on?
no

I’ve tried all the above things. With the new line in the .htaccess i’ve got rid of the http error, but i’m still stuck on the blanc pop-up. I know that all the images are uploaded, but he doesn’t remember. I have to clean the upload folder by hand. I only have this problem on my old wordpress blog, the blogs that are started i think from version 1.5 (updated then from B2). The newer blogs (i think started with version 2.x) don’t have the problem anymore after doing all the mentioned thricks

Changing the .ht file to

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

worked out right for me, AFTER I changed the permalinks settings to “day and name”. Using custom permalinks seem to activate and write the .htaccess file and suddenly it stood there in my root WP dir. The first upload stopped when I wanted click the submit button. So I got half an upload. The files where there on my server including thumbs.

Then I realised that custom permalinks somehow were needed to create the .htaccess file, but using custom permalinks also modify your .htaccess file. So, change your permalinks and you’ll see an .htaccess file in your root WP folder and if your satisfied with the new structure of your permalinks, leave them for what they are, replace your already existing .htaccess file with this:

# BEGIN WordPress
<IfModule mod_rewrite.c>
SecFilterEngine Off
SecFilterScanPOST Off
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

and last but not least set the file permission of the .htaccess file to 444 so that WordPress can’t rewrite it.

I just merged the code wordPress writes when it uploads, with the mod_security settings. That’s all. Hey and I ain’t no coder at all. Don’t be dissapointed with 2.5 because it works like a charm.

replace your already existing .htaccess file with this:

Wrong, wrong, wrong, wrong, wrong.

Never, ever, modify anything inside the #BEGIN WordPress and #END WordPress lines.

Firstly, you should have put that mod_security stuff into a new .htaccess file in the wp-admin folder. You only need to disable it for the admin stuff.

Secondly, you can add anything you want to the main .htaccess file, as long as you put it outside those begin and end lines. This would have worked just swell, for example:

<IfModule mod_security.c>
SecFilterEngine Off
SecFilterScanPOST Off
</IfModule>
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

WordPress will only mess with text inside those begin and end lines, everything else it will leave alone.

You don’t have to put everything in an .htaccess into one block, and I still do not understand why everybody thinks that you do…

@otto 42: The “#begin wordpress” thing is something that I din’t made up, I saw it appear in the .ht file. As i mentioned before, I am a kinda nerd if it comes to coding. But I figured it out how to debug it for my own sake. Something went wrong overhere. xcuzez moi. Just tried to make some sense what code worked for me. After all the # sign souldn’t make a difference in my experience, just a remark.
You cleaned up the code. I also doubded about the kinda ‘PHP insertions’. As you have figure it out, I aint no coder. I figure out my things my way. Thanks for the correction anyway. I’ll correct the lines in the upper suggested code and i’ll see what happen.

#That is PHP remarks. Again I ain’t into coding but i’ll figure it out. Thanks again.

I like to know from the people who have trouble with the image upload where there wordpressblog comes from. I’ve installed several wordpressblog in the last years. I have to old blogs I think I started them at version 1.5, and upgraded when needed. This are the one having problems. I have a blog started at 2.3.2, just upgraded and it works without any problem, even without the .htaccess and the fixes for IE. There are all on the same kind of server

A wild guess, but it works.
In one of the old blogs with problems I did the following:
I made an exportfile in the wp-admin
I made (for backup) an backup of the database with Export in phpmyadmin.
Then I deleted in phpmyadmin all the wordpress tables.
I didn’t change anything in the wordpressfiles on the server.
When going back to the blog it automatically installs and makes a new database.
All i had to do is in the wp-admin import the old posts, choose the right theme, setup my widgets and activate my plugins. And it works perfectly now. With me the problem is the old database (originally B2, changed to WP 1.5 and upgraded since)

@katooje:
I did the same. But after adding:

setlocale(LC_ALL, ‘de_DE’);

in wp_congig.php it broke again. I need to set ‘setlocale’ because some of my plugins require it to properly translate dates to german.

I have this problem only on one of my blogs. All posted fixes aren’t working for me. Commenting out ‘setlocale’ fixes everything.

I didn’t work for the last blog I upgraded. THe blog is working fine, I imported all the post etc, but uploading images is still a problem. I comes to ‘crunching’ and it stayes there. It’s so frustrating. One is working in FF and not in IE, arghhhh I just want to blog and add pictures ??

@otto 42: The “#begin wordpress” thing is something that I din’t made up, I saw it appear in the .ht file.

Yeah, I know. The begin and end stuff are comments that WordPress puts into the file and looks for when it needs to modify the file. WordPress will modify only stuff inside the begin and end lines, which is why you shouldn’t mess with that, because WordPress will simply overwrite your changes next time it needs to modify that file.

But it won’t modify anything outside those lines. That’s why you want your lines outside that section.

This solution from Otto worked for me. I didn’t have to change permissions or anything.

I already read about every fix here. But uploading just doesn’t work for me on one of my blogs. I tried everything. Really frustrating.