Repository navigation
Releases
1.8.0
Added: 15 values in the Control Panel, without this package getting a screen of its own
This package has no Control Panel of its own, only four public routes. That is exactly why every
one of its values was out of the operator's reach until now: a link's lifetime, the throttling,
the sender address, all of it only in .env. Settings → Addon Settings now carries a section
for this addon, with five groups:
- [new] Magic link: whether it is offered, how long the signed URL is valid, how long the session
lasts afterwards, the response-time floor, and whether links also go to unknown addresses. The
response-time floor is not a finishing touch: without it the response time betrays who is on
the list, because the fast case (address unknown) can be told apart from the slow one (mail
queued). “To unknown addresses” stays off, and it should stay that way — switched on, this
endpoint is an open mail sender with a few steps in between. - [new] Throttling: requests and time window per address and per origin. The second counter is the
one that stops somebody using this endpoint to mail a list of addresses that is not theirs. - [new] Sender: address and name for the case where the brand has no sender identity of its own. If
it has one, that one wins. - [new] Blocks on the page: whether the block for notifications, for the suppression list and for
sequences is shown. - [new] Audit trail: whether applied changes are reported to LeadHub.
Only the deviation is stored, everything else keeps following
config/preference-center.php.
Not on the page, and the group descriptions say so: routes.enabled, routes.prefix and
routes.middleware are read while the routes are being created. The same trap, hidden one level
down, catches the marketing block: the token route asks at creation time whether the source is
available, so that switch also decides whether this route exists at all. Offered on the page it
would make the block disappear at once and still leave the route standing until the next deploy;
half effective is worse than not at all. The three other sources are asked at request time only
and are therefore on the page. Also left out: delivery.mail_headers and
delivery.ignored_query_parameters, which belong to the protocol with the mail provider, and
audit.log_channel, because the log channels belong to the host and a free-text field over them
is one typo away from an audit trail that writes into nowhere.
New permission manage preference-center settings. Nobody holds it at first, and until it is
assigned to a role the section stays invisible.
Requires goldnead/statamic-brand-context 1.13 or newer. Older versions carry the page but
do not apply its values reliably: on an installation with a single brand, the settings of the
addons that registered last never reached the config, and up to 1.12 a second save of the same
section deleted the first save's override, without a message. Anyone who set values before this
update should check afterwards that they are still there.
Fixed: the lint baseline counted occurrences instead of naming a cause
For contributors only, with no effect on an installation. A baseline entry recorded “18” as the
number of env() calls in config/preference-center.php; with the 19th the run went red. A
baseline that records a count turns red with every addition and is then counted up instead of
read. The cause is that the rule measures against the application's config path, which does not
exist in a package; it has a parameter for that, and the baseline entry falls away entirely.
1.7.0
Fixed
-
[fix] A person with an umlaut in their address could never reach their own preferences. The magic
link form validated withfilter_var($email, FILTER_VALIDATE_EMAIL), which predates RFC 6531 and
rejects every non-ASCII character.bärbel.öztürk@beispiel.de— a contact in the CRM, a
subscriber on two lists, and someone whose token link works perfectly — was answered as unknown.The failure had no symptom, and that is the point: this form answers the same neutral sentence to
everyone on purpose, so that nobody can use it to find out who is on a list. A rejected address is
therefore indistinguishable from an unknown one. The page the GDPR expects a person to be able to
reach was closed to them, silently, for as long as the check existed.EmailNormalizer::looksDeliverable()now judges the domain through its punycode form and a
Unicode local part on its own terms, while still refusing what is genuinely undeliverable.
1.6.3
Fixed — die Matrix zeichnete Kästchen für Kanäle, die es nicht gibt
Die Spalten kommen aus der globalen Kanalliste, die Zeilen aus den Arten. Seit
goldnead/statamic-notifications 1.7 kann eine Art sagen, welche Kanäle sie
überhaupt führt — die Zeile fragte aber nicht danach und zeichnete für jede
Spalte ein Kästchen.
Auf der Produktion sichtbar an crm.task_assigned: die Art führt seit
leadhub 2.5 keinen Digest mehr, in der Tabelle stand die Digest-Spalte
trotzdem. Anklickbar, gespeichert, und beim Versand ignoriert.
Genau die Sorte Bedienelement, die diese Reihe abschaffen sollte: ein
Kästchen, das aussieht wie eine Wahl und keine ist.
Eine Art ohne diesen Kanal bekommt jetzt eine leere Zelle. Wichtig dabei:
„nicht vorhanden" und „aus" bleiben verschieden — ein ausgeschalteter Kanal
ist eine Wahl, ein fehlender ist keine.
1.6.2
Fixed — ein Mensch, eine Einstellung, egal durch welche Tür
Ein Besuch über den Mail-Link wurde immer als Kontakt aufgelöst, auch bei
jemandem, der ein Konto hat. Das hatte zwei Folgen, und beide sind Fehler:
- [fix]
notification_preferenceshängt an(user_id, contact_uuid). Wer über den
Mail-Link etwas einstellte, schrieb in eine andere Zeile als angemeldet —
derselbe Mensch, zwei Einstellungssätze, keiner sah den anderen. Das war
schon vor dieser Reihe so und fiel nur niemandem auf. - [fix] Seit 1.6.1 die Arten nach Zuständigkeit filtert, verschwanden über den
Mail-Link zusätzlich alle Einstellungen, die ein Konto voraussetzen.
Findet sich zu der Adresse ein Konto, wird der Besuch jetzt als dieses Konto
aufgelöst — dieselbe Kennung wie beim Anmelden. Mehr darf dabei niemand: der
Token beweist ohnehin die Verfügung über das Postfach, und
canStoreNotificationPreferences() hing nie am Kontotyp, sondern nur daran,
ob die Person überhaupt einzuordnen ist.
Gefunden in einem Nutzertest mit einem echten Konto — kein Test hätte das
treffen können, weil keiner je einen Nutzer anlegte.
Fixed — die Testsuite hing von früheren Läufen ab
statamic.users.repository steht in der Suite auf file, und der Treiber
schreibt echte YAML-Dateien. Die Datenbank wird zwischen Tests zurückgesetzt,
diese Dateien nicht. Solange kein Test Nutzer anlegte, blieb das folgenlos;
mit dem ersten, der es tut, fielen prompt drei fremde Tests um. setUp() räumt
das Verzeichnis jetzt aus.
1.6.1
Fixed — der leere Benachrichtigungs-Block stand mit einem falschen Satz da
Seit goldnead/statamic-notifications 1.7 die Arten nach Zuständigkeit
filtert, kommt eine leere Liste regelmäßig vor: eine Newsletter-Adresse ohne
Konto hat schlicht keine Benachrichtigungen einzustellen. Der Block wurde
trotzdem gezeichnet — mit der Zeile „Diese Installation kennt keine
Benachrichtigungsarten", die dann doppelt falsch war: die Installation kennt
sehr wohl welche, und dem Leser hilft der Satz ohnehin nicht.
hasTypes() verlangt jetzt Zeilen, nicht nur ein vorhandenes Array. Für den
Menschen davor sind „keine registriert" und „keine für dich" dasselbe: es gibt
nichts einzustellen, und eine Überschrift ohne Inhalt ist schlimmer als keine.
1.6.0
Added — laufende Serien verlassen
Der vierte Block, und der einzige mit einer Zwischenstufe. Listen sind An/Aus
für ein ganzes Thema, die Frequenz gilt für alles — eine Serie ist ein
einzelner Strang, den man verlassen kann, ohne den Rest aufzugeben. Genau das
ist der Fall, den jemand meint, der eine Willkommensstrecke nicht zu Ende lesen
will.
Gezeigt werden laufende Serien (ein Lauf wartet noch auf seinen nächsten
Schritt) und bereits verlassene. Ohne die verlassenen wäre der Block nach
dem Ausstieg leer und der Weg zurück nirgends zu finden.
Wie die drei anderen Quellen über class_exists geschützt: ohne
goldnead/statamic-automations gibt es keine Serien und damit keinen Block.
Abschaltbar über preference-center.sources.sequences.
1.5.2
Added — a test holds the informal address, and the way back is documented
1.5.1 changed the German wording and left the net for it in the host that had reported the
problem. That is the wrong place for a package's own guarantee: a refactor here, or a fresh
installation, would not notice the register switching back.
tests/Feature/GermanFormOfAddressTest.php checks every German string in de/ for formal
address forms. It matches the shapes the formal register actually uses rather than snapshotting
sentences, so rewording stays free and switching back to „Sie" does not — and it distinguishes
the address „Sie" from the plural pronoun „sie", which appears in these files legitimately
(„Redaktionelle E-Mails. Sie beruhen auf deiner Einwilligung") and has to stay. Checked against
the 1.5.0 files: three of the four assertions fail there.
An installation that prefers the formal register publishes the translations and edits them:
php artisan vendor:publish --tag=preference-center-translations. Wording is not part of this
package's public contract (see the README), which is why 1.5.1 was a patch release.
1.5.1
Changed — the German strings now use „du", like the rest of this family
This package was the only one of the goldnead addons whose German addressed the reader formally
(„Ihr Link zu den E-Mail-Einstellungen", „kopieren Sie diese Adresse"). statamic-marketing and
statamic-notifications have always used „du". On a host running all three, the same person got a
„du" confirmation mail and a „Sie" preferences link — and the preferences page they landed on
switched back again.
Both German files are converted: resources/lang/de/mail.php (the magic-link mail) and
resources/lang/de/public.php (the page that link opens). Wording only. Sentence structure,
order, placeholders and keys are untouched; only the form of address changed. The one remaining
„Sie" in lists_hint is the pronoun for „E-Mails", not an address.
English is unchanged. Nothing in src/ or in the views changed, so no behaviour did.
1.5.0
Changed
-
The five sender-identity classes moved to
goldnead/statamic-brand-context1.8.0, which is
now required at^1.8. They were four byte-identical copies with four namespaces — this package,
marketing, notifications and automations each grew their own on 12.08.2026 — and copies drift: by
the evening the marketing one had stopped refusing a transport without an address. Which address a
brand sends under is a property of the brand, so the rule lives with the brand.Behaviour is unchanged here, down to the log lines.
Goldnead\PreferenceCenter\Contracts\SenderIdentityResolver
andSending\BrandMailerstay as this package's own extension points.Sending\SenderIdentity
andSending\SaidRecentlyare gone from this namespace; use theGoldnead\BrandContext\Sending\
versions.
1.4.0
Fixed — the magic link went out under the host's identity, not the brand's
MagicLinkRequests ended in Mail::to($email)->send(new MagicLinkMail($links)): one mail carrying
every brand's link, through the process-wide default mailer, with the process-wide mail.from. A
mail that speaks for several brands has to pick one From, and on a host where each brand's domain
is verified in its own relay account (Scaleway TEM, Postmark, SES) there is no correct pick — the
provider refuses the address or substitutes its own, so the person who asked brand A about their
settings hears from brand B.
One mail per brand now, each as that brand. Contracts\SenderIdentityResolver answers "which
mailer, which From, which locale for brand N" out of brands.settings.mail; Sending\BrandMailer
is the single door the mail leaves through and puts the answer on the message
(Mailable::from(), Mail::mailer($name)) rather than into config — Laravel burns mail.from
into a mailer instance on first resolution and caches it for the life of the process, so a scoped
Config::set would escape its own finally.
In the ordinary case nothing changes. One brand knows the address, so one link, so one mail —
the same mail as before, now over that brand's own transport. Only the rare address several brands
know is split, and the split is what makes each part honest. The cost, stated plainly: such an
address receives one mail per brand for one request, so the per-address ceiling becomes
max × brands-that-know-it. Bounded by the host's brand list, not by anything a caller supplies,
and every one of those mails comes from a sender the recipient already has a relationship with.
Changed — the mail names its brand whenever the link has one
Previously only when several links shared one mail. With the links now in separate mails, that was
the sentence that said which is which. A single-brand install has no brand on the link and the
label stays absent, exactly as before.
Changed — a brand that declares a broken mail identity sends nothing
A brand that declares settings.mail without from_address, or names a mailer that
config/mail.php does not define, sends nothing and says so at error level, throttled per brand.
Delivering under the host-wide From instead would be delivering under another brand's identity,
quietly. The other brands that know the address still get their mail; MagicLinkRequests::request()
returns the new outcome misconfigured only when none of them got out. Like every other outcome it
is for logs and tests — the page says the same sentence whatever happened, which is the whole point
of the endpoint.
A single-brand install is unchanged, and that is covered by a test rather than by intent. So is
a multi-brand install whose brands carry no settings.mail: both resolve to the config identity,
including the package's own preference-center.magic_link.from. A host that keeps sender
identities somewhere else rebinds SenderIdentityResolver in its own provider.