=== Web Plura Diagnostics - Site Health, Email & Update Risk Advisor ===
Contributors: WPlura
Tags: site health, diagnostics, email, performance, updates
Requires at least: 5.8
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 0.2.9
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Find WordPress site health, email, speed, hosting, and update-risk problems before they cost leads, sales, or support time.

== Description ==

Web Plura Diagnostics helps WordPress site owners, agencies, and support teams find problems that quietly hurt leads, sales, trust, and maintenance time. It runs inside wp-admin and turns local site signals into clear, prioritized action items.

Use it when you need to answer practical questions before an update, launch, client handoff, or support call:

* Are forms, password resets, store emails, and lead notifications likely to work?
* Is the site showing health, hosting, cache, cron, or PHP warning signs?
* Which plugin, theme, or update risks should be checked before making changes?
* What should a business owner, developer, host, or support team fix first?
* What can be exported or shared without sending diagnostics to an external service?

For every finding, the plugin focuses on:

* What is wrong
* Why it matters
* What business impact it may cause
* Who should fix it
* What to fix first

No cloud account, no tracking, and no frontend scripts are required for the core diagnostics workflow.

No cloud requirement: core diagnostics, dashboard rendering, exports, and scheduled scans run locally in WordPress.
No tracking: diagnostics scans do not send telemetry or site diagnostics to Web Plura by default.
Free local checks remain available without cloud connection or a paid plan.

= Customer Problems It Helps Solve =

* Missed leads from broken contact forms, weak email setup, or untested notification paths.
* Risky updates when a site has stale plugins, inactive code, commerce dependencies, or no clear pre-update checklist.
* Slow or unstable sites caused by cache gaps, low memory, cron pressure, upload limits, or hosting constraints.
* Confusing support handoffs where clients, developers, and hosts need the same problem summary.
* Reactive maintenance where issues are discovered only after checkout, login, email, or lead capture fails.

= Key Checks =

* Fix First dashboard with score, priority groups, recommended actions, and recent-change history.
* Site Health-style checks for WordPress, database version, PHP limits, timezone, URL alignment, cache signals, and key file permissions.
* Email readiness checks for local mail transport, SPF, DKIM, DMARC, domain alignment, and manual admin-triggered test email results. Diagnostics scans do not send email automatically.
* Lead Capture Health checks for form plugins, contact pages, SMTP readiness, privacy-page status, and form-plugin updates.
* Pre-update Safety checks for inactive plugins, theme update backlog, commerce plugins, builders, and cache plugins.
* Hosting Advisor checks for memory, cache, cron pressure, upload limits, execution limits, and host-support guidance.
* Client-ready diagnostics with problem, impact, owner, urgency, next action, JSON/CSV exports, WP-CLI commands, and multisite network visibility.

= Good Fit For =

* Site owners who want a clear first-pass health, email, performance, and update-readiness review.
* Agencies preparing client reports, maintenance checks, launch reviews, or pre-update safety notes.
* Support teams collecting safe local diagnostics before deeper troubleshooting.
* WordPress admins who want prioritized actions without telemetry or a required cloud account.

Product page: https://wplura.com/products/web-plura-diagnostics
Terms: https://wplura.com/terms
Privacy: https://wplura.com/privacy

== External Services ==

Web Plura Diagnostics is local-first. Diagnostics scans, dashboard rendering, exports, and scheduled scans run inside WordPress by default.

The plugin links to Web Plura product, terms, and privacy pages for support and product information:

* Product page: https://wplura.com/products/web-plura-diagnostics
* Terms: https://wplura.com/terms
* Privacy: https://wplura.com/privacy

The public WordPress.org package uses WordPress.org update checks. Direct/private Web Plura builds may request a signed Web Plura release manifest from https://api.wplura.com/v1/plugin/updates/web-plura-diagnostics/manifest and send only the plugin slug, current version, and release channel.

Data, retention, and uninstall behavior:

* Diagnostics results, history snapshots, explain-mode preference, scheduled-scan settings, export metadata, and manual test-email metadata are stored locally in WordPress options/transients.
* Retention settings allow site admins to control how long local diagnostic history and email-test metadata are kept.
* Uninstall cleanup removes plugin-owned options, transients, scheduled scan hooks, and local diagnostic metadata.

