Not compatible with WordPress 3.5's new media manager

Thank you, Elisabeth!

I got a couple of emails that EMR was no longer working with 3.5 and I just implemented your changes to the plugin and it works great. I’ll submit a new version to www.remarpro.com momentarily.

I had to change line 57 (65 now actually) to:
` if ( !is_null($current_screen) && $current_screen->base == ‘post’ && $current_screen->post_type == ‘attachment’ ) { $on_media_edit_screen = true; }

I got errors on response to the “query-attachments” ajax call when editing a gallery.

I’ve also added a ! is_null( $current_screen ) condition on line 65, since get_current_screen() returns null in the Add Media and Set Featured Image dialogs.

One thing I’m not clear on is whether you should be able to replace media from within a post or page, or if the functionality should be restricted to the Edit Media page. Either way, this workaround does the trick for my purposes.

Thanks to M?ns and everyone else for your help in improving this plugin!

The issue that persists in version 2.8.1:

With EMR active, if I try to add Media to a post, the Media Library tab (that’s supposed to show existing images in my media library to use) always comes up blank.

Disabling EMR lets me see my entire Media Library there, as expected.

The fix that Joolee suggests 2 posts above seems to correct my issue.

This is very strange, I am not seeing this at all. I went ahead and implemented Joolee’s change anyway and submitted 2.8.2 so please update and try it out and let me know!

Hi
great plugin
2.8.2 just installed with WP 3.5.1, and the problem persist.
Any fix?

getting this error message:

Invalid argument supplied for foreach() in /home/myuser/public_html/myfolder/wp-content/plugins/enable-media-replace/upload.php on line 55

Cannot modify header information - headers already sent by (output started at /home/myuser/public_html/myfolder/wp-content/plugins/enable-media-replace/upload.php:55) in /home/frente/public_html/semanario/wp-includes/pluggable.php on line 876

Versión 3.5.1

Arnold, the only way I can see that you would get that error message is when WP fails to get metadata for the requested file. This would mean that there is no metadata stored in the database for that file.

I could make it fail more gracefully (and I might) but that wouldn’t really help you since my plugin needs the thumbnail sizes stored in that metadata to replace the resized images.

Question 1: When you receive that error, is the original file still replaced?

Question 2: Is it an image you are trying to replace?

Installed the Plugin
Requires: 2.8 or higher
Compatible up to: 3.5.1
Last Updated: 2013-1-18

IN: WP 3.5.1
Using WOO-Theme Bueno 1.7.4 / Framework 5.4.1

Replaced one pic as a test (jpg for jpg of simul. size).
Went ok but all I got now is a place-holder with no image…

WordPress Programmers; “We Real Need This Option”

bikeamtn: What happened in your file system – was the file replaced? Is it completely missing?

Hi M?ns; The details are: looking at the page as a public view, if I do a right-click ‘Show Image’ it will then load. Refreash the page and again just place-holder is shown. From the admin side of things, the image replace looks like it worked although in the library the thumbnail is the old image but if I select ‘Edit’ will show the new one in the edit screen. I tried flipping the image just so I could SAVE it hoping it would then show correctly but nope and still just shows place-holder.
I’ve now deactivated plugin and replaced the manual way (delete image in library, upload new with same name and assigned to the page or post and used the original URL-Link for the new image). That worked. That way it goes right in the same place without a page layout change. Its the long way around but thats what it is. Don’t know about others but my issue may be with using WooTheme.

That sounds more like there is a problem with the local cache in your browser preventing you from seeing the new thumbnail after replacing the image.

No; kept clearing cache, refreashing and checked using IE and Chrome. Also doesn’t explain why WP-admin Library was having a problem.