內容簡介
目的
檢測阻礙網站管理員進入 WordPress 管理員介面並停用導致問題的外掛程式的「致命錯誤（Fatal Errors）」。UBP 會報告/通知（通過電子郵件發送）網站管理員，提供一個有效期為 24 小時的安全連結，使網站管理員可透過點擊此連結來停用目標外掛程式！
想追蹤開發狀態和問題追蹤，請在GitHub 儲存庫上追蹤此外掛程式。
機制
此外掛程式的機制是將自己始終設定為 WordPress 外掛程式系統要執行的第一個外掛程式！然後，此外掛程式只需待機，直到所有其他腳本的執行終止為止！ UBP 的角色是在腳本終止時扮演的。然後它檢查腳本是否以錯誤終止。如果腳本以錯誤終止，UBP 就會向管理員發送電子郵件，包含一個備份連結和一個安全鍵，UBP 會根據此鍵授權連結所有者停用目標外掛程式。
優點
不需要透過 FTP 存取以強制停用 WordPress 外掛程式。您可隨時使用此外掛程式用郵件中發送的連結來停用目標外掛程式。
只載入最少量的程式相依性，僅在監聽錯誤時才會載入程式。
注意事項
每當您啟用或停用外掛程式，UBP 都會將自己放在 WordPress 活躍的外掛程式隊列中的第一個位置。
當網站已被錯誤阻擋時，此外掛程式無法自行安裝。
在網站完全運作良好的狀態下必須先安裝 UBP，然後它將幫助您備份網站，以防任何新的外掛程式出現錯誤。
它無法處理您的 WordPress 網站中的所有錯誤，但它總是可以讓您能夠在安裝任何阻止您進入管理後台的外掛程式後，讓您再次啟用網站。
它沒有管理使用者介面，因此不可設定，但下一個版本將有此功能。
不論檢測到何種「致命錯誤」，都會向管理員發送電子郵件，而且無論此錯誤是否阻擋網站，它都會報告可能在未阻擋您自行停用外掛程式的次要請求中發生的致命錯誤。
概念驗證
我仍有許多有用的想法和功能可添加到外掛程式，但需要使用者的評論來證明它的確有幫助，並且確實需要改進。
外掛標籤
開發者團隊
原文外掛簡介
Purpose
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!
For development state and issue tracking follow the Plugin on GitHub Respository
Mechanism
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.
Advantages
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.
Load minimum codes/scripts that required only to get involved (listen to errors). Load code required to functional only when error detcted.
Notes
Whenever you active or deactive a Plugin, UBP will always put itself as the first Plugin in WordPress active Plugins queue.
The Plugin won’t install itself while the site is already blocked by the error.
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.
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.
It has no admin user interface and therefor not configurable, however next versions will do.
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.
Proof Of Concept
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.
