Trickle 0.1.24

Trickle 0.1.24

• Add one-click transfer diagnostics inside the lightbox for all outcomes, with redacted retained logs and a selectable-text clipboard fallback.
• Tighten wrapped transfer-button labels while retaining comfortable padding and the minimum button height.

Validation: all 18 JavaScript suites, diagnostic-report and AJAX guard PHP checks, runtime PHP syntax and offline security checks passed. Desktop/mobile renders covered successful, failed and warning outcomes plus wrapped enabled/disabled button labels. Native controller diagnostics remained readable while the mutation lock was held. No live migrations were run for this release.

Diagnostics contain retained controller logs and recorded remote responses; separate remote server logs are not fetched. Install the same build at both ends before migrating.

Trickle 0.1.23

Trickle 0.1.23

• Compact plugin/theme comparisons into single-line rows; show green/up upgrades, red/down downgrades and neutral matches while retaining versions, activation, sizes and available updates.
• Verify installed file hashes, obsolete-file removal, table swaps and activation directly in resumable steps; rollback real replacement failures without making HTTP self-requests.
• Improve TLS and request diagnostics for optional HTTP probes, preserving explicit CA configuration.
• Keep table replacement from replaying while final verification resumes.
• Display quoted site titles and saved labels as plain text in both directions without weakening HTML escaping.
• Open Settings once after individual dashboard activation; leave bulk activation, CLI and silent updates unchanged.

Validation: all 17 JavaScript suites, six isolated PHP suites plus the CLI activation check, runtime PHP syntax and offline security checks passed. Desktop/mobile rendering covered 17 compact plugin rows and active parent themes. The native disposable-peer cycle passed file/database pull, resumable verification after one table swap, backup restore, corruption rollback and cancellation recovery. No customer production sites were modified. Verification checks migration integrity; it does not replace frontend functional testing.

Install the same build on both sites before transferring.

Trickle 0.1.22

• Trim repeated setup instructions, media help, connection copy and save confirmations.
• Keep progress sizes beside component names on desktop and left-aligned beneath them on mobile.
• Hide the transfer heading's focus outline while preserving keyboard focus on controls.

Validation: all 17 JavaScript suites and changed PHP template syntax checks passed. Offline desktop/mobile renders covered Settings, Diagnostics and media selection; dialog checks verified size alignment, heading focus and keyboard indicators on controls. UI-only changes; no migration or production-site testing was run for this release.

Install trickle.zip in WordPress → Plugins → Add Plugin. Both ZIP assets contain the same WordPress-ready package.

Trickle 0.1.21

• Keep progress monotonic across delayed polls and reloads; use half-tone transferred fill, full-tone verification and gold replacement.
• Consolidate View backup, Done and View site in one completion footer and remove redundant success text.
• Show component transfer progress from measured compressed byte ranges and acknowledged offsets; keep older snapshots’ progress at the whole-stream level.
• Sort and group activity, remove duplicate completion/stream entries, and retain exact failure details.
• Distinguish uncertain errors from confirmed stopped/cancelled transfers; include final cleanup in elapsed time.
• Use binary size units consistently and report independent force settings for plugins, themes and media.
• Restore the most recent transfer direction on page load.
• Keep bounded replacement checks available during maintenance and respect retry pauses during cancellation.

Validation: 17 JavaScript suites, 9 isolated PHP suites, runtime PHP syntax checks and offline security regressions passed. A full forced Harrison local → Harrison dev push completed with 24 tables, 10,132 files, matching builds and HTTP 200 health. The final progress changes passed replay of all 117 saved reports and desktop/mobile rendering checks. No customer production sites were modified.

Install trickle.zip in WordPress → Plugins → Add Plugin. Both ZIP assets have the same contents.

Trickle 0.1.20

Changes

0.1.20 — 2026-11-03

• Install the exact local Trickle build on connected sites with one click, including unreleased and same-version changes.
• Validate uploaded builds, destination PHP syntax, permissions and checksums; verify the installed build before migrations.
• Preserve the controlling administrator session across database replacement and improve authentication/recovery diagnostics.
• Stop on failed database reads or corrupt checkpoints instead of continuing with incomplete state.
• Consolidate migration selection, size estimates and connection controls; use a focused transfer dialog and compact component progress.
• Keep estimated component sizes visible during preparation and group transfer activity by plugin, theme, table or media year.
• Show clear incoming upgrade/downgrade and activation states; log each unavailable source plugin by filename.
• Share navigation with Backups, bound browser request timeouts, and simplify job storage and database helpers.

Older installations need this build installed once to enable direct local-build copying. The published JSON updater remains available for released versions. Active transfers, remote Git checkouts and host filesystem restrictions prevent plugin replacement.

Validation: 20 direct-build and 26 legacy-updater checks, browser one-click installation with exact-build verification, JavaScript regressions, PHP checks, security checks and QA pull/recovery tests. No customer production sites were modified for this release.

Earlier releases

See the GitHub release history and the changelog in update.json.

Trickle 0.1.19

Fix verification loops and unusable cancellation on large migrations.

