Sale!

WPStore+ Database Autoload Health

Name: WordPress Database Autoload Health & Safe Cleanup - WP Store Plus
Price: 39.00 USD
Availability: InStock

฿1,424EstimatedOriginal: Original price was: $59.00.Current price is: $39.00.

Audit WordPress autoloaded options, monitor database growth, safely clean eligible expired transients, and recover records through verified quarantine—without automatic destructive actions.

Launch Price: $39/year · Regular Price: $59/year · 1-Site License

Categories: Database & Optimization, WordPress Plugins Tags: Autoload Health, Database Autoload, Database Monitoring, Expired Transient Cleanup, Safe Database Cleanup, WordPress Database, WordPress maintenance, WordPress Performance

WPStore+ Database Autoload Health is a safety-first WordPress database diagnostics and controlled-cleanup plugin designed for website owners, developers, agencies, and technical support teams.

The plugin helps you understand how autoloaded options, transient records, and database tables affect your website before making any changes. It measures autoload size, identifies probable data ownership, reviews possible leftover options, monitors table growth, and provides a controlled workflow for cleaning eligible expired transients.

Unlike aggressive database-cleanup tools, WPStore+ Database Autoload Health follows an evidence-first approach. Unknown ownership, inactive plugins, large database records, or matching prefixes are never treated as sufficient evidence for deletion.

Safe Transient Cleanup is limited to narrowly defined database-backed records that pass live revalidation. Every cleanup operation follows a controlled workflow:

Preview → Backup → Integrity Verification → Quarantine → Cleanup → Recovery

Ordinary WordPress options remain review-only. The plugin does not provide general option deletion, automatic autoload changes, third-party table deletion, scheduled cleanup, or automatic destructive actions.

Why use WPStore+ Database Autoload Health?

WordPress websites can accumulate autoloaded options, expired transients, plugin metadata, and growing database tables over time. However, removing database records without clear evidence can break plugins, themes, scheduled tasks, sessions, checkout processes, or site configuration.

WPStore+ Database Autoload Health helps administrators:

Understand autoload pressure
Review the largest autoloaded options
Identify probable plugin or theme ownership
Detect possible leftover options without deleting them
Monitor database table growth
Clean only eligible expired transient records
Keep exact recovery backups in quarantine
Restore missing records without overwriting current data
Generate privacy-safe diagnostic reports
Receive metadata-only health alerts
Verify production and recovery readiness

Safety-first principles

Evidence before recommendation
Preview before cleanup
Backup before deletion
Quarantine before source-record removal
Live revalidation before every destructive step
No automatic cleanup
No ordinary option deletion
No automatic autoload modification
No third-party table deletion
No overwrite during recovery
Existing recovery access is never blocked by license status

Installation

### Install through WordPress Admin

1. Download the plugin ZIP file from your WPStore+ account.
2. Sign in to your WordPress administration area.
3. Go to Plugins > Add New Plugin.
4. Select Upload Plugin.
5. Choose:

WPStore-Database-Autoload-Health-v2.0.0.zip

6. Select Install Now.
7. After installation is complete, select Activate Plugin.
8. Open WPStore+ Autoload > Setup & Readiness.
9. Review the Safety Boundary and environment checks.
10. Open WPStore+ Autoload > License & Secure Updates.
11. Enter your license key and select Activate License.

### Updating from an earlier version

1. Create a full database backup.
2. Go to Plugins > Add New Plugin > Upload Plugin.
3. Upload the latest ZIP file.
4. Select Replace current with uploaded.
5. Wait for the update to complete.
6. Open WPStore+ Autoload > Production Readiness.
7. Confirm that the migration, recovery tables, package integrity, and license status are ready.

The plugin uses guarded and idempotent migrations. Existing scans, monitoring history, cleanup records, quarantine backups, recovery settings, and diagnostic metadata are preserved during supported upgrades.

### Recommended preparation

