Form Flight Recorder
| 开发者 | lukeaxiomflow |
|---|---|
| 更新时间 | 2026年9月8日 06:38 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- The submission that produced no notification. The form completed, the visitor saw the thank-you message, and no email was ever generated — a misconfigured notification, a conflict, a broken hook. Nobody was told about the lead.
- The form that silently stopped working. An update broke the page, a JS error killed the submit button, a spam filter started eating everything. Zero submissions looks exactly like a quiet day — unless something knows the form's normal rhythm.
- Every completed submission is recorded (counts and timestamps — never the content) together with the notification evidence from the same request: emails generated, hand-off to the mail system, transport failures, and the form plugin's own sent/failed status where it offers one (Contact Form 7 does).
- A submission that expected a notification and produced none becomes a "NO notification" alarm.
- A notification the mail transport rejected becomes a "send failed" alarm with the transport's own error text.
- Expectations come from the form plugin's settings at submission time (CF7 skip_mail/demo mode, WPForms notification settings, Gravity Forms active notifications), with a per-form auto/on/off override.
- Every form gets an automatic baseline (its usual submissions/week). A form that normally receives submissions and has gone quiet beyond its threshold — both your configured hours and 3× its typical gap — raises a "form gone silent" alarm. Forms without a meaningful baseline are never flagged (no false alarms on genuinely quiet forms).
- Instant email the first time a form misses a notification, fails a send, or goes silent (max one per form per day).
- Daily or weekly digest — sent only when there's something to say.
- Cockpit page: reconciled ledger, silent forms, per-form baselines.
- Site Health checks and WP-CLI (
wp ffrd status --format=json).
- Page-presence check — daily proof each form still renders on its page (catches "the update removed my form").
- Slack / webhook alert channels.
- Weekend-aware baselines (no Monday-morning false alarms).
- REST status endpoint + CSV export for agencies.
安装:
- Install and activate. You'll find Form Flight Recorder in the admin menu.
- It starts recording with the next submission on any detected form plugin (Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Fluent Forms).
- Set your digest and silence thresholds under Settings; tune individual forms under Forms.
屏幕截图:
常见问题:
Does it store what visitors typed into my forms?
No. Counts, timestamps, form ids/titles, a masked recipient (j***@example.com) and the first 40 characters of the subject line — never field content.
Does it prove the email reached the inbox?
No plugin can. Form Flight Recorder proves your site generated the notification and handed it to the mail system (and records the transport's error when hand-off fails). Deliverability beyond that point is your SMTP provider's territory — the point of this plugin is the failure class where there's nothing for a mail log to show: the email that was never generated at all.
Which form plugins are supported?
Contact Form 7, WPForms (Lite and Pro), Gravity Forms, Ninja Forms and Fluent Forms. Forms from other plugins are not recorded.
My form intentionally sends no email. Will it nag me?
Mark that form "off" on the Forms tab and its missing-notification alerts stop. The heartbeat still watches its submission rhythm.
How does the silence detection avoid false alarms?
A form is only flagged when it averages 3+ submissions/week AND has been quiet longer than both your threshold and 3× its typical gap. Pro adds weekend-aware baselines.
Why did a spam submission not appear in the ledger?
Submissions rejected by validation or flagged as spam never complete, so they are not real submissions — the recorder only counts what the form plugin accepted.
更新日志:
- Event history retention is now a free setting and defaults to keeping everything. It was previously fixed at 30 days in the free build and raised to 90 by the Pro build; that bound is gone, and no build removes it for you. Set your own limit under Settings, or leave it at 0 to keep every row.
- Removed "90-day history" from the Pro feature list, because retention is no longer a paid capability.
- Initial public release: submission-to-notification reconciliation across Contact Form 7, WPForms, Gravity Forms, Ninja Forms and Fluent Forms; zero-submission heartbeat with per-form baselines; instant alerts and daily digest; Site Health tests; WP-CLI with JSON.