Eric Binnion

cranewest

<p>Allows admins to deactivate a user as opposed to deleting a user. Works with web and XML-RPC based authentication.</p>
<p>Once installed and activated, a checkbox appears on the user profile settings page. When checked, the user will not be able to login with the account. If they attempt to login, <code>This user has been deactivated. Please contact the administrator.</code> will be displayed in the login error box.</p>


Deactivate WordPress Users

Allows admins to deactivate a user as opposed to deleting a user. Works with web and XML-RPC based authentication.

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.

Deactivate WordPress Users vs Uninterrupted Backup