DiagnosticIQ for WooCommerce
| 开发者 | johnokeane |
|---|---|
| 更新时间 | 2026年8月3日 07:01 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Your money path, watched live — payments, checkout, order emails, orders flowing, site online: every step a customer takes to pay you, each with a live status. Catch a break the moment it happens, before it costs you a sale.
- Around-the-clock watch on your most valuable asset — 24/7, DiagnosticIQ guards the store your business runs on. It flags the silent sales-killers that quietly cost you orders — a payment gateway switched off, order emails not sending, checkout erroring out, order flow stuck — and the nastier surprises too: files in your site root that don't belong (an early sign of malware), plus a snapshot of the plugin, theme, and WooCommerce versions you'll need when something breaks.
- Opt-in email alerts — scheduled scans can email you when a new critical problem or a health-score drop appears. Alerts are opt-in, and delivery rides your site's own email (see the FAQ) — everything an alert would tell you is always on the dashboard too. Free for everyone.
- Tell it what you're seeing, in your own words. "Checkout isn't working," "orders stopped coming in" — no logs to pull, no jargon to learn. Guided intake turns a symptom into a diagnosis.
- Purpose-built AI for WooCommerce — not generic slop. It reasons over your store's own signals — plugin and theme inventory, versions, recent errors, mail failures, config — against the WooCommerce failure patterns it's built to recognize, and names the root cause and the exact fix steps in plain English.
- Safe to try yourself — store-owner steps with no risk (re-enable a gateway, flip a setting back, clear a stuck queue), in plain English.
- Hand to your developer — anything needing code or deeper access, written as a scoped brief (the cause, the signals behind it, the suggested fix) so they start at the solution, not discovery.
- Confidence & safety on every step — each step is flagged for how sure the diagnosis is and whether it's safe to run, so nothing gets applied blind. And it's all read-only: DiagnosticIQ shows you the fix, never touches your site.
- Store owners who want to know what's wrong before paying a developer to find out.
- Agencies and freelancers who want the root cause in minutes when a client's store breaks.
安装:
- Install and activate the plugin through the WordPress Plugins screen.
- Open DiagnosticIQ in your admin menu — the Store Health Dashboard starts working immediately, free.
- When something breaks, run an AI diagnosis from the Diagnose screen — your first 2 diagnoses are free on every site, no key needed.
- (Optional) Add a license key under DiagnosticIQ → Settings for 20 AI diagnoses a month ($29/mo).
屏幕截图:
常见问题:
Is the free version actually useful, or is it a trial?
It's genuinely free and standalone. The Store Health Dashboard, money-path strip, local problem rules, unexpected-file scan, and opt-in email alerts (sent via your site's own email — see the alerts FAQ) run forever on your server with no account, no key, and no external calls. On top of that, your first 2 AI diagnoses are free on every site — no key needed.
Does the free version send my data anywhere?
No. It runs entirely locally. Only the AI diagnosis sends data (including your free ones), only when you run one, and only the diagnostic payload described under "External services" above.
Will the diagnosis change anything on my site?
No. DiagnosticIQ is read-only. It reports; you (or your developer) decide what to do.
I have a developer — how does this help them?
It hands them the case already worked up, so they don't start from zero. Each diagnosis is a scoped brief: the root cause, the specific signals behind it (the plugins, settings, versions, and recent changes involved), and a suggested fix path — so they skip the billable "discovery" phase and start at the solution. From there they apply their own expertise, playbooks, and coding tools to ship the fix fast. You pay for the fix, not the hunt.
Does it work with my payment gateway / theme / host?
The dashboard reads standard WooCommerce and WordPress state, so it works anywhere WooCommerce runs — any host, any gateway, any theme. Some tier-1 rules go deeper for Stripe.
The one exception: the AI diagnosis and license check need your site to be able to reach our service at billing.wptechhouse.com over HTTPS. Almost every host allows this. If your site is locked down with WordPress's WP_HTTP_BLOCK_EXTERNAL setting, add billing.wptechhouse.com to WP_ACCESSIBLE_HOSTS and everything works.
How do the automatic background scans run?
Scans run on your site's own WordPress scheduler (WP-Cron), which fires when your site gets visits. On most hosts that's plenty. Two setups worth knowing about: very quiet sites may go longer than the chosen interval between scans, and some hosts replace WP-Cron with their own scheduler (Kinsta and Pantheon do this for you automatically; on WP Engine you can switch on "Alternate Cron" in your portal). If the dashboard's "last scan" time looks old, asking your host to run wp-cron.php on a server schedule fixes it for good — it's a standard, five-minute request. Your dashboard always shows when the last scan actually ran, so you can see for yourself that the watch is on.
Will alert emails definitely reach me?
Alerts use your site's standard WordPress email, so they're only as reliable as your site's email in general. Many hosts deliver it fine; some (by their own recommendation) need an SMTP plugin for dependable delivery. Everything an alert would tell you is also always on the dashboard.
Does it work on multisite?
It's built and tested for single-site WooCommerce stores. It may run on multisite, but we haven't verified it there yet — if you run a network and want this, tell us and we'll test it with you.
Do I need WooCommerce?
Yes. The plugin is built for WooCommerce stores and requires WooCommerce to be installed and active.
更新日志:
- Honest under every host: an overdue background scan now says so (with how to fix it), a file check that couldn't run no longer looks "clean", and password-protected sites no longer trigger false "broken" readings.
- Diagnoses in progress survive aggressive object caches; health screens refresh properly behind LiteSpeed-style page caches.
- Clearer copy: the paid plan is described as 20 diagnoses a month everywhere; email alerts are described as opt-in and delivered through your site's own email; a heads-up before your last free diagnosis.
- Calmer visuals: severity badges unified to the dashboard's neutral style; other plugins' banners no longer push our screens below the fold.
- Free tier: your first 2 AI diagnoses are free on each site — no card, no license key. The dashboard and diagnosis screens show how many you have left.
- A license now covers a monthly allowance of 20 diagnoses; settings and admin copy updated to say so (a key is no longer required to try a diagnosis).
- Declare WooCommerce as a required plugin (Requires Plugins header, WordPress 6.5+ plugin dependencies).
- Maintenance: initialize health-alert defaults on activation. Alerts remain opt-in on this build — no email is sent until you enter one in Settings.
- The site-root file check now uses the WordPress Filesystem API (read-only; nothing is written).
- Removed an unnecessary core-file include and an error-level read.
- Privacy: IP-address scrubbing now catches all public addresses (a 0.7.6 refinement could miss some); plugin version numbers are still preserved.
- Internal prompt constants no longer use HEREDOC/NOWDOC syntax, per WordPress.org coding guidance.
- Minor packaging and header tidy-ups.
- Removed the development README from the WordPress.org package.
- Upgrades from 0.7.4 now migrate the existing diagnostic log instead of deleting it, and uninstall also cleans data left by pre-rename versions.
- Smarter scrubbing: plugin version numbers are no longer mistaken for IP addresses.
- Alert emails are rate-limited so an intermittently failing check cannot re-email on every scan.
- Add-ons: activation no longer requires a specific base-plugin folder name, and each add-on now cleans up after itself on uninstall.
- Renamed the plugin and its internal code prefix for WordPress.org directory compliance. Existing installs migrate their settings, license, and history automatically on update.
- The add-on unlock now completes on our website rather than charging in wp-admin.
- External-services documentation expanded to enumerate exactly what a diagnosis sends and to name Anthropic as the processor.
- Scrubbing now also redacts IP addresses and full email addresses before a diagnosis is sent.
- Hardening: prepared SQL for order/session counts, CSV-export formula-injection guard, musl-safe uninstall, IIS/autoindex log-directory guards, HPOS compatibility declaration, optional admin-bar pill toggle.
- Scheduled-scan email alerts are now free for everyone (no longer license-gated).
- All admin JS/CSS moved to properly enqueued assets.
- Diagnostic log now resolves its path via wp_upload_dir() for multisite/custom-uploads compatibility.
- Error handler no longer overrides the site-wide PHP error_log destination.
- WordPress.org release: directory-served updates (no bundled update checker).
- Hardened debug-log handling; legacy log files removed on upgrade.
- Expanded PII scrubbing (phone numbers) before any diagnosis is sent.
- Free tier is fully silent without a license key — no external calls.
- Expanded signal taxonomy: tier-1 rules plus Stripe, cache-loopback, and HPOS collectors.
- Store Health Dashboard refinements.
- Licensing and diagnosis reliability fixes.
- Store Health Dashboard with money-path strip.
- Async diagnosis engine.
- Initial release: guided intake and plain-English diagnosis.