v1.11.1
2026-11-20- Security: Heatmap capture mode can no longer be triggered through a crafted front-end link. The capture script is enqueued only for a logged-in administrator with a valid nonce, and it no longer takes its asset URL from the page address (cross-site scripting reported by Patchstack).
- Fix: Storage: "Reclaim this space now" gives honest figures. A table with no rows to reclaim says so instead of promising space that cannot come back, the estimate uses the space the server can really free, and the table list shows why a table is skipped.
- Fix: Storage: the progress of a move (data folder and database) advances by itself. The bar, the figures and the step no longer wait for a page reload.
- Fix: Storage: "Bring my data back" is no longer blocked by the tables an earlier copy left behind. The old tables are replaced through staging tables, with a clear choice on screen, and the WP-CLI command accepts –replace-old.
- Enhancement: Storage screen: the space reclaim card is clearer — the figures, the table list with its state, a live progress bar and a folded rebuild log.
- Fix: Uninstalling the plugin now removes everything it created (the storage options and the background tasks left behind), and the wordpress.org plugin page is no longer cut short.
- Fix: Storage: copying your data to a separate database now survives live traffic. A refused connection is retried, the copy keeps verifying until the tables stop moving, a chunk that failed goes back to catch-up, and the Storage screen shows the real state of the copy instead of a progress bar that looks stuck.
- Fix: Storage: a site that uses a separate database no longer leaks connections to it. Handles are reused, the number of open connections is capped, and the connection test closes everything it opens, so the second database no longer answers "Too many connections".
- Enhancement: Background mode: the table migration, the data folder move and the size cap now share one work budget, so a copy running in the background keeps the site fast.
- Enhancement: Smaller footprint: redundant pageview indexes are dropped and the page URL index is narrowed; the Storage screen gives an honest folder size estimate and copy time, and retention and A/B cleanup wait while a database copy runs.
- Fix: The wordpress.org figures strip always shows its four numbers.
- Fix: Advertising click IDs in page addresses (fbclid, gclid, msclkid, ttclid, twclid, yclid and similar) are replaced by "1" before anything is stored, so the value that identifies a single ad click is never kept. Visits from ads are still classified as before.
- Fix: The 15-minute heatmap sync check no longer holds up the other scheduled tasks of the site: it stops at its time budget and never runs twice at the same time.
- Fix: Data retention deletes old rows in batches of 1,000, and never runs OPTIMIZE TABLE on its own on a table larger than 256 MB; the Storage log says which table was skipped.
- Fix: On sites with plain permalinks (addresses like ?p=12 or ?page_id=2), every page opened now counts as a page view. Before, a visit of several pages was stored as one page view, so page views, bounce rate and top pages were wrong.
- Fix: The Cleanup History log keeps the latest lines of each task type: a long database copy no longer pushes out the retention lines.
- Fix: The one-off conversion of old scroll and mouse-move rows into per-visit counters is crash-safe: it takes a lock so two rounds never overlap, works in small chunks, and saves its progress with the counters, so a crash or a timeout resumes where it stopped without counting a visit twice.
- Enhancement: Storage screen: the page no longer reloads itself. Each block updates on its own, the message stays inside the block it belongs to, the progress advances by itself, and each block has one main button (one button starts the whole move, data folder and database).
- Enhancement: Storage: the disk space freed by a purge is given back to the server. One table is rebuilt per night, only if the server has enough free space for it, with a "Reclaim this space now" button on the Storage screen and a line in the Cleanup History log saying which table was rebuilt and how much space came back.
- Fix: The automatic daily clean-up could delete recent page views. It now only removes data older than the retention period you set.