Anyone using Wordpress can answer this if they like,
I have been using Wordpress for a long time. At the moment I am on one version lower than the new update which is 3.2.
I have for some time been able to upload Images via the dashboard 's Image gallery. Now it won't since I upgraded the last time. It will only allow from host cpanel..
The report is http error. It goes through the motions of crunching etc but no further.
Has anyone else had such a problem?
:(
I think this the flash uploader right? When you want to select multiple images vs. just one?
I think it might be a server issue as another customer on your server reported it awhile back.
I'll take a look...
Can you see if this is fixed now?
I'm going to move this thread to the Support board and change the subject slightly to "WordPress Media Upload Problem" in case people want to find it in the future.
===============
Update: I tested a WordPress install on this server and it's working now. Thanks!
-Jason
Quote from: dania on July 10, 2011, 03:49:57 PM
Anyone using Wordpress can answer this if they like,
I have been using Wordpress for a long time. At the moment I am on one version lower than the new update which is 3.2.
I have for some time been able to upload Images via the dashboard 's Image gallery. Now it won't since I upgraded the last time. It will only allow from host cpanel..
The report is http error. It goes through the motions of crunching etc but no further.
Has anyone else had such a problem?
:(
Is this a re-occurrence of the 'bad behaviour' module bug?
It is a compatibility issue with the bad behaviour module and other plugins, especially WYSIWYG editors. WordPress has fixed for this specific issue, but it is hard to track down if you don't know what you are looking for.
Here are some other solutions for older versions:
http://wordpress.org/support/topic/25-imagemedia-uploader-problems (http://wordpress.org/support/topic/25-imagemedia-uploader-problems)
It was a mod security configuration issue at the server level.
The first time someone reported it we went through lots of troubleshooting since that error is in tons of wordpress error posts all over the Internet and they all seem to have different fixes, none of which worked in this case. Once I saw it again a few times it leaned towards a serverwide issue.