I’m sorry that you had a poor experience. Let’s see if we can get to the bottom of it.
This plugin only has one line of real code. I’d suggest that your developer have a look at the main plugin file (available at http://plugins.svn.wordpress.org/disable-xml-rpc/trunk/disable-xml-rpc.php) and try adding that line of code to your theme’s functions.php file.
If that doesn’t break the Edit Media page, then it’s unlikely that the plugin itself was causing the problem – that line of code, with the exception of the readme file – is the only thing in the plugin.
Please let me know if that works in the functions file but still doesn’t work when you remove it from functions and enable the plugin. I’d be happy to discuss the problem further, as that definitely shouldn’t happen.
Thread Starter
Momo
(@yangman)
It works when I insert the code into functions.php without activating the plugin. When I remove the code and activate the plugin, the problem returns and now with a new twist, I get this message on top,
“The plugin generated 2 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”
Thread Starter
Momo
(@yangman)
I think I’ve found the bug on the plugin.
After ?> I noticed there are 2 blank lines. I simply remove the lines by backspacing, reactivate the plugin and everything is working fine. 🙂
I suppose by removing the ?> altogether will work too, but I didn’t try. I can activate the plugin now and working….HAPPY!
Thank you very much for your thorough testing. That did not occur when I tested the most recent update to the plugin (which was just a README update).
I will remove those lines in the official version when I’m back at my development system today and I will mark this as resolved at that point.
Thank you again!
Phil
I’ve just updated the plugin to version 1.0.1 to remove the extra lines at the end of the file. I’ve tested on a few installations and everything seems to be fine. Please give it a spin and let me know how it performs for you.
Phil
Thread Starter
Momo
(@yangman)
Updated to v1.0.1 and works like a charm.
Thanks for the update 🙂
FYI – best practice is actually to just not even have the closing ?> in php files for exactly this reason.
It’s even mentioned in the handbook: https://make.wordpress.org/core/handbook/best-practices/coding-standards/php/#remove-trailing-spaces