SteerWP Console

2.48.1

• Fixed: when a client site disconnects on its own side (or its credentials change), the Console now detects the rejection on the next status check, marks the site disconnected, and shows the “Connect this site” card so it can be re-paired. Previously the site stayed “connected” forever and re-pairing was impossible without deleting it.
• Housekeeping: the last legacy admin-notice query arguments were renamed to the steerwp_ prefix.

2.48.0

First WordPress.org release. Consolidated notes since 2.21.4:

• New: Client-site area setting (Settings → Branding). Choose whether SteerWP Connector stays hidden on client sites, shows the documents you share, or shows a full branded overview. Hidden by default.
• New: Comments command centre — scan pending comments across every connected site, with a spam scorer built from real-world spam patterns, asynchronous rescans and a one-click “mark all suspects as spam” purge, both with live progress bars.
• New: MainWP migration wizard — import clients, groups and sites from an existing MainWP dashboard.
• New: Pair existing sites from their own page; connection dashboard widget showing pairing progress across the fleet.
• New: Client merging (combine duplicate client records; sites, contacts and history move with them).
• New: Dashboard widgets can be shown or hidden per user; widgets are bounded so a slow site never slows the dashboard.
• New: Sidebar navigation with keyboard shortcuts; built-in knowledge base with searchable how-to articles.
• New: Freemius-based licensing for paid add-ons — one bundle key unlocks every add-on. Opt-in is optional and nothing is sent without it.
• Improved: All scripts and styles load through the WordPress enqueue APIs; output escaping and input sanitisation reviewed throughout; all option and transient names use the steerwp_ prefix; database identifiers are whitelisted and prepared.
• Improved: Top-level menu placed below the core WordPress items.
• Improved: Client Documents tab explains where uploaded files appear on the client’s site.
• Fixed: Comment counts refresh after a spam purge; display pagination on large comment queues; branding colour on the proposal signing page; login screen branding.
• Removed: The remote WP-CLI runner (not permitted for WordPress.org-hosted plugins). Services custom-CSS embedding (returns in a compliant form later).

2.21.4

• Fixed: sites.child_version was written exactly once, when a site was first paired, and never refreshed afterwards. The moment an agency updated the SteerWP Connector plugin on a site, the Console’s record of its version went permanently stale, and nothing would ever correct it short of re-pairing. The “Connector plugin” row on the site detail page has been showing a stale value ever since, and add-ons that gate on the Client version were rejecting sites that had already been updated.
• The Child has always reported its version in system_info; the Console was discarding it. Sync now refreshes the column on every run.
• Fixed: child_version was also missing from the allowlist in update_cached_data(), so any attempt to write it there was silently dropped — the update ran, reported success, and wrote nothing.

2.21.3

• Maintenance mode copy is now honest. The Manage tab claimed that “logged-in admins still see the real site” — that was false for SteerWP Connector 1.22 and earlier, which used WordPress’s .maintenance file. That file is checked before authentication, so it locked the agency out too, and WordPress stops honouring it after ten minutes, silently bringing the site back online while SteerWP still showed it as down.
• Sites running Client 1.23.0+ get the real behaviour and accurate copy. Sites on an older Client now see an explicit warning explaining both defects, rather than a promise the Client cannot keep.
• Adds support for the SteerWP Maintenance Pro add-on.

2.21.2

• Monitoring tab rebuilt with an explicit main + rail layout. The first pass reused the old card grid, which could not balance cards of very different heights: Security overflowed while a third column sat nearly empty, and Cron and Comments were pushed below the fold.
• Fixed: the Backups, Cron and Comments cards render no card wrapper of their own — the old code always supplied one at the call site. Calling them directly left the backup form floating on the page with no heading and no chrome. Each is now properly wrapped.
• The create-backup form no longer appears on Monitoring, which is a read-only tab. The backup list stays; the action lives on Manage.
• Security findings now lead with the findings. The explanation of what the scan checks was pushing the counts and the actual critical issue four elements down the card; it is now a collapsed hint.
• Fixed: the Overview uptime metric read a uptime_pct key that does not exist (the real keys are uptime_pct_24h / uptime_pct_7d), so it silently rendered an em-dash on every site.
• Fixed: Overview read client_version from the site row; the column is child_version. It silently rendered an em-dash.
• Fixed: the Monitoring tab badge and the Overview “Needs attention” list filtered health signals on severities of crit, risk and critical. Only crit, warn and info are ever emitted — so two of those were dead branches, and warn was omitted entirely, silently undercounting every warning on the site.

2.21.1

• Fixed: row action dropdowns were being clipped by their own table and could not be seen or clicked. The table carried overflow: hidden — added only so its border-radius would clip the corners of the striped rows — but that also clipped any menu opened from inside a cell. This affected every table with a row menu: broken links, clients, plugins, themes and users. Corners are now rounded on the corner cells directly, so the visual is unchanged and the menus can escape the table.
• Row menus now close when another is opened, when you click outside them, or when you press Escape. Previously nothing ever closed them, so two could sit open at once, overlapping.