Upload Media – Select Files button not working in WP 3.3

Have you read https://www.ads-software.com/support/topic/troubleshooting-wordpress-33-master-list yet and tried the ‘before you post…’ suggestions?

I’ve performed ALL of the tweaks in the master list and suggestions I’ve found dotted about the web, and I’ve completely re?nstalled a completely fresh database and copy of 3.3.1. It does not help. Given that

1) there are no plug-ins running;

2) all plug-in resets have been tried;

3) all caches in both FF and Safari have been cleared; and

4) Twenty-eleven is the theme,

I can’t see any other way to reduce this problem further or remove non-WP elements (because there are none in such a clean installation). A completely fresh installation should work, but does not. ??

I’ve been running other WP blogs for many, many years, but I’ve never seen a problem like this with a completely fresh installation. It would seem from the web that I’m not alone.

Does the browser uploader work?

Going to Media and clicking the Add New button, or choosing Add New from the Admin menu Media tab, brings up the drag-and-drop uploader, which seems to work fine.

Curious that this works but that the uploader does not work when one wants to add an image to a page. :-/

FWIW, Safari refuses to even show the clickable image (showing only the “Upload/Insert” clickable text), whereas FF shows the little camera/music clickable image.

99% of the problems on the backend are caused by javascript conflicts. That is why there is no one solution. For example, the drag and drop box has never shown up for me with FF, IE, Chrome, Safari. I didn’t even try to debug it. If one of the uploaders works then use it and don’t worry, be happy.

You can go here to check your version of java, https://javatester.org/index.htm and if you want to try upgrading the jquery in wp-includes/jquery/jquery.js go here https://docs.jquery.com/Downloading_jQuery#Current_Release

For some it seems like shocking the system with a new jquery or by loading google libraries does the trick – try this https://www.ads-software.com/extend/plugins/use-google-libraries/

> If one of the uploaders works then use it

Uploading is not the problem. The problem is the insertion of a reference to media in the library.

FWIW, the installed version of java is up to date.

As for jquery, if it’s included in the WP download, it should work with the rest of a clean WP installation. FWIW, WP 3.3.1 does not have a wp-includes/jquery/ folder. I presume you mean wp-includes/js/jquery/jquery.js. WP 3.3.1 includes jquery version 1.7.1, which is only a very minor rev. short of the current 1.7.2, and 1.7.1 comes with a recommendation to stay with 1.7.1 in some circumstances….

I tried both jQuery 1.7.2 AND the Google libraries routes. No change to the greyed-out page with its Add Media ‘pop-up’ that is both white and empty.

This problem would seem to be much more serious than jogging WP with jQuery or resetting browser caches.

??

Do you have FireBug? You can check the scripts as they run and maybe find where it is hanging.

Have you tried IE or a different computer? I know it is a pain but the debug protocol is a matter of elimination. Can you post a url?

Hmmm. Now this is interesting:

Your suggestion to use another computer prompted me to use Safari on the Leopard Server itself. It worked and brought up the Add Media pop-up properly (I’ve not tested further, i.e. whether it both displays AND works properly).

The implication is that the issue is with the browser computers, not the servers, even if I did determine that Apple’s most recent update to php is 5.2.15, not the minor tweak up to 5.2.4 that the WP 3.3.1 requirements say it should have. It is evident that the php version is not the issue, because both versions of Safari were contacting the same installation of WP.

As to what could be up with Safari on my desktop, I can’t imagine, because it’s the most recent version. Also, many people have reported the same problem with the Add Media button with Exploder on Windows and FF.

I have the most recent FF, and it behaves as Safari does on my desktop, implying a problem with some support code used by BOTH Safari and FF on my desktop iMac. I believe the latter to be up to date wrt to Java, etc., so I can’t imagine why an up-to-date Snow Leopard iMac would both behave like some versions of IE on some versions of Windows, and not behave better than Safari on a Leopard Server machine.

Curiouser and curiouser, said Alice, not speaking very good English.