[WordPress] 外掛分享: Rudwexa – AutoFixer

首頁外掛目錄 › Rudwexa – AutoFixer
WordPress 外掛 Rudwexa – AutoFixer 的封面圖片
全新外掛
安裝啟用
★★★★★
5/5 分(1 則評價)
7 天前
最後更新
問題解決
WordPress 7.0+ PHP 7.4+ v1.0.0 上架:2026-08-22

內容簡介

Rudwexa - AutoFixer 是一款強大的 WordPress 外掛,專門用於檢查網站的各種潛在問題,包括 PHP 錯誤、外掛衝突和資料庫問題。它提供簡單易懂的解釋和自動修復選項,幫助使用者輕鬆維護網站健康。

【主要功能】
• 檢查 PHP 錯誤與過時函數使用
• 偵測外掛衝突與 JavaScript 錯誤
• 修復資料庫問題與缺失檔案
• 提供安全的自動修復選項
• 連接第三方 AI 服務以獲取解釋
• 報告實際訪客的 JavaScript 錯誤

外掛標籤

開發者團隊

⬇ 下載最新版 (v1.0.0) 或搜尋安裝

① 下載 ZIP → 後台「外掛 › 安裝外掛 › 上傳外掛」
② 後台搜尋「Rudwexa – AutoFixer」→ 直接安裝(推薦)

原文外掛簡介

Click Scan Website and Rudwexa – AutoFixer checks:

PHP errors (parses debug.log for fatals/warnings/deprecations)
Deprecated function usage in the active theme and active plugins
Plugin conflicts (known bad pairs + fatal-error attribution)
JavaScript errors (real errors reported by actual visitors, not guesses)
Broken/unregistered shortcodes left over from deactivated plugins
Database issues (orphaned rows, table corruption, transient bloat)
Missing theme/plugin files
REST API reachability
Cron health (overdue events, duplicate-hook bloat)
Slow-query indicators (autoloaded option bloat, object cache presence)
Excessive active plugin count
Broken links in recent content
Security configuration (file editor, XML-RPC, exposed readme.html, etc.)

Every issue gets a plain-language Explain, and — where it is genuinely safe
to automate — Preview Fix, Fix Automatically, and Rollback.
Why some issues aren’t auto-fixable
Not everything should be auto-fixed. A fatal error buried in custom theme
code, a corrupt database table, or which of 60 active plugins to remove are
judgment calls a human needs to make. This plugin is upfront about that:
issues that would be unsafe to change automatically are marked as such, with
an explanation of what to do instead — it does not pretend to auto-fix things
it can’t safely auto-fix.
The safety model
Every fixer follows the same rule: snapshot before you touch anything.
Before a fixer changes a file, a database row, or an option, it writes a
snapshot to a dedicated backup store. Rollback reads that snapshot back and
restores exactly what was there before — no guessing, no partial undo.
External services
This plugin connects to a third-party AI service to power the optional “Ask AI” explanations — a feature that cannot be done locally, since it requires an actual language model to read the diagnostic finding and generate a plain-language explanation and suggested fix. AI requests are made only when you explicitly click an AI action; nothing runs automatically or in the background.
This plugin does not integrate with any AI vendor directly, and does not store or see an API key for one. Instead, it uses WordPress core’s own AI Client (WordPress 7.0+): you connect a provider once, at the WordPress level, under Settings → Connectors — typically by installing the official AI Provider plugin for whichever vendor you choose. The provider you connect there is where the issue text (or, for certain checks, a small code snippet) is actually sent and processed; this plugin has no visibility into or control over that beyond making the request through WordPress’s own API, and does not operate any proxy of its own.
Depending on which provider you connect, the applicable privacy policy and terms are:

Anthropic — Privacy Policy · Terms of Service
OpenAI — Privacy Policy · Terms of Use
Google (Gemini) — Privacy Policy · Gemini API Additional Terms of Service

If no provider is connected, or you’re on WordPress below 7.0, “Ask AI” simply isn’t available — every other part of this plugin works exactly the same either way.
Separately, this plugin includes an optional front-end script that reports real JavaScript errors from your site’s visitors (error message, script URL, and page URL) back to your own site’s REST API, so the “JavaScript Errors” check reflects real visitor experience. This data stays on your own site’s database — it is never sent to a third party. It can be turned off entirely under Rudwexa → Privacy settings.

延伸相關外掛

文章
Filter
Mastodon