== Installation ==

1. Upload the `web-plura-diagnostics` folder to `/wp-content/plugins/`.
2. Activate the plugin through the `Plugins` menu in WordPress.
3. Go to `Web Plura Diagnostics` in the admin sidebar.
4. Click `Run Diagnostics`.

== Frequently Asked Questions ==

= Who is Web Plura Diagnostics for? =
It is for WordPress site owners, agencies, support teams, and administrators who need a local health, email, performance, hosting, and update-readiness review before deeper troubleshooting.

= What customer problems does it focus on? =
It focuses on practical operational problems: missed form leads, unreliable WordPress email, risky updates, weak hosting readiness, slow or unstable sites, unclear fix priorities, and support handoffs that need a client-readable summary.

= Does this plugin require a cloud account? =
No. It works locally inside WordPress.

= Will this slow down my website? =
No frontend scripts or frontend monitoring are added by default. Diagnostics run inside wp-admin, scheduled scans are optional, and the plugin does not automatically change public content.

= Does this send my site data to Web Plura? =
No. The free plugin is local-first and does not send diagnostics, logs, or telemetry to an external server by default.

= Does it replace a firewall, malware scanner, or backup plugin? =
No. It provides local diagnostic insights and prioritized guidance. Use a dedicated firewall, malware response process, and backup/restore system where those protections are required.

= Does it send emails automatically? =
No. It only sends a manual test email when an admin explicitly clicks the button.

= Does it perform updates automatically? =
No. It only provides update-safety guidance.

= Does it support Multisite? =
Yes. It includes a multisite network dashboard surface for cross-site diagnostics visibility. Individual site access still follows WordPress capability checks.

= Does it include WP-CLI support? =
Yes. Admins can use `wp web-plura-diagnostics scan`, `wp web-plura-diagnostics export`, and `wp web-plura-diagnostics cleanup` for local operational workflows.

= Does it integrate with WordPress Site Health? =
Yes. WordPress Site Health can show a cached Web Plura Diagnostics score after diagnostics have run. The Site Health test reads cached local results and does not start a fresh scan.

= Does it collect telemetry? =
No. It stores local diagnostics cache and limited local metadata only.

= What data is removed on uninstall? =
The plugin removes plugin-owned options, transients, scheduled scan hooks, local diagnostic history, and local action metadata during uninstall.

= Where can I get support or product information? =
Use the WordPress.org support forum, or visit https://wplura.com/products/web-plura-diagnostics.

== Screenshots ==

1. Main dashboard showing site score, risk level, and Fix First issues.
2. Business-friendly diagnostics with problem, impact, owner, and next action.
3. Email Delivery Readiness for forms, password resets, and store emails.
4. Lead Capture Health for contact forms and silent lead-loss risks.
5. Hosting Advisor with copyable message for hosting support.
6. Pre-update Safety Check for plugins, themes, and recovery readiness.

== Changelog ==

= 0.2.9 =
* Improved the WordPress.org title, tags, and problem-focused readme copy for site health, email, performance, hosting, update risk, and lead capture diagnostics.
* Kept the public package local-first by removing the hard cloud plugin dependency header; optional Web Plura Cloud integration remains guarded in code.

= 0.2.8 =
* Updated the WordPress.org release package with the current local diagnostics admin UI, assets, uninstall cleanup, and readme metadata.
* Kept diagnostics local-first with no telemetry or required cloud account for core checks.

= 0.2.7 =
* Improved dashboard Recommended Actions with ordered action rows, priority badges, source context, and module links.
* Improved dashboard Recently Changed history with a compact timeline and previous/current value chips.
* Kept the public package local-first and streamlined the admin workflow.

= 0.2.6 =
* Improved WordPress.org listing copy, screenshots, Site Health integration, scheduled scans, retention cleanup, email dependency checks, cache checks, OPcache readiness, exports, and admin UI clarity.

= Earlier releases =
* Added the local diagnostics runner, health checks, email checks, performance checks, plugin impact checks, hosting checks, lead capture checks, update-risk checks, recommendations, exports, WP-CLI commands, scheduled scans, and WordPress-native admin UI improvements.
