Ren Ventura

<p>This plugin adds a button to the top of <code>wp-admin/plugins.php</code>. When clicked, every plugin (except for this one) will be deactivated. However, all active plugins are remembered.</p>
<p>After the plugins are deactivated, a button will appear to reactivate them. This will reactivate only the plugins that were active before – plugins that were inactive will not be enabled.</p>
<p>This is helpful for users who need to troubleshoot plugin conflicts by deactivating plugins in bulk. Without this plugin, you’d have to reactivate plugins based on memory. If there are a lot of plugins running on the site, with numerous plugins that are disabled, this can be difficult to do without first creating a list of what was active and inactive.</p>
<p>With the Plugins Deactivator plugin, you can easily disable all plugins at once. With one more click, you can restore your plugins to where they were before.</p>


Plugins Deactivator

Disables all WordPress plugins with one click. Remembers which plugins were active so they can also be re-activated with one click.

Code Machine

<h4>Purpose</h4>
<p>Detect WordPress Plugins ‘Fatal Errors’ that might block/prevent site admins from accessing WordPress admin interface in order to deactivate the Plugin that caused the issue! UBP then report/notify (sedning email) site admin with a secure link that valid for 24 hours from which site admin can deactivate the target Plugin by simply clicking the link!</p>
<p>For development state and issue tracking follow the Plugin on <a href="https://github.com/xpointer/ubp" rel="nofollow ugc">GitHub Respository</a></p>
<h4>Mechanism</h4>
<p>The mechanism of the Plugin is to always put itself as the first Plugin to be executed by WordPress Plugins system! The Plugin then just stay away and never get itself involved until the execution of all the other scripts is then terminated! UBP Plugin role is comes when the script is terminated. It then check if the script is terminated with error. If the script if terminated with error UBP send admin mail with backup link that has a secure key by which UBP give the link owner the permission to disable the target Plugin.</p>
<h4>Advantages</h4>
<ul>
<li>There is no need to access throught FTP to force WordPress deactivate the Plugin. You can always use this Plugin to deactivate the target Plugin only with the link sent with the mail.</li>
<li>Load minimum codes/scripts that required only to get involved (listen to errors). Load code required to functional only when error detcted.</li>
</ul>
<h4>Notes</h4>
<ul>
<li>Whenever you active or deactive a Plugin, UBP will always put itself as the first Plugin in WordPress active Plugins queue.</li>
<li>The Plugin won’t install itself while the site is already blocked by the error.</li>
<li>UBP must be installed first while the site is fully functional and then it’ll help you backing up your site if any newly Plugin produced an error.</li>
<li>It Won’t help you on all type of errors you’ve in your WordPress site however it can always give you the chance to get your site functional again after installing any Plugin that prevent you from accessing your backend.</li>
<li>It has no admin user interface and therefor not configurable, however next versions will do.</li>
<li>Send admin mail whatever ‘fatal errors’ is detected and it doesn’t matter if this error blocked your site or not. It’ll also report fatal errors that might happened in a secondary request that doesn’t block you from deacivating the Plugin yourself.</li>
</ul>
<h4>Proof Of Concept</h4>
<p>I still have many useful ideas and feature to add to the Plugin however the Plugin need users reviews to proof that its really helping and its really need to be improved.</p>


Uninterrupted Backup

Detect fatal errors that might be produced by the installed active Plugins, provide secure backdoor for deactivating the target Plugin.

Plugins Deactivator vs Uninterrupted Backup