• Keep Cancel transfer enabled while the interface is busy.
• Store large job records in compressed, checksummed private files, with small database status/reference rows, to avoid MySQL packet limits.
• Reject failed checkpoint writes instead of restarting verification silently.
• Read committed transactional cursors independently of the options negative cache.
• Preserve current private records for recovery/backups and prune superseded versions safely.

Verified with a job exceeding 16 MB and 25,001 records, forced database-save failure, interruption/recovery regressions, and a real 24,670-file QA pull. The repeat selected zero media files across all 12 source groups. Successful media remains on the QA destination for manual testing.

Install 0.1.19 on both ends and reload the Trickle page. Existing inline job/backup records remain readable. Testing used QA sites only.

Trickle 0.1.18

Trickle 0.1.18

• Bound and checkpoint packaging, frame verification, import, preview, replacement and recovery.
• Persist cancellation outside worker locks, cap retries, and clean up abandoned source packages.
• Keep maintenance active until replacement/recovery finishes; resume partial rollback and roll back unreachable or HTTP 5xx frontend checks.
• Show sizes before a first pull: database total, individual plugins/themes and media by year. Scan on site selection; no sizing cron or activation scan.
• Reuse folder checksum caches across selections and reduce media-comparison requests.
• Improve 502 logs with request offsets, durations and last observed source activity.
• Enable write-scoped remote Trickle updates without a separate opt-in setting.

Install 0.1.18 on both sites before a new transfer. Recovery remains available for retained older jobs.

Database export keeps one consistent snapshot with a 45-second limit. Filesystem/hosting failures can still require host intervention. Keep independent backups and use a maintenance window for busy destinations.

Validation: scoped-key and replay/storage security tests; real QA pull/push, interrupted import/apply/recovery, cancellation and activation tests; native JSON-feed upgrades; 1 GiB pull, repeat pull and saved-backup restoration. No customer production sites were used.

Trickle 0.1.17

Migration workspace and monitoring redesign.

• Component rail, comparison workspace and persistent selection summary.
• Navy telemetry view with measured bytes, speed, elapsed time and available ETA.
• Stream verification pipeline with visible recent activity, retries and errors.
• Inline stage timers and consistent current-site placement; arrows follow push/pull direction.
• Responsive layouts and improved selection navigation.

Validation: 35 code checks and 17 native updater checks passed. Three local pulls verified plugin/theme updates, a repeat transfer skipping 241 unchanged files, and 613 database rows plus ten media files. Desktop/mobile checkpoint replays were inspected. Full browser interaction and new production transfers were not tested for this UI release.

Install the same version on both sites before migrating. Normal transfer methods, authentication, exclusions, backups and recovery behavior are unchanged.

Trickle 0.1.16

Trickle 0.1.16 improves migration monitoring and closes two security gaps.

• Authenticate dedicated Trickle entry points before isolating ordinary plugins. Unrelated login and administration requests keep their plugins loaded.
• Reject staging and backup paths exposed beneath the public document root, including configured public symlinks.
• Add Settings and Diagnostics tabs, editable migration presets, component search and filters, and explicit destination action labels.
• Merge transfer and verification into one view with interactive byte/speed charts, stage timers, Follow live, grouped activity and copyable error details.
• Collapse setup during transfers and summarize results, unchanged files, protected folders, health and the saved destination backup.

Install the same version on both sites before transferring. Refresh open Trickle tabs after updating. The recovery loader refreshes automatically on the first WordPress request after updating when file modifications are allowed. CLI installations can reactivate Trickle to refresh it immediately.

Validation: offline security and real WordPress authentication regressions; UI/workflow, chart, settings, preset and verification checks; desktop/mobile render checks; 17 native JSON-updater checks; packaged PHP/JavaScript syntax and secret scans. No production migration was run for this release.

Trickle 0.1.15

Trickle 0.1.15 makes the successful transfer methods the defaults: continuous resumable downloads for pulls and signed upload windows of at most 16 MiB for pushes. The dashboard labels this Automatic (recommended); CLI commands use it unless another transport is explicitly selected.

• Keep large pushes below common request-body limits and declare Content-Length for each upload window.
• Resume from acknowledged byte offsets after interruption. Complete snapshot and per-file checksums still gate staging and replacement.
• Preserve the explicit 512 KB chunk option, checksum skips, saved transfer choices and destination backups.
• Keep plugin-originated traffic on the normal Trickle transfer/health user agents, including when an AI operator starts the migration. Remove test overrides and add actual-header regression checks.

Validation: 12 upload-window checks, 20 streaming regressions, actual API/health header capture, JavaScript regressions and PHP/Python syntax checks. A normal-identity ~949 MB SiteDistrict push completed with 131 API requests and no request errors. All 9,878 source media files and 15,325 code files matched destination hashes. Forty-three checked database tables matched the pinned snapshot; differences in two scheduler tables were tied to logged background execution and cleanup. Frontend health passed, three destination backups were retained, and recovery was idle.

Install the same version on both sites. Source snapshot preparation and final staging remain foreground PHP operations; host time/storage limits still apply. Very restrictive hosts can use the 512 KB option.