內容簡介
Site Remedy AI 是一款本地優先的 WordPress 診斷、監控及恢復工具，旨在幫助管理員了解網站問題的根源，並提供集中化的診斷證據以便快速排除故障。
【主要功能】
• 收集 WordPress 和 PHP 錯誤證據
• 記錄請求、API 和資料庫失敗
• 提供網站健康與環境資訊
• 追蹤插件和佈景主題變更
• 支援維護計畫與定期報告
• 確保隱私的診斷交接
外掛標籤
開發者團隊
原文外掛簡介
Developed by Xpert Developerz – https://xpertdeveloperz.com/
Site Remedy AI is a local-first WordPress diagnostics, monitoring, and recovery toolkit built to help administrators understand what is happening when a site develops problems.
WordPress issues can originate from plugin or theme changes, PHP errors, failed HTTP requests, database failures, scheduled activity, performance problems, or changes in the site’s environment. Site Remedy AI brings diagnostic evidence together so administrators can investigate problems from one central interface instead of troubleshooting by guesswork.
Diagnose WordPress Problems Faster
Site Remedy AI helps collect and organize evidence useful for investigating:
WordPress and PHP errors
Request, API, and database failures
Site health and environment information
Performance evidence
Plugin and theme changes
Incident correlation
Recovery verification
Maintenance planning
Scheduled reporting
Privacy-conscious diagnostic handoff
The goal is to provide better evidence for troubleshooting while keeping decisions and maintenance actions under administrator control.
Understand What Changed
A WordPress site may begin failing after a plugin update, theme change, configuration adjustment, unexpected request, or another site event.
Site Remedy AI records diagnostic and change evidence that can help administrators investigate what happened around an incident and identify useful relationships between errors, component activity, and site changes.
It is designed to support troubleshooting decisions rather than promise automatic repair of every WordPress problem.
Who Is Site Remedy AI For?
Site Remedy AI can be useful for:
WordPress administrators
Developers and technical support teams
Freelancers maintaining client websites
WordPress agencies
WooCommerce site administrators
Site owners who need better diagnostic visibility
It is especially useful when understanding why a problem occurred is important for making a safe recovery or maintenance decision.
Safety Model
Site Remedy AI is designed around administrator-controlled troubleshooting and recovery.
Evidence and deterministic analysis remain local by default.
Plugin/theme maintenance and recovery actions require administrator confirmation.
No unattended plugin/theme updates are performed.
Diagnostic exports are administrator initiated and exclude credentials, API tokens, raw payloads, and other sensitive fields.
Deactivation preserves evidence. Uninstall removes data only when the administrator explicitly selects full data removal in Site Remedy Settings.
Production rollout
Take a normal site/database backup before first deployment or maintenance changes.
Start on a staging or controlled production site and review Dashboard, Action Center, and Settings before broader rollout.
Site Remedy recommendations remain administrator-controlled; review evidence before applying maintenance or recovery actions.
Emergency Recovery Bridge requires HTTPS outside localhost and should only be enabled when standalone recovery access is required.
Development test helpers and the RC uninstall validator are separate tools and are not included in the production package.
Data lifecycle
Deactivation preserves Site Remedy evidence and configuration.
With Retain Site Remedy data selected, uninstall removes Site Remedy runtime schedules and the Emergency Recovery Bridge while retaining Site Remedy data for a later reinstall.
With Delete all Site Remedy data selected, uninstall removes Site Remedy tables, options, transients, schedules, and Recovery Bridge state.
The uninstall policy can be reviewed in Site Remedy AI > Settings before removing the plugin.
Privacy and external services
Site Remedy does not send telemetry, diagnostics, site content, credentials, or usage data to Xpert or to a Site Remedy-hosted service. Core monitoring and diagnostic analysis run on the WordPress site.
Site Remedy observes WordPress HTTP API activity so it can record failures made by WordPress, plugins, or themes. It does not create those third-party requests itself. The destination and privacy terms of those requests are controlled by the component that initiated them.
If an administrator explicitly enables scheduled report delivery or sends a test report, Site Remedy uses the site’s configured WordPress mail system (wp_mail) to send the selected report summary to the email address entered by the administrator. No report is sent to Xpert by default.
Diagnostic downloads are created only after an administrator requests them. They are designed to omit credentials, API tokens, raw request payloads, database queries, stack traces, and free-form sensitive content. Administrators should still review exported files before sharing them with a third party.
Source code
All PHP, JavaScript, CSS, and Recovery Bridge runtime source distributed with Site Remedy AI is included in human-readable source form in the plugin package. No JavaScript build step is required for this release. In particular, admin/assets/js/changes.js is the maintained source file used directly by WordPress and is not a generated or minified artifact.
Emergency Recovery Bridge
The optional Emergency Recovery Bridge is disabled by default. When an administrator enables it, Site Remedy creates a standalone recovery directory under the site’s WordPress content directory so limited recovery access can remain available if normal WordPress bootstrap fails.
The bridge code is shipped with this plugin; Site Remedy does not download or execute remote code. It uses a one-time recovery key, stores only a password hash, requires HTTPS outside localhost, rate-limits authentication attempts, and restricts plugin file disable/restore actions to the last-known plugin snapshot. The bridge is removed when Site Remedy is uninstalled.
