watson

I’ve found a solution, but it involves hacking WordPress it self.

In my case it worked to change the way WordPress connects to the FTP server. So instead of using passive mode (which is the hardcoded default in WordPress), I now use active mode.

To do this you have to edit wp-admin/includes/class-wp-filesystem-ftpext.php and change line 84 to this:

@ftp_pasv( $this->link, false );

In the future it would be nice to have an FTP WordPress constant called FTP_PASV that you could set to either true or false. This way the hack would survive WordPress upgrades ??

Same problem here – though I got a 404 HTTP error – not a 500 (WordPress 2.7.1). And changing “Insert into post” to “Insert media into post” worked great. Alternatively maybe it would work just changing it to “Insert into post” (Replacing some chars with HTML entities) – haven’t tried.

For people who want to do this the file you want to edit is located here:
wp-admin/includes/media.php

There are several places in this file where you need to edit.

Someone should fix this in a later version of WordPress. Even though it only affects some people, it stupid to put something there that just might break.

I just tried via the zip file upload feature – same issue

The Flash uploader does not work for me either. As far as I can tell it has been the same bug/issue for me in both WordPress 2.5, 2.5.1 and now 2.6.1.

The problem is as follows:

• After selecting which files to upload, the uploader starts an asynchron upload for each file, each with its own progress bar. But the progress bar doesn’t move at all and within half a second I get the same error message for each file: “An error occurred in the upload. Please try again later.”
• If I check the server access logs I see that the request is getting through to the server, but generates a ‘503’ http status code (Service Unavailable): "POST /wp-admin/async-upload.php HTTP/1.1" 503 - "-" "Adobe Flash Player 9"

Some people suggest that I disable mod_security in Apache. But I’m running Apache 2.2 on FreeBSD and as far as I can see no standard module is named mod_security. At least I’m not running it. Here are my compiled in modules:

core.c
  mod_authn_file.c
  mod_authz_host.c
  mod_authz_groupfile.c
  mod_authz_user.c
  mod_auth_basic.c
  mod_deflate.c
  mod_log_config.c
  mod_env.c
  mod_setenvif.c
  mod_proxy.c
  mod_proxy_http.c
  mod_proxy_balancer.c
  mod_ssl.c
  prefork.c
  http_core.c
  mod_mime.c
  mod_cgi.c
  mod_dir.c
  mod_alias.c
  mod_rewrite.c
  mod_so.c

In httpd.conf I’m also loading the following:

LoadModule autoindex_module   libexec/apache22/mod_autoindex.so
LoadModule dav_module         libexec/apache22/mod_dav.so
LoadModule dav_fs_module      libexec/apache22/mod_dav_fs.so
LoadModule php5_module        libexec/apache22/libphp5.so
LoadModule status_module      libexec/apache22/mod_status.so
LoadModule dav_svn_module     libexec/apache22/mod_dav_svn.so
LoadModule authz_svn_module   libexec/apache22/mod_authz_svn.so

this is not codecodethis is code/codethis is not code