Before running any cleanup:

* Create a complete database backup
* Test on a staging website first
* Confirm that the website has a working restore point
* Review the Dry Run Preview carefully
* Download the pre-cleanup backup
* Do not use cleanup while a persistent external object cache controls transient storage
* Never use a public support ticket to share a sensitive cleanup backup

### Minimum requirements

* WordPress 6.6 or later
* PHP 7.4 or later
* Administrator access
* A database user that can read the required metadata
* A current backup before performing cleanup

Frequently Asked Questions

1. Does the plugin delete ordinary WordPress options?

No. Ordinary options remain diagnostic and review-only, including options classified as Possible Orphan.

The plugin does not provide a general option deletion action.

2. Does Possible Orphan mean Safe to Delete?

No.

Possible Orphan means that historical ownership evidence indicates the option may have belonged to a removed plugin or theme. It is still classified as Manual Review Only and cannot be deleted through the plugin.

3. Can the plugin change an option’s autoload setting?

No.

The plugin reports the current autoload state but does not automatically or manually modify autoload settings for ordinary options.

4. What records can Safe Transient Cleanup remove?

Only narrowly defined and revalidated database-backed records:

* Expired transient value-and-timeout pairs
* Orphaned timeout records without a matching value record

The following remain protected or review-only:

* Active transients
* Future transients
* Malformed timeout records
* Value-only transients
* Ignored records
* Unverified records
* Records that fail live revalidation

5. Does the plugin automatically clean the database?

No.

The plugin does not include:

* Scheduled cleanup
* Automatic cleanup
* Automatic restore
* Automatic quarantine purge
* One-click Clean All
* Ordinary option deletion
* Automatic table optimization

Every cleanup must be started manually by an administrator.

6. How does the quarantine system work?

Before eligible source records are removed, the plugin stores exact copies in plugin-owned quarantine tables.

The records are verified using integrity checks before cleanup continues. Quarantined records remain available for:

* Backup download
* Recovery preview
* Conflict review
* Restore
* Metadata-only recovery reporting
* Manual purge

7. Can the plugin overwrite existing data during restore?

No.

Restore behavior is conflict-safe:

* Missing records can be restored
* Identical current records are treated as already restored
* Different current records are classified as conflicts and skipped
* The plugin never overwrites a current record containing different data

8. Can I restore a cleanup batch after my license expires?

Yes.

The Recovery Guarantee keeps the following available regardless of license status:

* Existing backup downloads
* Recovery previews
* Conflict reviews
* Restore actions
* Recovery reports
* Manual sensitive-backup purge controls

9. What happens when the license becomes inactive?

Core Mode remains available.

You can continue to use read-only diagnostics and access existing recovery data. Creating new licensed work is paused until the license or valid offline grace is restored.

Examples of licensed work include:

* Building Ownership Intelligence
* Running advanced Orphaned Options Review
* Creating new table snapshots
* Starting a new Safe Cleanup batch
* Running health monitoring
* Creating diagnostic snapshots
* Exporting a new Support Report

10. Does the plugin work with Redis or Memcached?

Read-only diagnostics remain available.

When WordPress reports an active persistent external object cache, database transient cleanup and restore are blocked because the WordPress database may not be the authoritative transient storage location.

11. Does monitoring perform cleanup or database repair?

No.

Scheduled monitoring reads metadata and sends alerts only. It does not perform:

* Cleanup
* Restore
* Purge
* Autoload changes
* Table deletion
* OPTIMIZE TABLE
* REPAIR TABLE

12. Does the plugin delete database tables?

It does not delete third-party database tables.

Plugin-owned recovery tables can be removed only during WordPress uninstall when the administrator explicitly selects Remove All Plugin Data and completes the required confirmation.

13. Does the Support Report contain sensitive values?

The Support Report is designed to exclude:

