內容簡介
StackFirefly 外掛可協助使用者發現 WordPress 中被正常運行監控忽略的問題。透過 Firefly Agent 將網站連接至 StackFirefly 監控服務，使用者能夠追蹤排程任務、電子郵件傳送或背景請求的失敗情況，並進行問題調查與恢復追蹤。
【主要功能】
• 監控 PHP 和瀏覽器 JavaScript 錯誤
• 檢查 WP-Cron 執行及 WooCommerce Action Scheduler 任務
• 提供用戶請求的電子郵件測試
• 進行伺服器端檢查以識別已知的外掛/佈景主題漏洞
• 支援 WordPress Multisite 網路啟用
• 整理重複報告以便於問題回顧
外掛標籤
開發者團隊
原文外掛簡介
Find WordPress problems that uptime monitoring misses.
Firefly Agent connects WordPress to the StackFirefly monitoring service. A website can be online while scheduled tasks, email delivery or background requests are failing. StackFirefly brings those observations together so you can investigate issues and track recovery.
A StackFirefly account and connection to the external service are required. Service availability and allowances depend on your account plan. Review current plans at https://stackfirefly.com/pricing before connecting. This plugin is the local connector; monitoring history, incident correlation and AI-assisted diagnosis run in the hosted service.
Monitoring
PHP and browser JavaScript errors, with sanitized diagnostic details and traces where available.
WP-Cron execution, WooCommerce Action Scheduler jobs, and REST/AJAX connectivity.
User-requested email tests and configured monitoring email tests.
Component inventories for server-side checks against known plugin/theme vulnerabilities.
Bounded WordPress core/uploads file scans and privacy-minimized configuration change summaries.
Security-header checks and Lighthouse/PageSpeed performance history provided by the hosted service.
AI-assisted suggestions use collected evidence; they are not proof of a cause or recovery. This plugin does not automatically repair your site, edit configuration files or update other plugins. Available evidence varies by error, connection and site configuration.
WordPress Multisite is supported through network activation. Pair the main website, then choose which subsites to monitor in StackFirefly. Initial discovery supports up to 100 websites. Selected websites use individual site allowances; shared core/configuration findings appear on the main website.
From an error to a next step
Repeated reports are grouped into issues so you can review available evidence, follow recent changes, and record your investigation. Acknowledgements, reported fixes and verified recovery stay distinct. Deterministic checks establish recovery; an AI suggestion does not mark a problem as fixed.
Connect your AI assistant with MCP
Connect StackFirefly to ChatGPT, Claude, Codex or another compatible remote MCP client. Your assistant can review selected sites’ issues, available evidence, recent changes and Lighthouse results without copying reports between tools.
Choose the workspace, sites and permissions. Connections are read-only by default. Optional permissions allow issue acknowledgements, reported-fix notes and verification requests, not changes to WordPress. Revoke access in StackFirefly at any time; newly added sites are not shared automatically.
This optional hosted-service feature requires manual setup and an AI account that supports remote MCP connections. It is separate from StackFirefly’s built-in AI diagnosis. Setup guide: https://stackfirefly.com/docs#ai-connections
External services and data
StackFirefly — https://stackfirefly.com
Pairing explicitly connects the site to StackFirefly over HTTPS. Before pairing, the plugin does not upload monitoring telemetry. Clicking the account/setup link passes the site’s home URL, WordPress installation URL and display name to StackFirefly to prefill setup. Paired sites send authenticated heartbeats (normally every five minutes) and bounded batches of observations; inventory is sent periodically or when changes are detected. Retries are bounded. Reliable scheduled delivery requires working WordPress cron or a host-managed cron runner.
Data may include site URLs and name, Agent/platform versions, PHP and web-server information, installed component names/slugs/versions and update state, status codes and timings, scheduler counts/ages, sanitized error messages, relative file/asset paths and line numbers, bounded stack frames, safe public page paths, third-party resource hostnames, file fingerprints and recognized configuration-setting change categories. Browser collection is served locally, is rate-limited and does not create visitor tracking identifiers. Requested PHP traces are bounded and omit function arguments.
Passwords, API secrets, cookies, authorization headers, form contents, order/customer records, raw request bodies and complete response bodies are not intentionally collected. File contents and private configuration values stay on the site. Diagnostic sanitization limits the detail available; not every error includes a trace or page location.
StackFirefly uses this data for monitoring, issue history, notifications and requested diagnosis. Its external probes request configured public pages. Performance tests, when requested or scheduled in the service, submit the public test URL to Google PageSpeed Insights. The plugin itself does not call Google PageSpeed Insights. AI-provider processing is described in the service privacy notice. If you authorize an external AI client through MCP, the selected monitoring context is shared with that client under your chosen permissions and the AI provider’s own terms and privacy settings. MCP tools do not return Agent credentials or pairing keys; the plugin does not connect to those AI clients directly.
StackFirefly terms: https://stackfirefly.com/terms
StackFirefly privacy: https://stackfirefly.com/privacy
Google terms: https://policies.google.com/terms
Google privacy: https://policies.google.com/privacy
WordPress.org checksum service — https://api.wordpress.org/core/checksums/1.0/
After pairing, WordPress’s checksum API may be used during scheduled core integrity checks. WordPress version and locale are sent to retrieve reference checksums. WordPress.org receives the requesting server’s connection metadata. No local file contents are sent to that service.
WordPress.org privacy: https://wordpress.org/about/privacy/
WordPress.org terms: https://wordpress.org/about/terms-of-service/
Updates
The WordPress.org package uses native WordPress plugin updates. Earlier direct-download packages use StackFirefly’s signed release channel. Both use the same plugin folder and saved connection settings. Do not delete/uninstall the old plugin to migrate; use WordPress’s upload-and-replace flow using the directory package. See the FAQ.
