Repository navigation
Releases
Access Ledger 1.1.0 — older findings and CSV export
Access Ledger 1.1 makes saved findings easier to work through: load older orders in bounded pages, search/filter the loaded set, and download formula-safe CSV alongside JSON.
- Adds scan-bound pagination and clear search/export scope.
- Rejects stale cursors when a new scan replaces the previous one.
- Fixes filtered requests on plain-permalink WordPress sites.
- Preserves the existing verified correction, audit and guarded-undo behavior.
Download access-ledger.zip and upload it through WordPress Plugins. Requires WordPress 6.8+, PHP 8.2+, WooCommerce 10+ and InnoDB.
Local validation: 356 integration assertions passed on baseline/current legacy stores and on the extracted release ZIP with HPOS. Separate-process concurrency passed. Chrome exercised the native download (403 → 200 → 403), pagination, CSV/JSON exports, stale-scan recovery, nonce denials and mobile layout. The hosted queue subsequently cleared: all three MySQL 8 matrix jobs passed in run 43465195677.
Access Ledger 1.0.0 — understand download access before changing it
Access Ledger gives WooCommerce store teams a way to investigate rejected download links before resetting permissions.
- Explain one order or scan up to 365 days in resumable batches.
- Separate expired/exhausted access, refunds and uncertain missing permissions from eligible email mismatches.
- Preview and confirm one email-only correction, retaining counts, allowances, expiry and download logs.
- Keep an operator audit trail with guarded undo and export dated findings as JSON.
- Responsive WordPress admin interface; no hosted service, telemetry, build step or runtime package dependency.
Download access-ledger.zip below, upload through Plugins → Add New → Upload Plugin, and open WooCommerce → Access Ledger. Requires WordPress 6.8+, PHP 8.2+, WooCommerce 10+ and InnoDB for corrections.
Validation includes real WordPress/WooCommerce/MySQL fixtures in legacy and HPOS modes, 199 assertions in the current suite, a separate two-process correction/download-consumption test, and Chrome checks that a real download changes from HTTP 403 to 200 after correction and back to 403 after undo. See validation and CI for exact environments and results.
The hosted GitHub Actions run was still queued before jobs were assigned at publication. The release evidence above comes from completed local runs, including WordPress 6.8.3/WooCommerce 10.0.4 and WordPress 7.1.4/WooCommerce 11.3.0. Check the workflow for its current status.
This first release does not create missing permissions, transfer ownership, extend expiry, reset allowances or integrate MemberPress/LearnDash/CRM systems. Test on staging with your extensions before using corrections on a live store. No long-running hosting fleet or large-store benchmark is claimed.