* Stored option values
* Ordinary option names
* Transient keys and values
* Database row contents
* Email addresses
* Site URLs
* Database names
* Passwords
* Tokens
* API keys
* Authorization data
* Absolute server paths
* Raw cleanup batch identifiers

The report must pass a recursive privacy audit before it can be downloaded.

14. Is the cleanup backup safe to share?

No.

The cleanup backup may contain real transient data encoded in Base64. Base64 is not encryption.

Keep the backup private and do not attach it to public support tickets. Use the metadata-only Support Report or Recovery Report instead.

15. Does the plugin guarantee faster website performance?

No specific performance improvement is guaranteed.

The plugin helps identify autoload pressure, database growth, and eligible expired transient records. Actual results depend on the website, hosting environment, database workload, active plugins, and the records reviewed.

16. Does the plugin support WordPress Multisite?

Yes.

Diagnostics and plugin-owned data are scoped per site. Network activation, upgrade, deactivation, and uninstall operations are processed in bounded batches.

17. What happens when the plugin is uninstalled?

The administrator can choose one of three policies:

** Remove Operational Data; Keep Recovery

Default option. Removes operational settings while retaining recovery data.

** Preserve All Plugin Data

Keeps plugin-owned options and recovery tables.

** Remove All Plugin Data

Deletes all plugin-owned data and recovery tables. This option requires explicit acknowledgement and typed confirmation.

Malformed or unknown policy settings automatically fall back to Keep Recovery.

Changelog

### 2.0.0 — Final Commercial Stable Release

* Finalized commercial production metadata and stable update channel.
* Added Production Readiness status.
* Added production package profile and complete runtime-file inventory verification.
* Added metadata-only Production Report.
* Finalized supported upgrade paths.
* Finalized signed upgrade checkpoints and downgrade protection.
* Finalized uninstall policies.
* Finalized privacy boundaries.
* Finalized license enforcement and Recovery Guarantee.
* Confirmed no expansion of destructive cleanup capabilities.
* Completed 1,800 runtime tests with no plugin-related entries in debug.log.

### 1.10.0 — Commercial Release Candidate

* Added Release Readiness workspace.
* Added package integrity manifest.
* Added guarded and idempotent install and upgrade migrations.
* Added automatic schema downgrade protection.
* Added HMAC-signed upgrade checkpoints.
* Added explicit uninstall data policies.
* Added metadata-only Release Report.
* Added commercial readiness details to System Status and Support Report.
* Completed 1,620 runtime tests.

### 1.9.0 — Commercial Hardening & Admin UX

* Added Setup & Readiness workflow.
* Added atomic site-scoped runtime locks.
* Added duplicate-operation protection.
* Added memory preflight.
* Added bounded metadata-only runtime diagnostics.
* Added bounded full Autoload CSV export.
* Added strict HTTP method enforcement.
* Hardened administrator actions and state-changing requests.
* Improved keyboard accessibility and responsive layout.
* Added Multisite batch processing safeguards.
* Completed 1,440 runtime tests.

### 1.8.0 — License Integration & Safe Feature Gate

* Added WPStore License activation, validation, deactivation, and site synchronization.
* Added secure commercial update checks.
* Added seven-day site-bound offline grace.
* Added signed local license backup.
* Added host, product, plugin basename, release-channel, and downgrade checks.
* Added Core Mode and Licensed Feature separation.
* Added Recovery Guarantee.
* Added fail-closed handling for unknown premium features.
* Completed 1,260 runtime tests.

### 1.7.0 — Support Report & Diagnostics

* Added privacy-safe TXT and JSON Support Reports.
* Added selectable report sections.
* Added recursive privacy audit.
* Added HMAC site fingerprints and report identifiers.
* Added metadata-only export logs.
* Added manual diagnostic snapshots.
* Added snapshot comparison.
* Added plugin-owned option autoload readiness audit.
* Added malformed-data hardening.
* Completed 1,080 runtime tests.

