Repository navigation
v0.24.0 — rebrand Settings page menu + h1 + body strings
What's new in v0.24.0 — Settings page rebrand
Extend whitelabel reach to the connector's own Settings page. v0.21.0–v0.23.0 covered the plugins list, plugin row meta, and login + adminbar surfaces — but Settings → DeckWP Connect in the wp-admin sidebar, the page <h1>, and every "This site is paired with DeckWP" body string still leaked the upstream brand.
The customer's wp-admin sidebar was leaking DeckWP even with a fully configured rebrand.
What gets rebranded now
- Settings submenu label (sidebar)
- Browser tab title
- Settings page
<h1> - "This site is paired with
<brand>" (paired state) - "Disconnect this site from
<brand>?" (confirm dialog) - "
<brand>revoked this connection." (revoke banner) - "Disconnected from
<brand>." (post-disconnect success) - "Pair this WordPress site with your
<brand>dashboard…" (unpaired state) - "Leave the default unless you are using a staging or self-hosted
<brand>install." (Dashboard URL hint) - "You do not have permission to manage
<brand>." (permission error)
How it works
No new toggle. The operator's existing Plugin Name field on the dashboard /sites/{site}/whitelabel page IS the rebrand source. The connector now reads the same plugins[<basename>].name value Whitelabel\Branding already uses for the plugins-list filter, and applies it to the Settings page render too.
Falls back to "DeckWP Connect" when no rebrand is configured. Strings remain translatable — each uses a sprintf template with a /* translators */ comment.
Known limitations (not yet rebranded)
- WP-Cron schedule
displaynames ('DeckWP Connect heartbeat','DeckWP Connect scan') inHeartbeat\SchedulerandScan\Schedulerstill hardcode the upstream brand. These are only visible to users with WP-Cron debug plugins (WP Crontrol etc.) — low-visibility leak, deferred until someone asks.
Wire contract
No change. Render-only update reading the existing option shape from v0.21.0.
Upgrading: drop in deckwp-connect.zip or self-update via the DeckWP dashboard. No DB migration. Existing whitelabel configs work unchanged — the new rebrand applies automatically once a Plugin Name is set in the dashboard's whitelabel form.