Summary
PressedMail 1.3.0 is about the composer being one thing instead of several, the
screen telling you the truth, and a brand panel that finally shows what it does.
Signatures and auto-replies now open in the same editor as the
message you are writing. Before, each had its own, so a style that worked in one
did not exist in another. They now share the same editing controls.
Adding a signature no longer rewrites your message. It used to be spliced into
the HTML, which dropped the colour and size of every block it passed, and on a
reply it landed below the text you had quoted rather than above it. It is placed
in the document now, at a position rather than through a string, so everything
around it keeps what it had.
The message composer also offers Rich Text alongside Markdown and Plain Text.
Rich Text and Markdown use the same document, so switching between them keeps
blocks and formatting. With email content caching on, a saved draft can keep
that document in the site's database.
The Branding & Appearance panel, where an Ultimate administrator sets the
workspace's name, logos and colours, was showing numbers that belonged to no
theme in particular. Choosing a base theme now fills the guided colours with
that theme's own values, the panel's example workspace follows every keystroke,
and the colour fields accept transparency.
Underneath, inputs, checkboxes and focus outlines become one system across every
panel and both themes, pop-out panes centre in the PressedMail window instead
of opening off the bottom-right. Administrator API access works again: four
settings endpoints were refusing every request that authenticated with an
Application Password.
Added
- The message composer, signature editor and auto-reply editor now share
rich-text formatting controls. Plain text remains an option in the message
composer.
- The message composer offers Markdown, Rich Text and Plain Text. Markdown and
Rich Text share one document, so switching views keeps blocks and formatting.
- One signature can be assigned to several email accounts at once.
- A Run now action on the Background tasks card, available to administrators,
which runs one scheduled-work pass on demand so the card's own evidence
updates.
- Choosing a base theme fills the guided colours with that theme's own values.
- Guided colours accept transparency with an eight-digit hex value.
- Each colour field's swatch opens a colour picker with hue, alpha and an
eyedropper.
- Administrators choose which themes their users may select, with at least one
always available.
- Logos and the square mark are chosen from the WordPress media library.
Changed
- The composer canvas follows the app's light or dark theme while you write,
and returns to the fixed email canvas in Preview.
- The Branding & Appearance palette sits beside the workspace example it
drives, and the example covers light and dark on its own switch.
- Dropdowns in the branding panel open a themed list instead of the browser's
own.
- Inputs, text areas, selects, checkboxes and focus outlines now come from one
set of tokens.
- The signature preference defaults to placing a signature above the quoted
text.
Fixed
- Adding a signature no longer strips the colour, size and formatting of the
message around it.
- A signature is inserted between what you wrote and the text you quoted,
instead of below the quote.
- Administrator REST endpoints accept core Application Password logins.
- The branding panel's own example controls painted the workspace's default
colours while claiming to show the brand palette, which made one of them
unreadable. The example now paints from the palette being edited.
- The branding panel's dropdown menus opened with the browser's light
background in dark mode.
Upgrade Notes
- Branding settings saved by an earlier version keep every value they had. The
one new field, the list of themes users may select, arrives carrying every
theme the workspace already offered, so no user loses a choice on upgrade.
- A signature's account binding moves from the signature row to its own table,
so one signature can serve several accounts. A failure holds the version back
and retries rather than losing the binding.