### 1.6.0 — Scheduled Health Monitoring & Email Alerts

* Added opt-in daily or weekly health monitoring.
* Added manual metadata-only health checks.
* Added privacy-safe test email.
* Added autoload health alerts.
* Added database table risk and growth alerts.
* Added expired transient backlog alerts.
* Added quarantine review alerts.
* Added scan availability alerts.
* Added incident lifecycle and reminder cooldowns.
* Added recovery notifications.
* Added aggregate email delivery.
* Added bounded monitoring and alert history.
* Monitoring remained disabled by default and non-destructive.
* Completed 920 runtime tests.

### 1.5.0 — Safe Cleanup Workflow & Recovery Controls

* Added time-limited HMAC cleanup preview seals.
* Added verified quarantine-before-delete.
* Added post-cleanup outcome verification.
* Added live recovery preview.
* Added conflict-safe restore.
* Added manual quarantine review periods.
* Added explicit sensitive-backup purge.
* Added metadata-only audit events.
* Added metadata-only Recovery Report.
* Expanded the recovery schema while preserving existing backups.
* Completed 760 runtime tests.

### 1.4.0 — Database Table Health & Growth Monitoring

* Added read-only Database Table Health workspace.
* Added table-level metadata analysis.
* Added probable table-owner attribution.
* Added conservative table assessments.
* Added database table health score.
* Added explicit manual snapshot history.
* Added growth comparison.
* Added selected metadata CSV export.
* Added information_schema and SHOW TABLE STATUS fallback.
* No table cleanup, optimization, or repair was added.
* Completed 600 runtime tests.

### 1.3.0 — Orphaned Options Review

* Added metadata-only ordinary option review.
* Added conservative classifications.
* Added Possible Orphan classification.
* Added source installation history.
* Added removed-source history.
* Added bounded database scanning.
* Added privacy-safe selected-row CSV export.
* Kept every ordinary option review-only.
* Enforced cleanup_allowed = no.
* Completed 520 runtime tests.

### 1.2.1 — Pagination UI Hotfix

* Corrected vertical pagination layout in Autoload Options.
* Added scoped horizontal pagination.
* Added responsive wrapping.
* Added keyboard-focus styling.
* Added accessibility labels.
* Preserved the Safe Transient Cleanup engine and database schema.
* Completed 60 focused runtime tests.

### 1.2.0 — Safe Transient Cleanup

* Added database-backed transient scanning.
* Added conservative transient classification.
* Added Dry Run Preview.
* Added downloadable pre-cleanup backup.
* Added quarantine-before-delete.
* Added cleanup history.
* Added conflict-safe restore.
* Added exact-record deletion safeguards.
* Added persistent object-cache protection.
* Limited cleanup to eligible expired pairs and orphaned timeouts.
* Added plugin-owned quarantine and cleanup-history tables.
* Completed 440 runtime tests.

### 1.1.0 — Ownership Intelligence

* Added bounded plugin and theme source indexing.
* Added MU plugin and drop-in source indexing.
* Added exact WordPress Option API reference detection.
* Added probable owner, confidence, and evidence.
* Added installed, inactive, removed, and network-active source states.
* Added manual owner rules.
* Added a non-destructive ignore list.
* Added historical source evidence.
* Expanded metadata-only exports.
* Preserved a fully read-only ordinary-option workflow.
* Completed 320 runtime tests.

### 1.0.0 — Initial Read-only Commercial MVP

* Added Autoload Health Dashboard.
* Added total autoload size and option count.
* Added largest autoloaded option review.
* Added Site Health and large-option thresholds.
* Added explainable health score.
* Added conservative probable ownership.
* Added WordPress core protection.
* Added search, filtering, sorting, and pagination.
* Added metadata-only CSV export.
* Added privacy-safe System Status.
* Included no cleanup, option deletion, autoload changes, table operations, or automatic actions.
* Completed 190 runtime tests.