# 1.0.28

- Link: https://blog.curbsoftware.com/changelog/v1-0-28/
- Published: 2026-09-10T22:00:00+00:00
- Author: curbsoftware

## Summary

A corrective release. 1.0.27 shipped a schema check that no MariaDB server could

ever satisfy, which left every Pro site on MariaDB re-running its whole upgradeon
every page load. That is fixed here, along with the Activity panel showingmailboxes
you had already deleted.

Install this over 1.0.27. Nothing needs to be done by hand: the site repairs
itself
on the next request.

## Fixed

 * Pro: upgrades finish again on MariaDB. 1.0.27 compared a stored column default

against the one it expected, and MariaDB prints a binary column’s default as a
hex
string, so one calendar column never looked right no matter how many timesit was
repaired. The upgrade recorded a failure, refused to mark itself done,and started
over on the next request, front-end page loads included. Sites onMySQL and all Free
sites were unaffected.

 * The Activity panel no longer lists mailboxes you have removed. Its rows only

ever recorded the WordPress user, never the mail account, so deleting an
account
could not take its history with it and the old address kept showing upnext to a 
folder name. Existing rows for deleted accounts are cleared onupgrade.

 * Deleting a mailbox now also cancels its queued snooze retries.
 * A sync job queued before a mailbox was switched off no longer runs afterwards.
 * Two IDLE endpoints trusted the account id in the request without checking who

owned it. One user could end another user’s IDLE session on the same site.

 * Background sync no longer records a request’s IP address and browser on the

activity it writes. When the queue is drained inline it borrows whichever
visitor’s
request happens to arrive, so those entries were being stamped witha bystander’s
details instead of the mailbox owner’s.

 * Bulk actions no longer write activity rows with no owner, which nothing could

read and no cleanup could reach.

## Upgrade Notes

 * No manual step. A site stuck on 1.0.27 clears its recorded upgrade failure and

advances on the next request.

 * 1.0.27 was withdrawn from the update catalog. Sites on 1.0.26 were never

affected and can move straight to 1.0.28.
