Skip to content

What Changed

This page summarizes customer-visible plugin improvements rather than every internal implementation change. Use it to get a quick sense of what has shifted between recent versions when you are comparing behavior across two installs, or when a customer reports a change after an update.

For the canonical list of every change (including internal refactors, dependency bumps, and test fixes) refer to the plugin repository’s changelog. This page is curated rather than exhaustive.

VersionDateHighlights
2.4.12024-12-21Hotfix for an edge case in reconnect after host migration. Reconnect now correctly clears stale heartbeat state instead of carrying it forward from the previous host.
2.4.02024-12-10Improved reconnect reliability after credential rotation. Clearer wording on the Test Connection failure surface. Hardening around outbound calls when an aggressive .htaccess rule was rewriting cURL responses.
2.3.02024-09-22Custom SMTP UX cleanup. Better defaults for the connection-choice screen on first load. Minor accessibility fixes on the settings page.
2.2.02024-07-30Backup exclusions: default list expanded to cover the most common operational log tables. Reviewed-but-not-included list documented in Backup Exclusions.
2.1.02024-05-14Error Monitoring toggle moved to the top of the settings page. 1-Click Access status surfaced on the connection summary.
2.0.02024-02-05Modern connection flow replaces the legacy “paste workspace token” path as the default. Token-based connection still works for now but is deprecated and will be removed in a future major version.
1.9.02023-11-18WordPress 6.4 compatibility. PHP 8.2 compatibility. Initial groundwork for the modern connection flow shipped in 2.0.0.

Across the versions in the table above, the customer-visible direction has been:

  • Better compatibility with current WordPress and PHP versions. The plugin tracks WordPress and PHP releases closely so you can update WordPress core without worrying about the TMXIO plugin breaking.
  • Improved connection and reconnect reliability. The connection flow has been simplified and the reconnect path is more forgiving of state mismatches that used to require a manual support touch.
  • Ongoing fixes around backup, restore, and cache-related operations. Most of the back-end work in 2024 went into making backups more resilient when sites had unusual table layouts or aggressive object caches.
  • Continued polish to customer-visible settings and integration flows. Default settings have moved toward “do the safe thing automatically” rather than asking the customer to choose every time.

If your team is comparing behavior across plugin updates, use this page as a high-level summary and confirm the current installed version in WordPress before troubleshooting a change in behavior. The version shown in Plugins in WordPress admin is authoritative — the table above is illustrative.

If a customer reports that a behavior changed after an update and the change is not described here, do not assume the behavior is intentional. Capture the version they updated from and to, and treat the report as a regression candidate until proven otherwise.

The plugin follows a familiar major.minor.patch pattern:

  • A major bump (2.0.0) indicates a customer-visible flow change, like the move from token-based connection to the modern flow. Read the corresponding row carefully before rolling the new major version across many sites.
  • A minor bump (2.3.0) introduces new customer-visible behavior or settings, but does not change existing flows. Safe to roll across most fleets without per-site review.
  • A patch bump (2.4.1) is a fix-only release. Always safe to update.