Upon updating this plugin (which requires deactivation then reactivation automatically during the update process), OR if you install this plugin THEN ACTIVATE IT fresh from the repository using wp-admin/plugin-install.php, it results in wp-admin becoming inaccessible with an Error 500 for any page that you try to load in wp-admin. The only remedy I have found is to rename the wp-content/plugins directory to something new then reinstall your plugins again (or delete yarpp from the plugins directory which will force-deactivate it).

I've enabled wp_debug with absolutely no success, including forcing WP to write errors to a log file. I've also been completely unable to obtain any PHP errors coming from any domain using this plugin, so unfortunately I can't even point anyone in a better direction than to examine the activation process of this plugin very thoroughly so I may continue to use one of the best WP plugins I have ever found. Please, and thank you!

I'm really sorry to hear this! and definitely want to get this resolved. Unfortunately I haven't run into this in my testing and without seeing the errors I'd have a hard time knowing where to start. :( Could you post what version of WP you're on, as well as other plugins that are active? What kind of hosting or server is this? Do you have some nonstandard setup, like some caching proxy or something?

Yup i have the same issue - it happens entirely with the new version of YARPP and either of the latest two versions of WP (I have upgraded to 3.5.1 from 3.5 today (so far at least only on development servers) and both show the problem).

It is not a conflict with any other plugins as on one of my installations I have deactivated everything except for YARPP before upgrading wp then YARRP and the problem still exists.

For now I guess I am left with the need to deactivate YARPP before updating it on all of our websites and leave it deactivated until this is resolved (or not update it in the first place).

p.s. if you do get in to the same state as I now have two of my dev sites as Jerome suggests an easy fix is to drop the YARPP folder in the WP plugins directory into a sub folder so it's not picked up by WP

Note: you will need to reinstall it when a stable version is released, back date to a previous version or be provided with a file/set of files that fix the problem (assuming it is not related to db changes) before you can get it back.