WP/email-toolkit
Watch
1
0
Fork
You've already forked email-toolkit
 0
Code Issues Pull requests Projects Releases 35 Packages Wiki Activity Actions
35 releases 35 tags
  • v0.8.4 84780637c8

    v0.8.4 Stable

    Robin released this 2026-09-11 12:27:40 +02:00 | 55 commits to main since this release

    Sign your newsletters

    Whoever writes a newsletter can now put their name at the bottom of it.

    Each person sets their signature once, on their own WordPress profile — and it takes the signature they already have. Paste the block your email client gives you, tables and logo and phone numbers included: it arrives intact. A preview sits right under the field, drawn at the true width of an email, so you see exactly what recipients will get, and a signature that is too wide shows you before it shows them.

    Then, on any newsletter: tick Sign this newsletter. Your name appears beside the box. Several people share the newsletters? Pick who signs — yourself, or the colleague the message is really from — and, if you may edit their profile, jump straight to their signature from there.

    The signature sits between your content and the unsubscribe footer, and it is there in the preview and in the test send, not just in the real one.

    Emails you send are part of your privacy tools

    When someone asks for their data, or asks you to delete it, the emails this site sent to their address are now included — date, subject, sender and an excerpt of each message — alongside their subscription, their measurements and the messages they sent you through a contact form. Erasing removes those copies and the files saved with them. That was the last corner of the plugin outside the privacy toolkit; the suggested privacy-policy text gained the matching paragraph, with your retention period when you have set one.

    Requires PHP 8.2+ and WordPress 6.8+.

    Downloads
  • v0.8.3 73d4b6fcef

    v0.8.3 Stable

    Robin released this 2026-09-10 15:25:00 +02:00 | 56 commits to main since this release

    "A mistake on this page? Tell us"

    Put that link on your articles and the message that arrives now tells you which page it was about — automatically. No field to configure, no shortcode, nothing to remember.

    The page the visitor came from, everywhere it helps

    • In the notification email, one discreet line under the message: The visitor came from → Installation guide. Click it, you are on the page.
    • In the subject line, if you want it there: the new {source_page} token turns your subject into [Contact] Report — Installation guide, so you know what it is about from your mailbox list, without opening anything.
    • In the inbox, a Came from line at the top of every message, plus the page carrying the form, the browser language, and the visitor's account if they were signed in.

    When the browser doesn't say where the visitor came from — a direct visit, a bookmark, a site that withholds it — the line says so plainly instead of disappearing, so a blank never looks like a bug.

    A field the visitor can see and correct

    Add the new Source page field to a form and the visitor sees the page too, already filled in, and can correct it if they were reporting something else. The new Report a problem starter template gives you the whole form in one click: the page concerned, what is wrong, and an optional email if they would like an answer.

    Your emails read better on a phone

    The action buttons under a contact-form notification (Reply, View in admin, Spam, Trash) used to run off the side of the message on a narrow screen. They now wrap neatly, and every email the plugin writes itself is laid out for phone screens instead of being shrunk to fit.

    Contact forms join the privacy tools

    Messages sent through your forms are now part of Export / Erase personal data (WordPress's own tools and the plugin's privacy screen), and the suggested privacy-policy text gained a Contact forms paragraph naming exactly what is kept, and for how long.

    Requires PHP 8.2+ and WordPress 6.8+.

    Downloads
  • v0.8.2 a529e5092e

    v0.8.2 Stable

    Robin released this 2026-09-09 01:56:50 +02:00 | 57 commits to main since this release

    Consent: WordPress users are in the picture

    The Privacy page's consent browser now lists the WordPress users who receive newsletters alongside subscribers: who never answered, who said yes, who said no, with the same search, a WordPress users source filter, and the same bulk recording with a justification kept in the consent log.

    Their consent was already honoured when sending and measuring; only the page left them out, so a consent collected elsewhere (a checkbox on your shop, for example) could not be recorded for them in bulk.

    Requires PHP 8.2+ and WordPress 6.8+.

    Downloads
  • v0.8.1 de304e010f

    v0.8.1 Stable

    Robin released this 2026-09-08 14:40:54 +02:00 | 59 commits to main since this release

    Your own subscriber fields

    A club, a company, a member number, a level: custom fields let you store what matters to you about each subscriber, and bring over what your previous newsletter plugin held.

    Custom fields

    • Define them in one place: Subscribers → the Custom fields button. Text, number, date or a choice from a list, up to 30 fields, saved as you type.
    • They are everywhere a subscriber is: a column of the subscribers table (pick it in the columns picker, sort on it, search on it), a field of the subscriber card and of the WordPress-user card, a column the CSV import accepts (name the column after the field), a target for your signup-form fields through Maps to, and a token for your emails: write {{club}} in a newsletter, a confirmation or a reminder and the value is inserted.
    • Values are part of a person's data export and erased with it.

    Import from the Newsletter plugin, including its custom fields

    The import now lists the custom fields of the Newsletter plugin, with how many subscribers filled each, and brings them along: the matching fields are created here and the values copied. A value already set here is never overwritten, whatever you chose for existing addresses, so running the import again after editing subscribers is safe.

    Requires PHP 8.2+ and WordPress 6.8+.

    Downloads
  • v0.8.0 9df580d25b

    v0.8.0 Stable

    Robin released this 2026-09-08 14:15:18 +02:00 | 62 commits to main since this release

    Send big, land in the inbox, and stay on the right side of the law

    Two milestones ship together in 0.8.0: deliverability and privacy. Plus a fix for a bug a client hit on the subscribers page.

    Deliverability

    • A site-wide sending limit, on by default at 1000 emails per hour. Whatever the identity or the recipient domain, the site never exceeds it — set it to what your mail provider allows, with a margin. The Deliverability page explains how sends flow (batches, browser loop versus cron, sliding windows) and shows whether cron is running.
    • Pace per recipient domain. Big mailbox providers throttle senders who arrive too fast. The plugin ships conservative ceilings for about 120 of them worldwide (Orange, Free, Laposte, Gmail, Outlook, Yahoo, GMX, Libero, Telenet and many more), switchable one by one, with your own rows on top and a default for everyone else. When a domain hits its ceiling, the newsletter card says so and the next batch waits its turn.
    • A limit per SMTP identity, on the identity card: "this plan allows 2000 an hour". Every email through the identity counts, order confirmations included, and newsletters stay under it. Every limit is explicit: a switch says whether one applies, and 0 means nothing goes out.
    • Bounces handled for you. Switch on the identity card to have the plugin read that mailbox's non-delivery reports every 5 minutes over IMAP, with the same credentials as SMTP, or push events to a webhook from your own script. Hard bounces mark the subscriber bounced, repeated soft bounces too, spam complaints unsubscribe. Every report lands in a bounce log. The mailbox is otherwise never touched: an ordinary email stays unread, and only standard reports are ever deleted, only if you ask.
    • A suppression list: addresses that bounced or complained are never mailed again, whatever the list. Searchable, with manual add and "allow again".
    • Sent copies in your mailbox (option on the identity card, off by default): emails sent through an identity are filed into its Sent folder, like a mail client would.
    • Deliverability at a glance: 30-day bounce and complaint rates against the thresholds providers apply, SPF / DKIM / DMARC of every sender domain, the recipient domains that reject the most, and how the last newsletters went.
    • Faster sends: parallel senders while the tab is open, and cron keeps sending for 50 seconds per run when it is closed.

    Privacy

    • Open and click measurement based on consent. New sites measure only the recipients who said yes; the others get a pixel that records the day the email was last displayed and nothing else. Consent is asked by a new form field, on the preferences page and in the WordPress profile, and travels with CSV imports. Withdrawing deletes what was measured. Sites that already measured keep their setting, with a notice.
    • A consent log: every subscription, unsubscribe and measurement choice, with the wording shown, the source and a truncated IP. Searchable, with its own retention.
    • A Privacy page for administrators: who consented to what, a subscribers-by-consent browser to record the consent status of an imported base in bulk (with a justification kept in the log), one person's data to look up, download or erase, every retention setting in one place, and a privacy-policy text generated from your settings. Export and erasure also plug into WordPress's own privacy tools.
    • Permissions: from the dashboard, give any role access to Newsletters or to the contact-form Inbox without making them administrators. They see only what they were granted.

    Fixed

    • Subscriber modal: the first change of a field was lost. Typing a name, a first name or a phone number and leaving the field did nothing the first time, with no message. Every change is now saved, a ✓ Saved badge shows in the modal header, and the subscribers list updates as you edit: names, and the lists you tick. Reported by a client, thank you.

    Requires PHP 8.2+ and WordPress 6.8+. Pre-1.0: the database schema changes between minor versions; updating is automatic.

    Downloads
  • v0.6.8 d74c6d44cf

    v0.6.8 Stable

    Robin released this 2026-09-07 15:14:32 +02:00 | 71 commits to main since this release

    Bring your subscribers over from the Newsletter plugin — and a straight answer about shared files

    Import from the Newsletter plugin

    The Newsletters → Import page now lists your three ways in: paste addresses, upload a CSV, and — for the many sites arriving from Satollo's Newsletter plugin — import straight from it. When its subscriber table is present, the card shows how many subscribers and lists it holds; the import screen then details what it holds — confirmed, not confirmed, unsubscribed, bounced — and every list with its size and its public/private flag. For each list, you choose where it goes here: created with the same name and visibility (the default), added to one of your existing lists, or skipped.

    • Addresses already present are merged, never duplicated; you choose whether to keep them as they are or refresh their name and profile.
    • Unsubscribed and bounced addresses can come along as unsubscribed, so they are never mailed again; never-confirmed ones as pending.
    • The original signup date, first and last name, gender, language and country are kept.
    • Runs in batches with a progress line, and can be run again safely: a second pass adds nothing.
    • Nothing is written to the other plugin.

    Tested on a live site: 679 subscribers and 22 lists in one go.

    Shared files: a clear answer when you trash or delete a newsletter

    Files attached to a sent newsletter stay online for the readers. What happens to them when you remove the newsletter used to be one vague sentence; it is now a real choice, asked when it matters:

    • Trash: keep the files online (default) or take them offline right away. The emails already delivered are never touched — only the links inside them.
    • Delete permanently: delete the files now, or keep them online for a delay (the default delay is a setting, 90 days out of the box, or "until you remove them").
    • Files kept after their newsletter is gone are listed in the Shared files settings with their expiry, and can be removed by hand at any time.

    Small things

    • List member counts no longer lag a few minutes behind an import or a manual add.
    • The Newsletter settings modal had the wrong title in French.
    Downloads
  • v0.6.7 9cb38b88cc

    v0.6.7 Stable

    Robin released this 2026-09-06 20:57:23 +02:00 | 76 commits to main since this release

    Answer your contact forms from the site — and dress every email your site sends

    Two things land in 0.6.7: conversations on contact-form submissions, and an email design shared by everything the toolkit sends.

    Reply from the inbox, the visitor answers from your page

    Open a submission in the inbox and write your answer in the familiar WordPress editor (bold, links, lists). The visitor receives it by email, sent from the form's own address, with a button that brings them back to the very page they wrote from — where the form has turned into the conversation. They read the exchange there and reply without any account; you get their reply in the inbox and by email, with the same Reply / View / Spam / Trash buttons as the first notification.

    • Every conversation email is as complete as the first one: the new message, the earlier exchanges quoted, the original submission.
    • The editor tells you what the visitor will see: which address sends, and the name that signs.
    • Line breaks, links and formatting survive; anything else is stripped for safety.

    One design for every email

    A new Email design button on the dashboard: logo, colours (with your theme's palette at hand), font, alignment, signature line — with a live preview. It applies by default to every email the toolkit sends: contact-form notifications and conversations, newsletters, confirmation and reminder emails, even the test email. Pick a dark message background and text, rules and secondary text follow; the text on your accent colour flips to black or white on its own, and secondary text stays readable in sunlight.

    Each newsletter can keep the default or customise it from its card — a switch, your changes, and a back to the default button.

    An inbox that behaves

    • Trash instead of deletion: every "delete" — row, bulk, email button — now moves the submission to a trash you can restore from; the trash empties itself after a delay you set (30 days by default).
    • Unread: new submissions and unanswered visitor replies are bold in the inbox, counted on the dashboard, and shown as a bubble on a new Inbox entry in the Email Toolkit menu.
    • Where is this form used? Each form card lists the pages that carry it, with a link to open or edit them.

    Small things

    • The newsletter shared-files settings and the Newsletter settings modal had been squeezed to 720 px by a stray rule — they breathe again.
    • Buttons in emails are centred the way every mail client understands.
    Downloads
  • v0.6.6 f584911969

    v0.6.6 Stable

    Robin released this 2026-09-06 10:19:05 +02:00 | 93 commits to main since this release

    Shared files: you decide what happens when a newsletter is deleted

    0.6.5 let a newsletter share files through download buttons. This release closes the one question it left open: what happens to those files when the newsletter itself goes away?

    Deleting a newsletter now asks

    Moving a newsletter to the trash changes nothing — its download buttons keep working and you can restore it. When you delete it permanently and it still hosts files, the confirmation now says so ("3 shared files (12 MB) are attached to this newsletter") and offers two choices:

    • Delete the files too — the default. The buttons in the emails already sent stop working, and a recipient who clicks one lands on a short, clear "no longer available" page rather than a broken link.
    • Keep the files online — the buttons keep working. The files simply move to a list in the Newsletter settings.

    Emptying the trash also tells you how many files it is about to remove.

    A home for kept files

    Newsletter settings → Shared files now shows how many files are hosted on your site and how much disk they use, followed by every file kept after its newsletter was deleted: name, size, number of downloads, which newsletter it came from and when. Each one can be deleted individually, or all at once.

    The automatic expiry delay, if you use one, applies to kept files too — counted from the day the newsletter was deleted — so nothing lingers forever by accident.

    Small things

    • The Plugin data page now counts hosted files alongside subscribers.
    • A file removed with its newsletter now shows recipients the same "no longer available" page as an expired file, instead of an "invalid link" error.
    Downloads
  • v0.6.5 de6eeeb797

    v0.6.5 Stable

    Robin released this 2026-09-05 20:18:54 +02:00 | 94 commits to main since this release

    Share files with your newsletter — without attaching them

    A newsletter can now carry documents: a PDF programme, a price list, a registration form, photos. 0.6.5 adds a "Files to share" panel to the newsletter editor and to each newsletter card.

    Add a file, done

    Open the newsletter, click Add files in the sidebar, pick your documents. Every file becomes a download button at the end of the email. Nothing to insert in the content, nothing to configure. Preview and test sends show exactly what recipients get.

    Why the plugin never sends a real attachment

    Sending the same 4 MB PDF to 2,000 people means 8 GB leaving your server, a worse spam score on every message, full mailboxes on the other side — and no way to fix a typo once it's gone. So the file stays hosted on your site and the email carries a button instead:

    • the email stays light and lands in the inbox, not in spam;
    • every download is counted, per file and per recipient, like any other click;
    • you can replace or remove a file, even after sending;
    • files stay available as long as the newsletter exists — or, if you prefer, expire automatically after a number of days you choose in the Newsletter settings. A recipient who clicks an expired button gets a short, clear "no longer available" page instead of a broken link.

    Duplicating a newsletter duplicates its files; deleting it deletes them. Download links are signed and unguessable, and the files are not reachable directly on the server.

    Small things

    • A New newsletter button on the Newsletters dashboard — it was only on the list view.
    • The envelope icon on the Test and Send now buttons now sits on the same line as the text.
    Downloads
  • v0.6.4 c7bb058a5d

    v0.6.4 Stable

    Robin released this 2026-08-03 03:14:11 +02:00 | 101 commits to main since this release

    Design your forms, then reuse that design everywhere

    0.6.3 gave every contact and newsletter signup form a click-driven style editor. 0.6.4 turns it into a design system.

    Save a look, reuse it, make it the default

    Build a form you like, hit + next to any dropdown, and give it a name. That preset now appears on every form — contact forms and newsletter signup forms share one library, so a colour scheme you saved on one is available on the other.

    Set a preset as your default and it applies to every form that hasn't overridden that setting. Changing your brand colour becomes one edit instead of twenty. A new Styles button in the toolbar (and inside Defaults) opens a manager where you can rename, delete, or promote any preset.

    The Defaults screen now hosts the full editor too — it used to expose three lonely text fields out of twenty available settings.

    Shadows, effects and a lot more control

    • Shadows are their own thing now — form, fields and button, each None → Strong, plus an accent glow. Field and button shadows previously couldn't be changed at all.
    • Effects covers interaction: focused field, field hover, button hover, and an always-on form ambience — Glow, Breathe, Aurora, Rainbow, RGB spin, Plasma, Ember. Each with its own glow size and speed, from Frantic to Glacial.
    • Padding for fields and buttons, and every length is now set with a number box and a unit dropdown — no more guessing whether 8 px was valid (it wasn't).
    • Controls appear only when they're relevant, so the panel stays readable rather than showing a wall of settings that do nothing.

    Four new colour schemes (Midnight, Terminal, Sand, Mint) and nine new presets, including Neon night, Paper, Spa, Bubblegum and Terminal.

    Forms that celebrate

    When a message is sent, the form is replaced by the success message — and you choose how it arrives: a letter flying off, a rocket launch with smoke, confetti with real physics, or a fireworks display with multiple shells. Pick a speed, press play to preview it right in the editor, or turn it off entirely.

    Everything honours prefers-reduced-motion: visitors who ask for less motion keep the colour and the meaning, and lose only the movement.

    Accessibility and correctness

    • Every built-in colour scheme now meets WCAG AA contrast. Some helper and button text sat as low as 2.5:1 and was genuinely hard to read.
    • Fonts and label emphasis actually apply. Body font, label font and label emphasis were silently discarded when saved — they looked right in the preview and reverted on reload.
    • A blocked anti-spam check now says so. If a cookie-consent banner or blocker prevents the captcha from loading, visitors are told immediately instead of having their message rejected after they've written it.
    • Buttons no longer shift under your cursor on hover, which made them harder to click.

    Under the hood

    Releases and updates now come from git.lrob.net.

    Upgrading: no action needed, and no existing form changes appearance. Everything new is opt-in.

    Downloads