Well things can change withoud doing anything. There is no way I can put images to my posts anymore. Which browser I take, it all ends up in a white empty popup screen. It makes me grrrrrr
Well things can change withoud doing anything. There is no way I can put images to my posts anymore. Which browser I take, it all ends up in a white empty popup screen. It makes me grrrrrr
This thread is all over the place, so I'm not sure where to start. I tried the mod_secure off thing (I think), but someone said it doesn't work with rewrites on.
I know that isn't my problem though. My issue is the following lines in my .htaccess, which is in the root folder:
RewriteCond %{HTTP_HOST} !^www\.kristarella\.com$ [NC]
RewriteCond %{REQUEST_URI} !^/robots.txt$
RewriteRule ^.*$ http://www.kristarella.com%{REQUEST_URI} [L,R=301]
It's basically there to make sure whatever is typed into the address bar goes to the right place.
If I delete these lines of code then I can upload images. Is this a WP bug? Am I redirecting the flash uploader to somewhere it shouldn't be?
For me the fix was the following:
In your .htaccess file near the bottom make sure that you remove 'AddType text/x-server-parsed-html .htm .html' and on it's place add 'AddHandler server-parsed .html .htm'.
Don't know if this will help any...
I have the same problem. Made an effort do everything, that advised here, made alteration in a file, but constantly get the same error: "The uploaded file could not be moved to /home/xxxxxxxx/public_html/wp-content/uploads."
I haven't been able to get any of these fixes to work for me, although curiously enough, I can take any photo that the uploader chokes on and resize it to a smaller image using an editing software, and it will upload successfully.
My 6.0 megapixel camera creates files of 850 to 1,200 KB. If I bring them down to the 500's, they'll upload sucessfully.
Obviously, this is a work-around and not a fix. It seems to point to the problem, anyway.
Umm, no EotS, I think that's as good a fix as you're going to get for the flash uploader. I don't think it's capable of "crunching" 1MB files. I've had that happen to me before, I don't think it has anything to do with the HTTP errors that people in this thread have gotten. Sorry :(
Do you really want to upload files that big?
Anyone know anything about the problem with the htaccess code I posted before? I'm sure it must have something to do with the way WP is directing upload requests, but I no idea about that sort of stuff.
I don't think it's capable of "crunching" 1MB files. I've had that happen to me before, I don't think it has anything to do with the HTTP errors that people in this thread have gotten. Sorry :(
It gets to the end of the crunching and then shows an http error. It uploaded the file, but did not create a medium-size version. So when I post it in a thread, it shows up full-size and then you have to go through tedium to size it down for the post.
Do you really want to upload files that big?
Of course. That is the size the camera produces, and they're shared with family. Do I really want to have to downsize everything before I move it to the page? Especially when I'm encouraging my wife to write to our blog and put pictures up, and she's not going to do it if she has to edit and resize every picture first.
EotS,
I can see this is a bit of an annoying issue. This thread (http://wordpress.org/support/topic/167276?replies=21#post-728189) suggests it's the RAM/CPU load on your server's side that limits the crunching of large images, which I agree with. There's some contention though, so it might be that an htaccess fix will work for you (http://www.hongkiat.com/blog/wordpress-25-image-upload-error-wordpress-fix/).
I guess it's not fun to resize everything before uploading, but there's programs and scripts that can do batch resizing, so you don't have to do it individually. I was mainly thinking that it's going to be using a lot more MB on your server and will be more expensive and it's a lot for others to have to download (but I guess if they're crunched the later is n/a).
Hopefully that htaccess will fix it for you though.
I've read Otto's post and followed all those instructions... I upgraded exactly according to the directions, added the .htaccess to wp-admin, etc. I don't get an http error; the interface just never uploads the file or shows me a dialog to accept it. This is a screen shot of what I get. Has anyone seen this problem?
@astrumporta So your screen just stays like that? For how long? That's what it should look like while it's uploading. The blue line on the left indicates that it's uploading and then when it's done it goes away. How big is the image you're uploading?
Hey, thanks for replying kristarella. The image is only 28 kb. I've left the screen up for several minutes and nothing happens. After I close the window manually, the file is definitely not in the library. I've tried this from 2 different Macs and with other images...
I had a similar problem with my blog. Was fine until I upgraded to 2.5.
If you have exhausted all other avenues, I would contact your host. My host (Hostgator) was blocking the upload of images for security. I had to tell them the location of all of my blogs so that they could remove the security feature. This worked perfectly.
When I was getting the problem I was just getting "http error", but I know some people got "crunching" instead.
It seems that the server was logging this message: mod_security: Access denied with code 403. Pattern match "^Shockwave Flash" at HEADER("USER-AGENT") [id "***MY ID"][rev "1"] [msg "SpamBot UA"] [severity "CRITICAL"] [hostname "***MY-DOMAIN***"] [uri "/testing/blog/wp-admin/async-upload.php"]
Hope this helps you guys. I spent hours trying sugegsted fixes. I never would have guessed that it was a security issue with my host. After contacting them it was fixed within the hour.
At first they argued that it was 3rd party software, but I told them that I had a test blog and I also had blogs on 2 servers and it was the same on all of them. They referred me to their higher level support and they fixed it within an hour.
Let me know the outcome dave@isnigh.com
I have the Firefox Firebug thing - and as I kept getting a 'bad HTML'error I figured the problem could have been in the settings:
Site Admin > Settings > Writing-settings and unchecked “WordPress should correct invalidly nested XHTML automatically”
It worked for a while. i could also load through IE for a while. Maybe it is a problem with the size of the image file (small ones work better) and it could be a host thing, or a cache size or whatever. I really haven't a clue, groping in the dark. I seem to get the problem sporadically but more often at times that this connection ADSL connection slows down.
The code is: / send html to the post editor
2function send_to_editor(h) {
3 var win = window.opener ? window.opener : window.dialogArguments;
4 if ( !win )
5 win = top;
6 tinyMCE = win.tinyMCE;
7 if ( typeof tinyMCE != ‘undefined’ && ( ed = tinyMCE.getInstanceById(’content’) ) && !ed.isHidden() ) {
8 tinyMCE.selectedInstance.getWin().focus();
9 tinyMCE.execCommand(’mceInsertContent’, false, h);
10 } else
11 win.edInsertContent(win.edCanvas, h);
then
win.edInsertContent is not a function
With 2.5 of course. Whatever - are we all getting different problems? I've no idea about all this, really.
Q
http://nineteenhundredandyesterday.com/?p=103
worked for me for now. I may also contact my host but they break things so until I move to a better one I will work with single image at a time uploads.
It seems there are many ways the new flash-based image uploader can fail. I'm fairly drowning in data here, so can anyone point me to a discussion/thread that specifically addresses:
WP 2.5 image upload failing because of password-protected .htaccess file
I know this is my problem because if I turn off password protection in my .htaccess file, things work again, and because I have other WP 2.5 blogs running on the same account that are working just fine (w/out password protection.)
I haven't found any solution here so far that works for my problem -- has anyone else?
I agree with cantonbecker.
I got the http error only with password-protected .htaccess file.
But I got the error only when using Ubuntu/Firefox (or Epiphany or Opera)/Flash player 9.
I have no error with Windows XP/IE7 (or IE6 or Firefox)/Flash player 9.
Is there still no fix that makes an end to all the image upload problems? I have one site which is working fine in firefox, but IE6 is giving problems with sendig images to the post. I can go to media library, click show on one of the images and when i click Send to post, it just send the image that was last added, not the image that was selected. This problem is nog accuring in firefox. In IE7 I just don't know which image it will send to the post, because it's stuck on the white popupwindow after sending the image to the post.
It would be so nice if everything was working in all of the browsers.
At this moment I don't know where to look voor THE fix, there are so many threads about this subject that I'm really longing for 1 place with the answer.
Turned out the problem I was having was caused by a Javascript security precaution -- the update frame was trying to access the main frame, which was coming from a different domain/protocol.
The protocol was different because I've been trying to make sure my WordPress login is secure, using SSL. It appears that this might be "done properly" in 2.6 (about time! - but thanks), removing the necessity for me to bodge around it, so that problem should be gone then.
The domain was different because we are lazy and like typing just "blog" in our browsers' location bars, allowing our DNS resolver to complete the name from our default search domains. This meant that the original page was coming from something like "blog" while the upload frame was from "blog.example.com" (coming from the settings for "wordpress location").
To fix this, just make sure that "UseCanonicalName On" is present in the apache config for your virtual host.
--
The "NoFlashUpload" plugin appears to have almost exactly zero effect on this system at the moment, by the way. Not sure why, and since the normal upload is now working I'll probably not bother to work it out.
--
The FlexibleUpload plugin also won't work, as I have symlinked wp-content/* to somewhere outside of /usr, as it's a bad idea to start editing files inside /usr any more than you absolutely have to on a system with a half-decent package manager. There are other reasons too, but that one will do for now.
If every other plugin I've tried so far can manage without "require ../../../../whatever", I'm not about to change for one that can't.
Hi,
Friends i don't know how to upload my image.Can you give me information regarding that.
aylen
orkut
Here is a solution to the password protected install/admin directory problem. I am using it in 2.6.1. I have added this to my .htaccess file to allow the flash uploader to function. It reverses the require [user] directive.
# allow flash uploader to work in a password protected directory
<Files async-upload.php>
Order Deny,Allow
Allow from all
Satisfy any
</Files>
Hi folks,
I'm new to WordPress, and have actually the 2.6.2 version.
I had the same problem as yours and tried everything from this post.
Finally I tried to move the upload directory from /wp-content/uploads to /uploads, and it solves my problem!
I created the uploads folder manually with my ftp client, and set it to 777. In settings->misc., I set the upload directory name to "uploads" (no slash anywhere)
Note that I get an error if I check the checkbox "organize my files in year and month folders" (or something like that, I have the french WP version!)
I'm not sure if I broke something by moving the upload folder or if it's more dangerous for security, what do you think?
Hope this helps!
Sebastien
Hi
My picture uploader in wordpress is not uploading pictures. What might be the problem?
i get only box whit a red x in ther left corner
*NOTE: If you don't want to read through all of this babble, skip down to the bottom to see what worked for me. ;-)*
****
I hate to bring this one up again, but I figured it was a central post that everyone refers back to, so it would be a good spot for someone like me who had exhausted all their possible options on this one.
I had poured through almost every post here regarding this issue, and had tried every suggestion, checking back daily for weeks. Every plug in, .htaccess workaround, permission set, hack, you name it...nothing worked.
Today, I was setting up a new blog on the same host package, the same domain, the same DB server, and I decided to see if it too had the same upload error issue as I was having on my main photoblog site. Right out of the box, I uploaded a 1024x768 500k image...no problem at all. The best I was able to currently upload on my photoblog (that was having the HTTP upload issue) was about 800x600p and around 200k. I decided to spend some time going through all of my plugins, half at a time to see if I could narrow it down to a plugin on a 50/50 basis. As soon as I deactivated 1/2 of them...the issue was gone. Seeing that, I reactivated 1/2 of the previously deactivated ones and then tried again. The issue came back first shot with the same file. From there, I just kept playing the 50/50 game until I found the plugin that was causing it for me. I toggled it back and forth, and sure enough, it was the one that was causing me the headaches.
WP-SpamFree 1.9.6.6
Now, granted, I did not go back through all of the settings for WP-SpamFree yet, so there *may* be a way to get it to play nice. I was more concerned about being able to use WP to upload the photo sizes that I was able to prior to 2.5 or 2.6...whichever started tossing me the errors. I will report back if I find a setting or workaround for still using the plugin without the issue.
So if you are reading this, and had gone through all of the steps on the first 4 pages without any luck, check what I've mentioned above.
Good luck!
This is an excellent troubleshoot method - it reminds me of the early days of Mac OS 9! LOL! Well done.
More importantly, for me anyway, was that it worked. ;-)
This topic has been closed to new replies.