1. 1.0.9

    Latest
    • Added sorting by column to the add-on's lists in the Admin panel (click a column header); requires core 19.1.16 or later
    • The add-on's list filters use the new filter bar of the Admin panel (active filter chips, "Clear all", "More filters")
    • Added: dynamic segments. On the Users, Listings, Payments (promotions, subscriptions) and Reviews admin lists, a "Save as segment" button saves the current filters as a newsletter segment. Each time a campaign is sent, it reaches the people that list shows at that moment.
    • Added: campaign audience. A campaign can reach its confirmed subscribers only, the people of its dynamic segments who never subscribed only, or both. People who never subscribed get an opt-out link instead of an unsubscribe link, and an opted-out address is never emailed again until it subscribes and confirms.
    • Added: excluded segments. The people of an excluded segment never receive the campaign, even when they belong to a selected one.
    • Added: a live recipient count on the campaign form, which follows the audience, the segments, the target countries and the sending mode.
    • Added: personalization variables for campaigns: {first_name}, {name}, {email}, {phone}, {site_name}, {site_url} and {unsubscribe_url} are replaced with each recipient's details in the subject and the content (email and SMS). A fallback can follow a pipe, for example {first_name|there}. The campaign form lists them in a Personalization card, and a click copies one.
    • Added: hints for the subject and content fields of the campaign form.
    • Added: the Segments page lists the admin lists dynamic segments can be built from, and shows the type and the number of people of each segment. The edit page of a dynamic segment shows its list, its filters and how its people stand towards the newsletter.
    • Updated: dynamic segments are never offered on the subscription forms, the subscriber forms or the Newsletter page section.
    • Updated: a campaign using a segment whose list is unavailable (its add-on is turned off) is not sent.
    • Fixed: a subscription with a phone number and no email address could not be saved (server error), and with double opt-in such subscribers would have been confirmed at once. They are now saved and stay pending until they open the confirmation link sent by SMS (using the site SMS settings). Without SMS settings, the subscribe form asks for an email address instead. The update makes the subscriber email column optional.
    • Fixed: subscribing again with an unsubscribed address re-activated it at once. It now always goes back to pending and must be confirmed again with a new link, and an old confirmation link can no longer re-activate it.
    • Fixed: the public subscribe form accepted any segment, private and inactive ones included, and could add segments to an existing subscriber. It now only joins active segments that are public or selected on the Newsletter page section, and only the signed-in owner of an address can change the segments of an existing subscription.
    • Fixed: the subscribe form answered differently for new and already subscribed addresses. It now always shows the same message.
    • Updated: the confirmation and unsubscribe links now open a page with a button to confirm the action, so mail scanners that open links no longer confirm or unsubscribe anyone.
    • Added: campaign and welcome emails carry the List-Unsubscribe and List-Unsubscribe-Post headers (RFC 8058): mail clients can show their own one-click unsubscribe button.
    • Fixed: the CSV and TXT subscriber exports could hold spreadsheet formulas (e.g. a name starting with =). Such cells are now prefixed with a single quote, which the import removes again.
    • Updated: the automatic clean-up of unconfirmed subscriptions now includes the phone-only ones.
    • Fixed: the subscription confirmation, welcome and campaign emails were sent from the placeholder address newsletter@example.com, which mail services and recipient servers reject, so they never arrived. They now use the site sender address and name (Settings > Mail) unless another sender is set in the newsletter settings. The update removes the stored placeholder sender.
    • The "From Name" and "From Email" newsletter settings are now optional and show the site sender they fall back to.
    • New "Countries" settings tab with a "Country-based newsletter" option (off by default). When on, campaigns get a "Target Countries" card to send them to the subscribers of some countries only (optionally including the subscribers without a country), segments can be restricted to one country, and the subscriber list shows and filters by country.
    • Each subscriber is now tagged with the country of the site it subscribed from (or the account's or listing's country for the marketing-offers consent box). The update fills in the country of the existing subscribers from the user account, or else the latest listing, using the same email address.
    • New "Show the country field on the subscribe form" option (off by default): the site is loaded per country, so the subscribe forms don't ask for a country unless this option is on.
    • A segment restricted to a country is only joined by, and only listed for, the subscribers of that country, default segments included.
    • The Add Subscriber form has a country select, and the subscriber import and export have a new country_code column, added last so files exported by earlier versions still import.
    • The campaign edit page now shows how many active subscribers match the saved segments and countries.
    • Scheduled campaigns are now sent automatically once their date is reached, by the new 'newsletter:send-scheduled' command that the Laravel scheduler runs every minute (the server cron must run 'php artisan schedule:run').
    • Saving a campaign with a "Scheduled At" date now gives it the Scheduled status; it always stayed a draft before.
    • A campaign can no longer be sent twice (double-click or overlapping runs): it is claimed in a single database update before sending.
    • The public subscribe endpoint now enforces the configured rate limit ('rate_limit' attempts per minute per IP address), with a translated error: HTTP 429 for AJAX requests, a redirect back with the error otherwise.
    • The French translation now has proper accents and typography.
    • Removed the unused 'notify_admin_on_subscribe' / 'notify_admin_on_unsubscribe' config keys: admin alerts follow the core notification types.
    • The documentation now describes the installation, update, deactivation and removal steps exactly as the add-on manager performs them, and now covers every setting (including the automatic clean-up of unconfirmed subscriptions), the NEWSLETTER_FROM_NAME / NEWSLETTER_FROM_EMAIL / NEWSLETTER_REPLY_TO keys, the supported import and export formats, and the notification types that control the add-on's emails.
    • The admin "New campaign", "New segment" and "New subscriber" forms are now submitted through AJAX, so validation errors come back without a full page reload.
    • Leaving 'NEWSLETTER_FROM_NAME' or 'NEWSLETTER_FROM_EMAIL' empty in '.env' no longer blanks out the sender: an empty entry now falls back to the application name and to 'MAIL_FROM_ADDRESS' as it did when the key was absent.
    • New "Auto-delete unconfirmed subscriptions" option in the Opt-in settings (visible only when Double Opt-In is enabled), with a configurable retention period in days.
    • New newsletter:purge-unconfirmed artisan command, scheduled daily by the add-on, that deletes pending subscriptions whose email address was never confirmed (supports --days, --dry-run and --force).
    • "Delete unconfirmed now" button (AJAX) next to the retention field, to run the same clean-up on demand with the number of days currently entered in the form.
    • Added 'consent_given_at' column to 'newsletter_subscribers' to stamp the opt-in timestamp (wording is audited via 'gdpr_consent_logs')
    • Subscription form now renders a required consent checkbox when the GDPR add-on is active, with a link to the configured privacy policy.
    • Explicit opt-ins are mirrored to the GDPR consent log ('newsletter_opt_in' action, marketing category) for centralized reporting.