• Over 2 servers, 3 browsers, and 3 virgin-clean installs of WP 3.4.1 we have yet to get the media uploader to work at all. There seem to be hundreds of complaints spread around the net regarding this issue – and no definitive solution offered anywhere. Very frustrating problem. Wasting untold hours on this with zero result gotten from all tried and suggested solutions.

    Sadly, have not found any response from the factory on this continuing problem; please point me to one if any credible one exists!

    Two questions for the forum if I could:

    1. Has anyone gotten the v3.4.1 media uploader to work ‘out of the box’ for a fresh, no plug-ins WP installation?

    2. Are there ANY alternatives to adding a central media content control option to WP? Don’t really care what it is – as long as it works.

    Thank you!

Viewing 15 replies - 1 through 15 (of 22 total)
  • 5 browsers, about 6 servers, 12 WP 3.4.1 sites and not a problem with the Media uploader on any one of them. ??

    1. Yes.

    2. Not that I know of.

    Have you tried:

    – deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

    – switching to the Twenty Eleven theme to rule out any theme-specific problems.

    resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

    – re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress.

    Thread Starter FrustratedFella

    (@frustratedfella)

    Grrr…. (smile). Wave your magic wand my way Esmi.

    We cannot get WP 3.4.1 media uploader to work at all after trying all those solutions. Did 3 fresh, blank installs of WP, tried it with default themes and custom ones, never had any plug-in activated beyond the default install, and in each re-install we have started from scratch.

    Regarding resetting the plug-ins folder, aside from deleting it and installing from scratch, and verifying that the “active_plugins” option is set at “a:0:{}”, is there something else to try?

    Nothing about our installs of v3.4.1 has been done any differently than previous versions; of which we have at least 5 other active WP installs – of previous versions. There are 3 sites happily running v3.3.x on the original target server.

    Oddly, when on the ‘Upload New Media’ screen, the “Try the browser uploader instead” URL shows as only “<domain-path-omitted>/wp-admin/media-new.php#” — just an undefined placeholder hash on the same page.

    when on the ‘Upload New Media’ screen, the “Try the browser uploader instead” URL shows as only “<domain-path-omitted>/wp-admin/media-new.php#” — just an undefined placeholder hash on the same page.

    Now that sounds like some sort of server issue. Are the 3.3 installs on the same physical server as this one?

    Can you access the Flash uploader option? If so, what happens if you use that?

    What about the drag’n’drop option when using Firefox or Opera ( drag’n’drop doesn’t work properly in IE as far as I recall)?

    Thread Starter FrustratedFella

    (@frustratedfella)

    Yes, there are three v3.3.x installs on the same server, each working just fine. Two were moved to that server and one was installed fresh many moons ago.

    No, clicking on the flash uploader “Select files” button results in nothing at all. Dead link, same as the ‘browser upload’ option.

    Have tried 3 versions of IE, and the current Chrome release. All exact same results. Running Flash 11.3.300.265 (current) and Java 1.70_05 version.

    Did you download a fresh copy of WP for each of the 3 installs?

    Thread Starter FrustratedFella

    (@frustratedfella)

    For 2 of the new installs yes from fresh downloads. For one I simply re-unarchived the same source file.

    In future I’d suggest a fresh download every time – especially in cases like this. Can I tempt you to try another download and install?

    Thread Starter FrustratedFella

    (@frustratedfella)

    Without a tangible clue towards any sort of fix – and that’s spread around hundreds of complaints on the same exact issue I found through Google – I am less than excited about going through all the same motions again. Isn’t there a saying about “Insanity is repeating the exact same actions and expecting a different result”? (laughing)

    I appreciate your help esmi but I will have to tell the client that v3.4.1 is simply broke and we will offer a v3.3.3 install instead. Given the volume of hits on this exact problem I know I am not alone in this massive frustration.

    Humour me, please? If you still have a problem after this, I’ll try to get some eyes on the problem.

    What I can say for certain is that this is specific to your installs and/or servers and it’s an issue I’ve not come across before. If you still get upload failures with that weird url/path being output in the upload window, please copy & paste the full details here (modify any paths if they are sensitive). We just might be able to come up with a definitive reason for this.

    Thread Starter FrustratedFella

    (@frustratedfella)

    I get a perverse pleasure from humoring moderators so I am game (laughing).

    But aside from what I’ve already posted, what else can I offer? The URL generated for the ‘browser upload’ is as posted before and very lacking in any clue or indicator. And since the uploader generates no apparent error…

    Happy to provide an offlist phpinfo dump, or a private login for a credible WP pro, etc. Also happy to turn on extended/debug logging or whatever might offer a pointer to the core issue. I am root on my servers and can access anything needed for proper diagnosis.

    I’ve asked if anyone else has seen this or has a suggestion. In the meantime (and it’s a long shot), try adding define('CONCATENATE_SCRIPTS', false ); to the bottom of your wp-config.php file (just before the require_once line).

    Thread Starter FrustratedFella

    (@frustratedfella)

    I genuflect in your general direction esmi – it worked.

    Now we get a coupon-looking ‘Drop files here’ box and everything seems to work just fine.

    Exactly what does the ‘CONCATENATE_SCRIPTS’ variable do? Is there something/anything which could have been changed about the server config to remedy this problem?

    And most importantly – will this “non-standard change” have any other ramifications in other areas of WP or its plug-ins?

    Thank you esmi!

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Edit: And Jan laughs out loud. Very loudly! ?? Glad that Esmi’s solution worked!

    – – – – – –

    Mind if I walk through the logs with you here? I want to see where the break is, if any, on your web server and rule that out if possible.

    If you have access to your web server logs (and some patience), can you try something a little odd? I just want to see if the media uploaded loads and what you get in your logs if it does or doesn’t.

    Clear your browser’s cache, log into one installation and visit the media upload URL directly like so.

    https://your-wordpress-url-here/wp-admin/media-upload.php

    On my test server I get this line in the access log.

    xxx.xxx.xxx.xxx - - [13/Jul/2012:19:50:43 -0400] "GET /wp-admin/media-upload.php HTTP/1.1" 200 3127 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11"

    I’m using Chrome on Windows. If that loads, you should get the media uploader filling up the whole page. That’s normal.

    Now in Windows, drag a jpeg image to the Drop files here.

    When I do that with a small file, my log shows this.

    xxx.xxx.xxx.xxx - - [13/Jul/2012:19:54:30 -0400] "POST /wp-admin/async-upload.php HTTP/1.1" 200 33 "https://test-server-url/wp-admin/media-upload.php" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11"
    xxx.xxx.xxx.xxx - - [13/Jul/2012:19:54:31 -0400] "POST /wp-admin/async-upload.php HTTP/1.1" 200 1887 "https://test-server-url/wp-admin/media-upload.php" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11"
    xxx.xxx.xxx.xxx - - [13/Jul/2012:19:54:31 -0400] "GET /wp-content/uploads/2012/07/gravatar2-150x150.jpg HTTP/1.1" 200 9432 "https://test-server-url/wp-admin/media-upload.php" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11"

    When I save the file I uploaded, my access logs get these lines.

    xxx.xxx.xxx.xxx - - [13/Jul/2012:19:57:13 -0400] "POST /wp-admin/media-upload.php?type=image&tab=type&post_id=0 HTTP/1.1" 200 3091 "https://test-server-url/wp-admin/media-upload.php" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11"
    xxx.xxx.xxx.xxx - - [13/Jul/2012:19:57:13 -0400] "GET /wp-admin/load-scripts.php?c=0&load=jquery,utils,plupload,plupload-html5,plupload-flash,plupload-silverlight,plupload-html4,plupload-handlers,json2,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,admin-gallery&ver=3.4.1 HTTP/1.1" 200 193364 "https://test-server-url/wp-admin/media-upload.php?type=image&tab=type&post_id=0" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.11 (KHTML, like Gecko) Chrome/20.0.1132.57 Safari/536.11"

    And the file is saved to my media library.

    Can you try that? May be we can find an error on your server.

    it worked

    Woohoo! ??

    So it would seem that your server has an issue with javascript files when they’re strung together (ie “concatenated” in an effort to boost site performance) as opposed to being served separately. What does surprise me is that you didn’t mention seeing any issues in the Admin area generally. Normally this kind of server problem causes the Admin layout to break down.

    Hello All.

    Just done a fresh install of 3.4.1 with GoDaddy (don’t know if thats frowned upon in these here parts…)

    I have several other blogs running on 3.3 and lower, and uploading media is fine.

    However on this new blog with 3.4.1. I can NOT get the image to upload without a “broken image” link.

    Even through filezilla the image goes into my folder fine, but is not a legit link.

    Even when I “edit” the image, it recognises it, but has not workable / viewable thumbnail.

    Ok, well, hope someone can help?

    Rob

Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘Media uploader still broken in v3.4.1’ is closed to new replies.