LIOSFERA Order Diagnostics
| 开发者 | liosfera |
|---|---|
| 更新时间 | 2026年10月28日 21:57 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
LIOSFERA Order Diagnostics is a locally running WooCommerce diagnostics plugin by LIOSFERA. It detects orders waiting unusually long for payment and monitors WP-Cron and Action Scheduler health. It stores order IDs, technical incident codes and timestamps in local WordPress tables. It never modifies orders or processes money.
Important: A delayed order is not proof that the bank charged the customer. Payment verification must be performed in the original acquiring provider dashboard. This build never calls a bank API and does not claim to recover a missing webhook.
Free includes local incident history, deduplicated warnings, temporary snooze, HPOS and classic WooCommerce order support, configurable thresholds, history retention and optional hourly email/Telegram digests for new warnings. No cloud account, trial period, upsell gate or external service is required.
安装:
- On a supported WordPress/WooCommerce installation, install the plugin ZIP under Plugins > Add New > Upload Plugin.
- Activate. Open WooCommerce > Order Diagnostics.
- Set your scan thresholds and review alerts. Diagnostic scanning is read-only.
- Ensure WP-Cron is invoked regularly; an external cron is recommended for low-traffic stores.
屏幕截图:
常见问题:
Does this confirm a payment was received?
No. Local WooCommerce state is not independent proof of bank settlement. Verify the original acquiring provider dashboard.
Will the plugin change orders or take payments?
No. The scanner does not change order status, amounts, capture or refund payments, or contact bank APIs.
Does it send customer data to a remote server?
By default, no. Diagnostic data remains in WordPress. If the store operator opts in to email, technical incident data is sent using the site's email transport. If the operator connects their OWN Telegram bot, the plugin sends selected diagnostic codes and up to five technical order IDs via HTTPS to api.telegram.org and the paired private chat. No shared LIOSFERA backend is used; no acquiring-bank API requests are made. Order IDs and store URL can be commercially sensitive, so enable these integrations only with appropriate recipient consent.
What happens on deactivation or removal?
Deactivation leaves the local data intact so a reactivation can resume monitoring. Explicit uninstall deletes the plugin-specific tables, options, scheduled tasks and alerts permanently. Back up diagnostic history before uninstall if needed.
How are scans scheduled?
WP-Cron triggers the scans and maintenance. If WP-Cron is disabled, configure a functioning system cron. The plugin reports when the previous scan was delayed.
更新日志:
0.1.0-dev.27
- Disclose Telegram Bot API privacy policy and terms in the plugin readme, and clarify merchant-controlled WordPress email transport privacy obligations. No runtime behavior changes.
- Fail closed when the WordPress options table cannot be confirmed transactional (InnoDB) before an Email or Telegram delivery checkpoint.
- Safely reject nested or invalid diagnostic dashboard URL filters without PHP errors.
- Commit accepted Email/Telegram batch cursors and success timestamps atomically in an InnoDB transaction under a verified sender lock.
- On failed checkpoint, return a retryable result without recording misleading delivery success.
- Prevent outdated Email and Telegram transport failures from restoring errors after opt-out, chat disconnection or lock takeover.
- Require a valid Telegram Message ID before considering sendMessage accepted; malformed HTTP 200 responses remain retryable.
- Verify sender-lock ownership and channel configuration before notification calls and before committing Email/Telegram cursors.
- Avoid stale worker checkpoints after opt-out, bot disconnect or lock takeover during transport, while retaining safe retry semantics.
- Keep action confirmations beside their relevant forms instead of allowing WordPress to relocate admin notices to the top.
- Verify end-to-end authenticated navigation, settings updates, snooze/restore, and incident pagination in an isolated WooCommerce browser.
- Return after scan, settings, Email, Telegram and snooze actions to their relevant page section instead of the top.
- Add accessible native accordions for monitoring and Telegram configuration; incident lists remain open.
- Move action confirmation messages next to their related controls and preserve incident tabs after snoozing/restoring.
- Reject nested form parameters before they can affect notification preferences or incident actions.
- Safely skip malformed Telegram update objects during private-chat pairing.
- System-wide scheduler incident warnings now link directly to WooCommerce scheduled actions, with no diagnostic or notification behavior changes.
- Redesigned WooCommerce admin with responsive monitoring settings, clearly separated notifications, system status, and incident tables.
- Better scan action spacing, compact severity labels, and more readable order links.
- Improved compact Email/Telegram checkboxes for narrow screens.
- Avoids a duplicate Telegram delivery warning when an action result is already shown, while preserving the warning on later visits.
- Fixed duplicate Telegram action feedback notices in the WordPress admin.
- Shows non-sensitive email or Telegram delivery failure only while channel is enabled; existing scan settings unaffected.
- Sanitized scalar Telegram connection and preference fields at the admin POST boundary, in addition to strict token validation, authorization and per-action nonce verification.
- Re-tested the frozen prior candidate against WooCommerce 8.8.3 classic storage in an isolated synthetic shop.
- Added optional self-hosted Telegram bot integration, separate from email and any LIOSFERA shared bot.
- Encrypted private token storage, one-time /start pairing and nonce-protected admin actions.
- New-incident hourly digests, replay protection, manual test and disconnect; no actual customer payment actions.
- Optional hourly email digest for new unresolved incidents, off by default.
- Deduplication, bounded event scans, safe transport retry and test message.
- Corrected semantic HTML for disabled WP-Cron notice and explicit incident table column headers.
- Added adversarial GET, valid-nonce insufficient privilege and axe-core accessibility regression tests.
- Hold a short InnoDB row lock while atomically committing the scanner cursor and health record.
- Compare-and-delete expired and released locks so another worker's ownership is preserved.
- Test concurrent independent MySQL connections, transaction rollback and worker takeover.
- Prevent a superseded scan worker from overwriting a newer worker's cursor or scan status.
- Added simulated and real WooCommerce/MySQL lock handoff regression tests.
- Read-only diagnostic scanner now requires successful incident writes before advancing its cursor.
- Locked scans use owner tokens so expired workers cannot unlock a newer scan.
- Added synthetic and real isolated MySQL write-failure regression tests.
- Added bounded follow-up cleanup when old diagnostic event history exceeds a daily 500-record batch.
- Prepared LIOSFERA WordPress.org icon, banner and isolated screenshots outside the plugin ZIP.
- Release candidate staging and checklist; not published on WordPress.org.
- Tested against PHP 7.4/8.2/8.3/8.4/8.5 and WooCommerce 10.0/11.2 in isolated environments.
- Removed deprecated manual gettext loader; hardened security regression tests.
- Publisher identification standardized to LIOSFERA.
- Safe bounded WP-CLI catch-up mode for high-volume stores.
- Fixed-shape SQL queries for the local incident tables and additional integration tests.
- Browser-checked admin and isolated WooCommerce Blocks checkout.
- Beta preparation: WordPress.org checks, isolated CSS, upgrade and uninstall safety tests.
- Fixed-watermark HPOS/legacy scanner; recent order priority; failed/overdue task monitoring; local incident journal.