EP Newsletter
EP Newsletter is a full newsletter system for PageMotor. Subscribers and lists, campaign composition with draft/test/send, batch delivery with configurable pace, open and click tracking, autoresponder sequences triggered by subscription, and automated content digests. Delivery routes through EP Email so SMTP, from-addresses, and deliverability are managed in one place.
Published by ElmsPark Studio.
Overview
Section titled “Overview”Core features:
- Subscriber management. Add, import from CSV, export, track source (which form they came from).
- Lists. Named mailing lists with segmentation.
- Campaigns. Compose, preview, test-send, schedule, send.
- Batch delivery with configurable batch size and delay between batches, so you don’t overwhelm SMTP providers.
- Open tracking via invisible pixel; click tracking via link rewriting.
- Double opt-in with confirmation and welcome emails.
- Autoresponders — timed sequences of emails triggered when someone subscribes.
- Automated digests — daily, weekly, or monthly digests of new content on your site.
- Delivery extensions. Swap in Mailgun (the recommended provider) or a custom driver.
- Webhook handling for bounces and complaints from delivery services.
- PM API control (new in 1.2.0) — manage lists, subscribers, campaigns and autoresponders over the PM API and MCP, no direct database access.
- Unified send log (new in 1.2.0) — every send recorded in one table with a type/source column for deliverability diagnosis.
Requirements
Section titled “Requirements”- PageMotor 0.8.2b or later
- EP Email (required)
- EP Suite base class
Optional:
- EP Newsletter Mailgun for Mailgun delivery (the recommended provider).
- EP GDPR for consent logging on subscription.
- EP Affiliate for affiliate-source tracking on subscription.
Installation
Section titled “Installation”- Install EP Email.
ep-newsletter.zipcomes with an EP Suite licence — ElmsPark supplies it directly (see EP Suite plugins); after install it updates through your site’s Updates screen.- Upload via Plugins → Manage Plugins. Activate.
- Work through the settings sections below.
Shortcodes
Section titled “Shortcodes”| Shortcode | Purpose |
|---|---|
[newsletter-form] | Subscription form. Attributes: title, button, name_field=true/false, list=slug. |
[newsletter-unsubscribe] | Unsubscribe page with optional feedback form. |
Settings sections
Section titled “Settings sections”Subscription
Section titled “Subscription”- Double opt-in. Toggle. If on, subscribers get a confirmation email; only after clicking do they join the list. Strongly recommended.
- Confirmation email subject and body.
- Welcome email subject and body (sent after confirmation).
- Resend welcome to existing subscribers. (new in 1.10.0) Off by default. When someone already subscribed signs up again, they get the welcome email again, at most once every 24 hours per address. Change what they are told with Welcome Sent Again Message under Subscription forms.
- Confirmation redirect page. Where to send users after confirming.
- Default list for forms without an explicit list attribute.
Subscription forms
Section titled “Subscription forms”- Enable. Toggle the shortcode.
- Success and already-subscribed messages.
- Rate limiting. Minutes between subscription attempts from the same IP. Catches lazy bots; does NOT stop attackers who rotate through Tor exits or proxy pools — see Abuse prevention below for that.
Abuse prevention
Section titled “Abuse prevention”Four layers of defence against subscription form abuse, layered to catch different attack shapes:
| Layer | Stops | Blind spot |
|---|---|---|
| Honeypot field | Naive bots that fill every field | Sophisticated bots targeting only visible fields |
| Per-IP rate limit | Lazy bots hammering from one IP | Attackers rotating through Tor exits or proxy pools |
| Per-domain frequency cap (new in 1.1.27) | Subscription-bombing where one victim email domain is signed up to many newsletters at once | Single-victim, single-mailbox attacks |
| Disposable email blocklist (new in 1.1.27) | Sign-ups from throwaway inbox providers (mailinator, guerrillamail, 10minutemail, ~130 others) | Custom-domain disposable services not yet on the list |
Per-domain frequency cap. When too many sign-ups arrive for the same recipient email domain within a rolling window, further sign-ups to that domain are silently accepted but never stored. Designed to defeat subscription-bombing attacks: per-IP rate limiting does nothing against them because each request comes from a different IP. The cap watches the email domain instead. Defaults to 5 sign-ups per domain per 24 hours. Silent success (not visible failure) so attackers cannot probe for the threshold.
Disposable email blocklist. Sign-ups from known disposable / throwaway providers are rejected with an honest “please use your regular email address” message. Built-in list covers ~130 providers including the major families (mailinator, guerrillamail, 10minutemail, yopmail, temp-mail, trash). Add your own domains via the Additional Blocked Domains textarea (one per line or comma-separated, # starts a comment). For developers, the ep_newsletter_disposable_domains filter accepts a richer list at runtime.
Scope. Both new checks only fire on the public [newsletter-form] shortcode. Admin-side Add Subscriber, CSV Import, and the subscribe_external() public API (used by EP Booking and similar plugins for legitimate checkout-time sign-ups) are intentionally unaffected.
Campaign settings
Section titled “Campaign settings”- Default template. Base HTML wrapper for campaigns.
- Batch size and delay. E.g. 100 emails per batch, 30-second delay between. Tune to your SMTP provider’s rate limits.
- Open tracking and click tracking toggles.
Automated newsletters
Section titled “Automated newsletters”- Frequency. Daily, weekly, monthly.
- Send day and time. Read in your site’s timezone — see Timezone.
- Target list.
- Subject template. Supports placeholders for date ranges.
- Email template. Structure of the digest.
Unsubscribe
Section titled “Unsubscribe”- Page URL. Where
[newsletter-unsubscribe]lives. - Success message.
- Feedback collection. Optional — ask why they unsubscribed to improve future content.
Email delivery
Section titled “Email delivery”- Driver. EP Email built-in (uses your configured SMTP), Mailgun (via EP Newsletter Mailgun, the recommended provider), or any registered third-party driver.
- Test connection button.
- Check bounces button — polls the driver’s bounce API and marks bad addresses.
- A separate newsletter sender. The From and Reply-To under General apply to newsletters only, so you can send from a marketing address (for example news@ on its own sending domain) while EP Email keeps its own address for booking and contact mail. Make sure whatever sends your mail has that address or domain verified.
Campaign workflow
Section titled “Campaign workflow”- Compose. Write the subject and body using the campaign editor. Merge tags:
{name},{email},{unsubscribe_url},{site_name}and{date}. When a subscriber gave no name,{name}becomes your Name When Blank setting (under General, for example “there”), or “Subscriber” if that is empty. For one email only, write{name|there}. - Preview. Render the campaign as it will appear in common mail clients.
- Test send. Send just to your own address to check.
- Choose recipients. Pick one or more lists, or a segment.
- Schedule or send now. A scheduled time is read in your site’s timezone — see Timezone.
- Monitor. Open and click rates, bounce count, complaint count all update as the campaign progresses.
Sending your own HTML
Section titled “Sending your own HTML”(new in 1.11.0) Choose Your own HTML as the template and the email you designed goes out exactly as written: your layout, your fonts, your footer, with no wrapper around it. Paste a complete HTML document into the body. Open tracking, if it is on, adds its pixel just inside your closing </body> tag, and every email still carries the one-click unsubscribe headers below. Over the PM API, pass "template": "html" to create-campaign or to an autoresponder email.
One-click unsubscribe
Section titled “One-click unsubscribe”Every email to a subscriber carries List-Unsubscribe and List-Unsubscribe-Post: List-Unsubscribe=One-Click headers (RFC 8058), which Gmail and Yahoo require of bulk senders. That puts an Unsubscribe button next to your From name in those mail apps. It works on every sending route: EP Email, a sending service add-on, or PHP mail(). Confirmation emails and admin test sends do not carry them.
Moving from another newsletter service
Section titled “Moving from another newsletter service”The import-sequences and import-subscribers actions (PM API, admin) bring a list across with each person’s sign-up date, consent history and place in your welcome sequence, so nobody gets an email they already had. An import never sends anything, never re-subscribes anyone who unsubscribed or bounced, and starts as a dry run that shows exactly what would change.
The actions read an ep-newsletter-import/1 file. For EmailOctopus, the converter tools/emailoctopus-to-ep.py in the plugin’s source builds that file from your Contacts exports (one per list), plus an optional description of your welcome series. Run it, dry-run both imports, read the counts, then run them for real. Do this on a staging copy first.
Autoresponders
Section titled “Autoresponders”An autoresponder sequence is a series of timed emails. Example welcome sequence:
- Immediately: “Welcome! Here’s what to expect.”
- +2 days: “Our 5 most useful articles.”
- +5 days: “A case study you might like.”
- +10 days: “Ready to go deeper?”
Each email has its own subject, body, and delay after subscription. Created once, runs forever.
Content digests
Section titled “Content digests”Set up an automated weekly digest:
- “Blog posts published this week” gathers the last 7 days of new content.
- “New products in stock” pulls from EP Ecommerce Products.
- Custom query for bespoke content types.
Digests run on the schedule you set and only send if there’s new content to include.
Background processing (scheduled sending)
Section titled “Background processing (scheduled sending)”Scheduled campaigns, autoresponder sequences, and automated digests are all delivered by a background queue runner. It fires automatically whenever an admin page loads (throttled to once a minute), which is fine for a busy site. On a quiet site where nobody is signed into the admin, that trigger never runs and scheduled email stalls silently.
(new in 1.1.29) To drive the queue on a quiet site, EP Newsletter exposes a secret-token cron URL:
https://your-site.com/?ep_newsletter_cron=<secret>The ready-made URL, with a crontab example, is under Settings → Background Processing. Point a system cron job or uptime monitor at it, for example every five minutes:
*/5 * * * * curl -s "https://your-site.com/?ep_newsletter_cron=<secret>" >/dev/null 2>&1The token is generated once and checked with a timing-safe compare; a wrong or missing token returns HTTP 403 and does no work. Keep the URL private (anyone with it can trigger a send, though it exposes no subscriber data). The admin-page-load trigger still works as a fallback, and the process-queue API action below does the same job for an authenticated caller.
Timezone
Section titled “Timezone”(new in 1.8.0) The times you enter — a campaign’s schedule, the automated digest’s send time and weekly send day — are read in your site’s timezone, set under PageMotor’s Site Settings → Time Zone. The schedule field on the campaign composer names that zone underneath it, so you can always see which clock you are typing in. Type 09:00 and the campaign goes out at 09:00 your time, whatever timezone the server happens to be on.
Stored times are UTC underneath, converted back to your zone whenever they are shown to you. That is what makes the server’s own setting irrelevant: you no longer need to ask your host to change date.timezone, and a server left on UTC is no longer a problem. Some hosting panels, CloudPanel among them, default new sites to UTC — that used to send a Central European site’s campaigns two hours early. It no longer does.
On PageMotor 0.10.3b, which has no Site Settings → Time Zone yet, times are read in the server’s PHP timezone exactly as before. Nothing about what you type changes, and upgrading the core later moves you onto the site setting.
Upgrading from 1.7.x or earlier
Section titled “Upgrading from 1.7.x or earlier”Times already in your database were stored on the server’s local clock. The first admin page load, or the first background queue run, after the update converts them once, automatically. You do not need to do anything, and none of your existing dates should change on screen.
If you have campaigns scheduled or autoresponder sequences in flight across the upgrade, glance at the campaign list afterwards and confirm the scheduled times still read as you intended.
Managing EP Newsletter over the PM API
Section titled “Managing EP Newsletter over the PM API”(new in 1.2.0) EP Newsletter registers PM API actions under the EP_Newsletter class, so an agent or script can drive the whole content-to-email pipeline through the PM API and MCP without writing to the database directly. Browse them with list-actions, inspect one with describe-action, then invoke with call-action. Each handler returns the standard result envelope ({success, data} on success, {success:false, reason} on a problem).
Access tiers follow the data each action touches: reads are read-only so an agent can report without write access, writes are admin, and subscribe is producer (a trusted caller).
1.2.1 adds autoresponder edit and delete actions, read actions for the queue and the send log, and a delay_minutes option on email steps so sequences can run sub-hour.
| Action | Access | Purpose |
|---|---|---|
list-lists | read-only | All mailing lists with subscriber counts. |
list-subscribers | admin | Subscribers, filterable by list_id and status, paginated. |
list-campaigns | read-only | Campaigns with open and click counts. |
list-autoresponders | read-only | Autoresponder series with their email steps. |
get-campaign-stats | read-only | Open and click stats for one campaign. |
subscribe | producer | Subscribe a contact. Default: trusted caller, active immediately (skips double opt-in and the public abuse checks). Pass double_optin: true (new in 1.5.3) to create the contact as pending and send the confirmation email instead. |
unsubscribe | admin | Unsubscribe by email and cancel pending autoresponder emails. |
create-list | admin | Create a mailing list. |
delete-list | admin | Delete a list. Subscribers are kept. |
create-campaign | admin | Create a draft campaign. |
update-campaign | admin | Update a campaign’s subject, body, list, or template. |
send-campaign | admin | Queue recipients and start sending now. |
schedule-campaign | admin | Schedule a draft to send at a future time. |
create-autoresponder | admin | Create an autoresponder series. |
add-email | admin | Add a timed email step to a series (delay in days, hours, and minutes). |
update-autoresponder | admin | Update a series (name, list binding, or active/paused status). |
delete-autoresponder | admin | Delete a series and all its email steps and pending queue items. |
update-email | admin | Update one email step (subject, body, delays, template). |
delete-email | admin | Delete one email step and its pending queue items. |
get-autoresponder-queue | admin | Read the autoresponder queue (pending, sent, failed, cancelled) with scheduled times, filterable by subscriber or status. |
process-queue | admin | Run the background queue now: due campaign batches, autoresponder emails, scheduled campaigns, and due digests. |
list-send-log | admin | Read the unified send log, newest first, filterable by send_type. |
The API subscribe deliberately bypasses the per-domain cap and disposable-email blocklist that guard the public [newsletter-form], because an authenticated API caller is trusted. This is the same reasoning as the subscribe_external() PHP path that EP Booking uses for checkout-time sign-ups.
(new in 1.5.3) When your integration captures its own opt-in and needs the consent trail, pass double_optin: true to subscribe: the contact is created (or moved back to) pending with a fresh token, the confirmation email is sent through the standard flow, and they only become active when they click the confirmation link — which also fires the welcome email and autoresponders, exactly like a form signup. An already-active contact is never demoted to pending. The response reports status and confirmation_sent alongside subscriber_id; if the confirmation email fails to send, the action returns the failure with the pending subscriber_id so you can retry.
Delivery log
Section titled “Delivery log”(new in 1.2.0) Every newsletter send is recorded in a single table, ep_newsletter_send_log, whichever delivery route it took (an external driver, EP Email, EP Email’s SMTP class, or the PHP mail fallback). Each row carries a send_type column (campaign, autoresponder, welcome, confirmation, transactional), the recipient, status, the driver used, the provider message id, and the related campaign and subscriber ids. One place to diagnose deliverability, instead of piecing it together from the queue tables. Read it over the API with list-send-log (new in 1.2.1).
Troubleshooting
Section titled “Troubleshooting”“Scheduled campaigns go out at the wrong time”
Section titled ““Scheduled campaigns go out at the wrong time””On 1.8.0 and later, check Site Settings → Time Zone is your zone. That is the clock the schedule field uses, and the field names the zone underneath it so you can confirm it at a glance.
Before 1.8.0 the schedule was read on the server’s clock, so a server left on UTC fired a Central European site’s campaigns two hours late. If you are still on 1.7.x, updating is the fix. Changing date.timezone on the server was the old workaround and is no longer needed.
If the times are right but the send is simply late, that is the queue runner rather than the clock — see Background processing.
“Campaign paused partway through sending”
Section titled ““Campaign paused partway through sending””Usually an SMTP error that tripped the driver. Check EP Email’s delivery log. If SMTP is the problem, fix it and click Resume on the campaign.
“Open rates are 0%”
Section titled ““Open rates are 0%””Open tracking uses an invisible pixel. Gmail, Apple Mail’s privacy protection, and most modern clients proxy images so tracking pixels don’t load per-user. Open rates have become unreliable metrics regardless of plugin.
“Subscribers complain about not receiving confirmation emails”
Section titled ““Subscribers complain about not receiving confirmation emails””EP Email SMTP config is wrong, or emails are going to spam. Check EP Email’s delivery log. Test with a Gmail address you control.
“I’m hitting my SMTP provider’s rate limit”
Section titled ““I’m hitting my SMTP provider’s rate limit””Drop batch size, increase batch delay. If you’re regularly sending thousands, consider EP Newsletter Mailgun which handles higher volumes more smoothly.
“Bounce addresses keep receiving campaigns”
Section titled ““Bounce addresses keep receiving campaigns””Check the bounce check. Click Check bounces manually. If bounces aren’t being flagged, the delivery driver’s bounce webhook isn’t configured.
“Content digest doesn’t include my new page”
Section titled ““Content digest doesn’t include my new page””Digests only include content matching their query. Check the digest’s content type filter. Drafts and scheduled-but-not-yet-published pages don’t count until they’re actually live.
“Subscription form being subscription-bombed”
Section titled ““Subscription form being subscription-bombed””Dozens of pending subscribers with random-alphanumeric names and IPs from Tor exit ranges or commercial proxy pools. Your form is on a publicly-harvested list of newsletter forms and a bot is signing one or more victim addresses up to all of them at once. Per-IP rate limiting does nothing here because each request comes from a different IP. Confirm Abuse prevention → Per-Domain Frequency Cap is on (lower the count to 3 or 1 if the attack is concentrated on a single recipient domain) and Disposable Email Blocklist is on. Clean up the pending spam in Subscribers. The frequency cap is a rolling window so once an attack subsides the cap auto-lifts.
“Legitimate user with a temp email is being rejected”
Section titled ““Legitimate user with a temp email is being rejected””The disposable blocklist working as intended. If you want to allow one specific provider, add it as an exception via the ep_newsletter_disposable_domains filter in site code. To disable the whole blocklist, untick Abuse prevention → Disposable Email Blocklist.
Feedback and corrections
Section titled “Feedback and corrections”For a quick question about this plugin, EP Support inside your admin is the fastest option. The chat widget sits on every EP plugin settings page and knows which one you’re on, with starter questions and links preloaded for that exact screen.
For anything bigger — a bug report, a feature request, or a “how do I…” that needs a real reply — open a ticket at help.elmspark.com. A real person, helped by AI, writes the reply. Usually within a few hours. Tickets don’t disappear into the void.
Changelog
Section titled “Changelog”1.11.4
Section titled “1.11.4”- Changing this plugin’s settings over the API now needs an admin token. Producer tokens and AI apps connected through a producer account can still read the settings. Saving from the Admin screen works exactly as before.
1.11.3
Section titled “1.11.3”A security update. Please install it.
- People who unsubscribed stay off your list unless they confirm. Typing the address of someone who left into a sign-up form no longer signs them back up. They get a confirmation email, and only their click puts them back, whatever your double opt-in setting.
- Subscriber exports are safe to open in a spreadsheet. A name or email that starts like a formula is now saved as plain text in the CSV.
- Templates that never existed are gone from the menus. Minimal, Branded and Notification were offered as email templates but were never built, so an email set to any of them went out with no template at all. They are no longer offered. Anything already saved with one still sends exactly as it did, and the campaign editor shows it as Plain text.
- Campaigns sent through Mailgun, Brevo or SendGrid get your template. With EP Newsletter Mailgun 1.0.15, Brevo 1.0.10 or SendGrid 1.0.20, a campaign set to the Default template goes out inside EP Email’s template, just as it does without a delivery service, and carries a plain-text version.
1.11.2
Section titled “1.11.2”A security update. Please install it.
- Only you can unsubscribe your subscribers. People you imported, added by hand or added through another plugin could be unsubscribed by someone who only knew their email address. Every unsubscribe link now needs the subscriber’s own secret, and people who confirm their sign-up keep theirs.
- Your drafts and sequences are private again. The list, campaign, sequence and statistics reads in the API now need an administrator’s key. Before, they could be read without one, including campaigns you had not sent yet.
- Confirmation emails can no longer carry someone else’s words. The “please confirm” email now greets the reader with your Name When Blank text instead of whatever was typed into the form, and an address gets at most one confirmation email an hour.
- A soft bounce no longer stops mail. Only a hard bounce or a spam complaint marks a subscriber as bounced. A full mailbox or a busy server does not.
1.11.1
Section titled “1.11.1”- Works with EP CRM. A subscriber confirming their sign-up, or unsubscribing, now appears on their record in EP CRM. Nothing changes if you do not use EP CRM.
1.11.0
Section titled “1.11.0”- “Hi there” when you don’t have a name. A new setting, Name When Blank (under General), sets what {name} becomes when a subscriber gave no name, for example “there”, so “Hi {name},” reads “Hi there,”. Left blank it stays “Subscriber”, as before. For one email only, write {name|there}: it uses the real name when there is one and your fallback when there isn’t.
- Send your own HTML exactly as written. A new template choice, Your own HTML, sends the email you designed with no wrapper around it: your layout, your fonts, your footer. It still carries the one-click unsubscribe header Gmail and Yahoo expect, and the open-tracking pixel now sits inside your email’s closing body tag, so a full HTML document stays valid.
- Moving from EmailOctopus. A new tool, tools/emailoctopus-to-ep.py, turns your EmailOctopus list exports into a file the existing Import actions read. People on more than one list become one subscriber on each list, their sign-up dates and consent come across, and each person’s place in your welcome series is worked out from when they joined, so nobody gets an email they already had. The import never sends anything, and it runs as a dry run first.
1.10.0
Section titled “1.10.0”- Send the welcome email again to someone who is already subscribed. A new setting, Resend Welcome to Existing Subscribers, under the Welcome Email settings. When someone already on your list fills in a sign-up form again, often because they want the free guide your welcome email carries, they get the welcome email again and are told so. Before, they only saw “You are already subscribed” and got nothing.
- It cannot be used to flood anyone’s inbox. The welcome email goes to an address at most once every 24 hours, counting the first welcome too. The email always uses the name you have on file, never what was typed into the form.
- It is off until you switch it on, and it needs the Welcome Email switched on. You can change what the visitor is told with the new Welcome Sent Again Message.
- Sequences are not restarted. Only the welcome email is sent again.
- Needs PageMotor 0.11.5.
- The new “Install and activate EP Email” button now speaks your language. Its label, its progress messages and its error messages are translated into Danish, German, Spanish, French, Italian, Dutch and Portuguese. Before, sites in those languages saw them in English.
- Nothing else changes.
- One click to get EP Email. If EP Email is missing or switched off, the “EP Email is required” notice now has a button: Install and activate EP Email, or Activate EP Email if it is already installed. Before, you had to leave the page, find it and do it by hand. Only administrators see the button.
- EP Email comes from the ElmsPark update server and is checked against its published checksum before it is installed. If the download cannot be verified, nothing is installed and the page says so.
- Needs PageMotor 0.11.5.
- Move a list from another newsletter system without anyone getting a repeat email. Two new actions, import sequences and import subscribers, bring across your lists, your subscribers with their original sign-up dates and consent history, and your autoresponder sequences. People already part-way through a sequence carry on from where they were: someone who has had the first three emails gets the fourth next, never the first three again. An import never sends anything, never re-subscribes anyone who unsubscribed or bounced, and running it twice changes nothing. It always starts as a dry run that shows what would happen.
- Pausing a sequence now pauses its emails. A paused sequence holds the emails already waiting to go out, and sends them when you switch it back on. Before, pausing only stopped new people joining it. If you have a paused sequence with people waiting in it, they will receive their due emails as soon as you switch it back on.
- A sequence can move people onto a list when they finish it, for example from a welcome sequence onto your main newsletter list.
- A campaign with no list chosen can no longer go to everyone by accident. A new Campaign Settings choice, Campaigns With No List, says what happens: send to all active subscribers (as before), send to a fallback list you name, or refuse until a list is chosen. A campaign whose list has been deleted is refused instead of sent. Creating a campaign over the API without a list now warns who it would reach, and a new campaign-audience action shows who a campaign would go to, and how many people, without sending.
- Existing subscribers are not welcomed twice. When someone already on your list signs up through another form, or is added over the API to another list, they get that list’s own sequence only. Sequences that are not tied to a list, such as a welcome, are not started again.
- Data requests now include consent history. EP GDPR’s export of a subscriber now carries their consent history with its original dates and IP addresses, their stored details, lists and sequence emails.
- Needs PageMotor 0.11.5.
1.8.12
Section titled “1.8.12”- A Modular Content block keeps its formatting in a newsletter made only of the block. When a campaign, autoresponder or test email held nothing but
[modular-content id="7"], the block arrived as plain text. It now arrives as the block was written, whenever the email uses a template or a Delivery Service. - Works with EP Email 1.10.73. Needs PageMotor 0.11.5.
1.8.11
Section titled “1.8.11”- A failed test email now says why. When a test send fails, the message names the Delivery Service it tried and gives the reason the service returned, such as a missing sending key or a refused request. It used to say only “Failed to send test email.”
- A campaign that reached nobody now shows as Failed. If every email in a campaign fails to send, the campaign list shows Failed in red, with a short note on what to check. It used to show Sent.
- Failed sends are counted in the campaign list. When some emails in a campaign fail, the Recipients column shows how many, for example “5/9 (4 failed)”.
- Needs PageMotor 0.11.5.
1.8.10
Section titled “1.8.10”- Modular Content blocks now work in newsletters. With EP Email 1.10.72 or later, put
[modular-content id="7"]in a campaign, an autoresponder or your confirmation and welcome emails, and the block’s content is sent in its place. Edit the block once and your pages and your newsletters both change. Only live blocks are sent, and scripts, forms and other shortcodes inside a block are left out. - Add-ons can now change newsletter text before it is sent. With EP Email 1.10.72 or later installed, add-ons built on the EP Email Extension API can change the text of every newsletter message: campaigns, autoresponders, and the confirmation, welcome and test emails. This works whichever sending service the newsletter uses. Without such an add-on, nothing changes.
- Needs PageMotor 0.11.5.
- The Gibberish Name Filter no longer drops real names. With the filter switched on, some ordinary names were read as machine-generated and the sign-up was silently dropped: names such as Mark Schwartz, Bjorn Strand or Ewan McGregor, and names typed in capitals. The filter now scores each word of a name on its own, treats spellings such as “sch” and “cz” as one sound, and reads accented letters properly. It still catches the random-string names that sign-up bots use.
- The filter is off by default. If you never switched it on, nothing changes for you.
- Needs PageMotor 0.11.5.
- Lighter pages. The code behind the sign-up form now loads only on pages that show a sign-up form, wherever the form sits: in the page itself, or in a header, footer or other box. Other pages, including your 404 page, no longer load it.
- Needs PageMotor 0.11.5.
- Settings language menu. The language menu in this plugin’s settings now lists only the languages it is actually translated into, plus English, so you can no longer pick a language that changes nothing.
- Danish. Adds a Danish translation.
- Section status. Each settings section shows whether that feature is switched on. On a site that also runs an older EP plugin, the section shows its plain title instead.
- Branding. When EP Newsletter is the plugin that holds your brand colour, its settings gain a Branding section: one colour every EP form shares for its buttons.
- Fixes a crash on the newsletter signup form when an older EP plugin is installed on the same site. Submitting the form returned an internal error and nothing was saved or sent. EP plugins share one common code library, and whichever copy loads first is the one every EP plugin on that site uses, so a single out-of-date plugin could leave this one calling a spam check its copy did not have. The check now carries its own fallback and no longer depends on another plugin being up to date.
- No change on a site where this never happened: the same spam check runs, and nothing else changed.
- Makes the double opt-in option easier to find when browsing the API for a confirmation-email trigger. No behaviour has changed.
- Corrects the PageMotor 0.11.3 preparation shipped in 1.8.3. That release grouped this plugin’s API and MCP actions into families, but in a shape PageMotor 0.11.3 does not accept. On 0.11.3 the plugin would have registered none of its actions, and nothing on screen would have said so.
- This version uses the shape 0.11.3 expects, and keeps the earlier shape for sites still on an older PageMotor. One build serves both, so there is no order you have to update things in.
- Safe to install now. Nothing you can see changes.