This week's LumiWed product updates.
-
Review numbers can be published from the admin app — the homepage reviews
band reads a rating and review count that had to be written straight into the
database before. Marketing settings now has a Review platforms card to type in
what the Trustpilot profile says and publish it, with the same rules the
database enforces so a half-filled row can never reach the homepage.
-
LumiWed vs The Knot — a side-by-side for couples comparing us with The Knot, including what they do better (registry, vendors, budget).
-
Wedding website vs Wix or Squarespace — when a general site builder is the wrong tool, and when it is not.
-
Blocking a junk email domain is now an admin edit, not a deploy — Catalogs
gained an "Email domains" tab. Anything listed there is refused when a guest is
added, updated or imported, and the match covers subdomains, so one entry for
mailinator.com also stops sub.mailinator.com. The domains reserved by
internet standard stay in code, listed read-only underneath, because the guest
form has to refuse those the moment they are typed.
-
Operators can block junk guest email domains without a deploy — a new
blocked_email_domains table holds domains no RFC covers (@nomail.com and
the disposable-mailbox addresses couples invent when a form looks like it
wants one). The IETF-reserved TLDs stay in code, where the guest form can
check them instantly and offline. This ships the table on its own; the code
that reads it follows.
-
Bring your guest list from Zola, Withjoy or The Knot — the guest import
now recognises the way other platforms spell their columns ("First Name",
"Email Address", "Given Name"), and when it cannot tell what a column holds it
asks you instead of rejecting the file. Guests who have no email address —
common on lists built for paper invitations — now import too: they appear in
your guest list with a note that they need an email before they can be
invited, instead of being dropped.
-
Update existing guests from a spreadsheet — turn on "Overwrite existing
guests" in the import dialog to refresh names, emails, languages and
plus-ones from your file. You confirm first, and RSVPs and invite links stay
untouched.
-
Imported guests keep their postal address — a guest list exported from a
platform built around paper invitations carries a street address for most
guests. Those columns are now recognised ("Address", "Street", "City",
"Zip", "Postcode" and the usual variants), or you can point them at the
right field yourself, and the address is saved with the guest instead of
being dropped. A row with a city but no street tells you it could not be
saved, rather than losing it quietly.
-
The homepage now shows what couples actually wrote — the reviews section
showed only the Trustpilot score; it now carries the reviews themselves,
swipeable when there is more than one, each linking to the review on
Trustpilot. Reviews are added and published from the admin app, and appear
exactly as they were written.
-
Reviews on the homepage — lumiwed.com now has a reviews section linking
straight to our public Trustpilot profile, and it shows our star rating and
review count there as soon as we publish them.
-
A quieter review ask — the "leave a review" link in the celebration
screen now appears only the first time your site goes live, not on every
update.
-
Mark a guest as invited yourself — if you posted a card, sent a WhatsApp
message or asked someone in person, you can now record that on their row.
They stop showing as waiting to be invited. Nothing is sent, and it does not
affect the timer on email invites. This is the only way to invite a guest who
has no email address, which is common on a list brought over from another
platform.
-
Count children separately on your RSVP — switch it on in Settings and
guests who say yes are asked how many of their party are children, so your
caterer gets an adults-and-children headcount in the vendor pack instead of
one total. Off unless you turn it on, and free on every plan.
-
Simplified Chinese — your wedding website, guest emails, and dashboard now speak 简体中文.
-
A quoted review can now carry the stars the reviewer actually gave — the
homepage band leaned on the overall score above the quotes, which only reads
correctly while every quote is five stars. Reviews can now record their own
rating, so a four-star review can be quoted honestly instead of borrowing the
average or being left out.
-
A vendor pack for your caterer, venue or planner — the Export menu on
Guests can now build one spreadsheet made of the sheets a supplier actually
asks for: headcount per event, meal counts per dietary need, allergies and
written notes word for word, plus-ones, and your full guest list. You pick
which sheets go in, and the whole workbook is written in your wedding's
language rather than always English, so a Spanish caterer at a
Spanish-and-German wedding can read it. Guest contact details are switched
off unless you ask for them, because the pack is made to be forwarded on.
-
Wedding party section — introduce the two people standing beside you. Add
a photo, a few words and social links for each on the Couple page, then place
the new "Wedding party" section wherever you like on your website. Everything
is optional, the bio is translated into every language you publish in, and you
can hide the section per language like any other.
-
The pricing pages now list every Premium feature that is actually switched
on — the comparison table and the plan bullets were only ever showing the
long-standing Premium features, so newer ones stayed invisible to anyone
deciding whether to upgrade. The vendor pack export and per-language sections
and schedule now appear where couples compare the plans.
-
Clearer options when your site is about to come down — the expiry
reminder email now mentions that Premium keeps your site live for a full
year after the wedding, not just one month, alongside the option to extend
your date.
-
Chinese text — names and messages written in Chinese now use a matching font on your wedding site and in guest emails, instead of the computer default.
-
The rich-text editor in the content dashboard is now on the latest version
of its underlying library — a behind-the-scenes upgrade that keeps the
bold/italic/heading/list/quote/link/image formatting working exactly as
before, on a maintained release.
-
As many witnesses as you like — add everyone standing beside you, not just
two, and say whose witness each one is. Your wedding site groups them under
each of your names, and shrinks the photos so they all fit on one row.
-
Demo starter content now says plainly that it is demo content — the
explanation sat in grey prose under a grey label, in the same voice as the
sample cards below it, so the one sentence that mattered read as more sample
content. It is now a highlighted note: "Below is demo content. It disappears
as soon as you add your first moment." The schedule, love story, travel and
story-block sections all say it the same short way.
-
Destination wedding platform guide, rewritten — our destination-wedding
comparison no longer ranks itself first. It now says plainly what The Knot and
WeddingWire do better, adds a capability matrix covering travel pages,
languages, per-guest language, registry and vendor directory, and re-checks
every competitor claim against that vendor's own pages. Updated in all 17
languages.
-
The quick feedback box asks a plain question now — the dashboard's
feedback modal used to open with an internal label, a "Tiny wish, big signal"
headline and a note about analytics tooling that meant nothing to a couple.
It now says "Quick feedback", asks whether the page should do something it
currently does not, and shows the text box and the send button. Translated
into every dashboard language.
-
The reviews on the homepage now look like quotes — a large opening quote
mark sits above each one, the review itself is set in the site's serif at a
slightly larger size, and the reviewer's name is preceded by a dash. The band
read as plain body copy before, so a real quote from a real couple looked like
more of LumiWed's own writing.
-
Round icon buttons are now a full fingertip wide by default — the dismiss
buttons on your dashboard banners, the gallery lightbox arrows and close
button, the photo-adjust toolbar and the feedback button were all drawing at
40px. Twelve of them are now 44px, the size a fingertip expects on a phone,
and the icons inside them are unchanged.
-
Invitations now arrive from you, not from us — a guest's inbox shows
"Anna & Mark via LumiWed" instead of "LumiWed Invitations", and hitting Reply
writes back to your own email address. Replies to reminder emails used to
bounce instead of reaching you.
-
The site-expiry reminder now arrives in your language — the notice we send
before a wedding site comes down used to be written in English for everyone.
It now goes out in whichever of our 17 languages you use, right down to
getting "in 3 days" grammatically correct in each one.
-
Premium feature switches now follow one naming rule — the switches behind
each Premium feature are named the same way everywhere, and the docs list
which ones are live. Nothing changes for couples; it just stops a switch from
being renamed by accident, which would quietly hand a paid feature to
everyone.
-
Publish from any page on your phone — once your site has the basics and
at least one event, a "Publish" button now sits in the top bar on every page
of your dashboard, so you no longer have to go back to the home screen or
open the menu to take your site live.
-
A quoted review now links straight to the review itself — the reviewer's
name on each card opens their own review on Trustpilot, instead of a second
"Read more on Trustpilot" button sitting under the one already below the
quotes. A quote whose source gives us no direct link stays plain text rather
than pointing somewhere that is not it.
-
Leave a review right after you publish — the celebration screen that
appears when your wedding site goes live now links straight to our Trustpilot
page, so you can say publicly how it went. The footer on lumiwed.com links to
the same page.
-
The reviews section on the homepage is easier to act on — the paragraph
explaining the reviews is gone now that the score speaks for itself, and the
main button reads "Read more on Trustpilot" with an icon showing it opens in
a new tab. Updated in all 17 languages.
-
Follow us from the website — the LumiWed site footer now links straight to
our Instagram, TikTok and LinkedIn.
-
Social links are editable — which social profiles the website shows, and
in which order, is now managed from the admin panel.
-
Clearer translation editing — when you open a schedule moment, travel note
or love-story milestone while a guest language is selected, the editor now
says which language you are writing in and offers a one-tap way back to
editing your main language.
-
Copy the original text while translating — the reference text above each
translation field now has a copy button, so you can lift a name, date or
address straight into your translation instead of retyping it.
-
The RSVP confirmation your guests get now matches the invitation — the
receipt we send after someone RSVPs was still going out in the old plain
layout, so a guest could get a beautifully designed invitation and then a
confirmation that looked like it came from somewhere else. It now uses the
same warm design as the rest of your wedding's emails, and what the guest
answered — which events, who they are bringing, dietary needs — is laid out
in the same card the couple sees on their side.
-
Six more emails now look like the rest of LumiWed — the site-published,
publish-reminder, expiry-warning, deletion-confirmation, claim-invite and
Premium partner notes were still going out in the old plain layout, so two
emails from the same wedding could arrive days apart looking like two
different companies. They now use the same warm design as the partner
invitation: same header, same pill button, same spacing.
-
Reminder to invite your guests — if you've added guests but haven't sent
any invites yet, the guest list now shows a reminder with a one-tap button
to send everyone their personal invite at once.
-
Adding a guest by hand — the form no longer says a name is missing when
your phone filled it in for you, and a name typed with stray spaces is tidied
up instead of saved blank.
-
Tidier jumps between sections — tapping a link like "Confirm attendance"
on your wedding site now brings the section fully into view instead of
sliding its top edge under the menu bar.
-
Privacy mode settings — saving your settings from the mobile app now
follows the same Premium rules as the dashboard, instead of keeping its own
copy of them.
-
Updates go live first time — the service behind invitations, RSVPs and
publishing had grown slow enough to start that Cloudflare rejected roughly
half of our deployments, so fixes sometimes waited hours for a retry. It now
starts in well under half the time, and updates land on the first attempt.
-
Guests no longer get asked about events their language never showed — a
moment hidden from, say, your Spanish guests stopped counting as an
unanswered RSVP for them. The guest list, the printed sheet and the CSV and
Excel exports now leave that cell blank instead of reading "Pending" forever,
so you are not chasing replies that could never arrive.
-
Sending a batch of invites — the send button now shows a spinner and locks
while the batch is on its way, so tapping it again cannot start a second run
and send some of your guests a duplicate invite.
-
Calendar days read fully in your language — if you use a screen reader,
the date pickers no longer mix English into an otherwise translated date:
"Today" and "selected" are now spoken in your dashboard language too.
-
Date picker — the day you pick is highlighted again. The selected date, today,
and the ends of a date range had lost their colour, so on a light background the
chosen day was almost invisible.
-
The support chat bubble now honours the size set in the admin console —
Chatwoot ships its own stylesheet that overrode ours, so every size the
operator picked was silently discarded and the bubble always drew at its
stock 64px. It now scales as configured, on phones as well as desktop.
-
A guest who cancels no longer leaves a child behind in the guest list —
declining already deleted the plus-ones they had named, but the number of
children in their party stayed on file, so the list showed a cancelled guest
travelling with one child. Cancelling now clears both.
-
The couple's own edit of that number is bounded by the party — the guest
list accepted more children than there were people in the party, while the
vendor pack quietly capped the same guest, so the two disagreed about the
number the caterer was cooking for. Both now read the same.
-
The children count now corrects what you type — entering a negative or a
half number in a guest's children field snaps it to a sensible value instead
of failing with an error you could do nothing about.
-
Chinese dashboard copy — the shared-access note on the workspace settings
page now speaks to you directly, the way it already does in every other
language, instead of describing the primary admin as someone else.
-
Continue on the Content step — when something is blocking you, we now
scroll straight to it instead of only pointing at the handful of fields we
knew about. And if the detail holding you up has no field on that page, we say
so rather than asking you to hunt for a red one.
-
Failed edits to your schedule and travel notes now say so — if deleting a
timeline moment or a travel note doesn't go through, the entry stays put and a
message explains why, instead of the click quietly doing nothing. The same
goes for editing a travel note.
-
Editing your schedule and travel notes works again on multilingual sites —
the Content page used to open in "translate to your second language" mode, so
the pencil on a moment or travel note showed your own text as a read-only
reference next to an empty translation box. It now opens in your main
language and keeps the language you pick while you move between steps; pick
another language from the switcher when you want to translate.
-
A long editing session no longer loses your text — if you left the
content page open for a while, saving a section could fail with a blunt "Not
authenticated" and your edit was gone. Your browser now quietly renews the
sign-in and saves anyway. If the sign-in really has run out, the message says
so in your own language instead of showing raw technical text.
-
The cookie policy fits your phone screen again — the cookie table stretched
the whole page sideways, so the text beside it ran off the edge and had to be
dragged into view. The page now stays at screen width and the table scrolls on
its own.
-
Country names now follow the dashboard language — the country/origin
picker on the couple page always listed countries in English, so a Spanish
dashboard offered "Spain" and "Germany" instead of "España" and "Alemania".
The list is now named and sorted in the language the couple is reading.
-
The country picker still finds a country by its English name — typing
"Germany" in a Spanish dashboard now surfaces "Alemania", so nobody has to
guess the local spelling of a country they know in English.
-
Your details page always opens now — a single saved value the app no
longer recognised, such as a name-display setting from an older version or a
"show my birthday" switch left on after the date was cleared, could leave the
page stuck on "Couple profiles could not load" with no way past it. The page
now opens with that one value reset to a sensible default, so you can see the
rest of your details and put the odd one right yourself.
-
Dashboard recovers itself after an update — if we ship a new version of
the dashboard while you have it open, opening a page like Design no longer
shows an error screen. The page quietly reloads once and picks up the update.
-
Cookie preferences link works again — the "Cookies" link in the dashboard
sidebar did nothing when clicked. It now opens the cookie page where you can
review or withdraw your consent at any time.
-
Date & time pickers now speak your language — the "Pick a date" and
"Pick a time" hints, the calendar's month and weekday names, and the
picker buttons now follow your dashboard language instead of showing
English.
-
Dropdown menus — fixed a rare crash where a dropdown could send a page
into an endless refresh loop and drop you onto an error screen, mostly on
phones where a password manager or autofill was filling the form for you.
-
Sturdier unsubscribe links — opening an email unsubscribe link that got
mangled by an email client or copied incorrectly now shows a clear "link
invalid" page instead of an error screen.
-
Blank contacts can no longer enter the email campaigns — a malformed
write could create a marketing contact with no address at all, and because
every lifecycle audience is defined by what a couple has not done yet, an
empty contact matched all of them and joined every campaign. Nobody was ever
emailed, since there was no address to email, but the audience counts were
wrong. Contacts without an address are now refused outright and excluded from
every audience.
-
Floating buttons are easier to tap — the round scroll-to-top, language and
preview buttons, and the Next and RSVP pills beside them, were rendering
smaller than the 44px a fingertip needs, so taps near their edge missed. They
now sit at a full 44px on the couple dashboard and on wedding sites.
-
Couples now get their founder welcome in their own language — the email
went out in English to anyone whose language had not yet been recorded, which
in practice meant most new signups. Nothing knew the language at the moment the
account was created, so English was written down as though it were a real
choice, and every later lifecycle email inherited it. The language is now left
blank until the dashboard reports it, and a couple who switches language has
that carried across to their email as well.
-
Guest details are easier to edit on a phone — the salutation, name,
email and side fields in a guest's details are now full-size, matching the
language and dietary fields next to them. They were noticeably smaller and
fiddly to tap. The desktop guest table keeps its compact rows.
-
Importing the same guest list twice no longer doubles it — the import
now recognises a guest who is already on your list by name as well as by
email, tells you clearly which rows were left out, and never changes those
guests unless you ask it to.
-
The guest-import sample now matches your own wedding — the CSV template
and the example in the import box are written with the languages your wedding
actually publishes, so the file you download is one the import will take. And
if a row does name a language you have not selected, the error now says which
languages would work instead of leaving you to guess.
-
Add-your-first-guests shortcut works again — following the "add sample
guests" prompt from your dashboard now opens the import box with the sample
rows in it, instead of the guest list failing to load.
-
Guest import template no longer suggests unusable email addresses — the
downloadable template and the pre-filled sample rows now leave the email
column empty instead of showing example addresses. Importing them
unchanged used to add guests whose invitations could never be sent; now
those rows simply ask you to add an address when you have one.
-
Your guests keep the language they picked — when a guest switches your
wedding site to their own language, it now stays that way after a reload,
including on the invitation-code page they see before the site unlocks.
-
A guest's language is visibly editable again — the language field in a
guest's details is now the same picker you use everywhere else, showing the
flag and the language name. It used to be a small flag on its own, which was
easy to mistake for a label rather than something you could change.
-
Guest sites no longer break when a shared helper is added — the wedding-site
Worker was loading a months-old copy of our shared code, so anything added to it
recently was simply missing at run time and the page failed instead of rendering.
It now always reads the current code, and a new check stops the same mismatch from
reaching a Worker again.
-
More reliable invite links — opening a wedding site with a broken or
tampered invite link now always shows the friendly "invalid invite" page
instead of, in rare cases, an error page with no explanation.
-
A guest link no longer gets blamed for a server hiccup — if your wedding
site briefly has trouble loading a guest's invite, that guest now sees a
proper "something went wrong" message instead of being told their invite
link is invalid and bounced back to enter a new one.
-
Signing in and publishing no longer bounce you back to the sign-in page —
right after a sign-in, your session is briefly still being set up. The
dashboard was reading that half-second as "signed out", so it sent you back to
sign in, and a publish started in that window could throw you out to a
sign-in callback instead of publishing your site. It now waits for the session
to settle and carries on.
-
Two buttons on your phone are now big enough to actually hit — the search
button above your guest list and the menu button in the site preview were
drawing at 36px, small enough to mis-tap on a phone. Both are now 44px, the
size a fingertip expects.
-
Language pickers are easier to tap — every language dropdown in the
dashboard is now a full-size control, matching the other fields around it.
They were slightly too small to hit reliably on a phone.
-
Tapping anywhere on a language row in the content editor now switches that
language on or off — previously only the small toggle itself responded, so
tapping the flag, the language name or the row's padding did nothing, which
is easy to mistake for the page being stuck. Locked rows behave the same way:
the whole row opens the upgrade prompt instead of only the lock icon.
-
Emails greet you by name again — some welcome and lifecycle emails opened
with a bare "Hi," because the couple's name never reached the email system.
The one place the name was recorded sat behind a mailing-list call that could
fail on its own, and once it did nothing ever filled the name back in. The
name is now recorded before anything else can fail, and it is refreshed
whenever an account's name changes.
-
Reminder emails now notice what you have already done — publishing your
site, adding your guests, upgrading to Premium or inviting your partner is
passed straight to the reminder system, so you no longer get a nudge to do
something you finished days ago.
-
Locked fields now look locked — a wedding URL inside its 24-hour cooldown,
and the other fields you cannot edit yet, are shaded instead of looking ready
to type in. No more clicking a field that was never going to accept the change.
-
Easier to tap your way back home — the small "LumiWed" link at the top of
our comparison, city and language guides, and the one in every page footer,
was too small to hit reliably on a phone. The link looks exactly the same, but
now has a full-size tap area around it.
-
Page help "?" button — the header help tip now opens reliably. On a fresh
dashboard it could do nothing when pressed early in setup; it now waits until
your account is ready and then plays the tip.
-
Your partner controls now say they are yours — the note above the Make
primary admin and Remove partner buttons in workspace settings used to say
those actions "stay with the primary admin", which read as somebody else even
when you are the primary admin. It now speaks to you, in all 17 languages.
-
Buttons now show they are working — starting your setup, adding a schedule
item, uploading photos or sending invites now spins the button while it works,
instead of quietly changing its label. You can tell your tap registered.
-
Failed photo uploads no longer disappear — when a photo can't be added to
your gallery, the row telling you which file failed now stays put until you
pick new photos, instead of vanishing a second and a half after the batch
finished.
-
Adding a guest to your RSVP — turning on "I'm bringing a guest" no longer
asks for a name before you have been given the field, the reminder disappears
the moment you start typing one, and a half-typed name no longer blocks the
rest of the form from saving. Answers written at the same moment are now sent
one after another, so a guest is never told their party is over the limit when
it is not.
-
Guided setup — Fixed a bug where simply hovering over the sidebar right after signing up could silently skip your setup interview and create an empty wedding site. The interview now stays available until you choose how to start.
-
No more false "Premium upgrade broken" alarms after an account is deleted —
when a couple opened the Premium checkout, changed their mind and deleted their
account, the abandoned checkout expiring a day later was logged as a failed
upgrade. It is now recognised as the harmless leftover it is.
-
Deleting your account now closes any Premium checkout you left open — an
abandoned payment page can no longer be completed after the account is gone,
and the deletion is recorded in our analytics so the old identity stops
counting as an active couple.
-
Going back from the site preview no longer breaks the page — opening the
preview and then using its "Back" link could land you on a broken Content or
Couple details page instead of the editor. Both pages now wait for their data
before drawing, the way the Design page already did.
-
Publishing while translations run — the Publish button now waits with you
instead of failing. While your site is being translated it stays disabled and
shows how many translations are done, so you are not left clicking Publish and
getting an error until the run finishes.
-
Guest list, guest details and billing always open — a single guest saved
without a last name used to take your whole guest list down with a "could not
load" screen. Those pages now show what is stored and let you fix it, instead
of locking you out until someone repaired the row by hand.
-
The rest of our shared code can no longer be served from a months-old build —
the same mismatch that broke guest sites was still possible for our shared
interface, translation, flag and AI packages, which every app and the mobile app
read from. They now always resolve to the current code, and the check that catches
this runs on every pull request instead of only on request.
-
Switching wedding reminder emails on no longer needs the whole schedule sent
with it — a save that carried only the toggle was refused with "add at least
one reminder", even for a couple whose reminders were already scheduled. The
check now looks at the reminders actually saved for the wedding, so it still
stops reminders being switched on with nothing to send, and now also stops the
schedule being emptied while reminders stay on.
-
Required fields no longer look already filled in — the event title, ceremony
name and venue name showed example text that was easy to mistake for your own
saved wording, so the editor could block publishing over a field that looked
complete. Those examples now read as suggestions ("e.g. …"), and a field that
is required to publish never borrows sample-content text.
-
Answering "No" to a required question — a yes/no RSVP question you marked
as required can now be answered either way. Guests who wanted to say "No" were
stuck on a red error that never cleared, and it quietly blocked their dietary
needs, plus-ones and message from saving too.
-
Guests can see where to type their invitation code — on the RSVP section
of a wedding site the code box was styled as a rounded pill with no label, so
it read as a caption rather than a field, and a guest who submitted it empty
got the explanation as a notification in the far corner of the screen. The
field now carries a visible label, looks like a text box, accepts a pasted
invitation link as well as a bare code, and says what is wrong right beneath
itself.
-
RSVP button that did nothing — when a guest's invite link reached your
wedding site but their RSVP could not be loaded, the "Confirm my attendance"
button appeared and then did nothing at all when tapped. That button is now
withheld in that situation, and the invite-code box is offered instead so the
guest still has a way through.
-
Saved details no longer show up as missing — on some phones, returning to
the couple page (or opening the publish checklist) could show an older,
cached copy of your details and claim required fields were empty even though
they were saved. The dashboard now always loads your latest saved data.
-
The schedule date field no longer shows a calendar icon that does nothing —
when a programme moment had no date yet, a round calendar badge sat at the top
of the field looking like a button, but tapping it never opened anything. It is
gone; the date and time pickers just below it are, and always were, the way to
set the moment.
-
Couple details — Fixed a bug where clicking a sidebar section right after
filling in your couple details bounced you straight back to the couple page.
The app now waits for your last edit to save before it moves you.
-
Signing back in returns you to the page you were opening — if your
sign-in hiccupped while you moved between pages, the dashboard sent you back
to the page you had just left instead of the one you had asked for. Tapping
again repeated it, so it could feel like the button did nothing, and a few
people ended up back at the sign-up screen. You now land on the page you were
actually going to.
-
Taps on your wedding site land first time — the scroll-in animation no
longer briefly hides parts of the page it has already shown, so a guest
tapping a photo, a schedule card or the RSVP button right after the page
loads gets a response instead of nothing.
-
Setting up on your own — the couple details step no longer asks for your
partner's name and country before you can continue. Fill in your own details
and carry on; the only thing still needed is your partner's first name before
you publish your website, and both the couple step and the publish checklist
now say so plainly.
-
Steadier checkout and billing — the payment connection now asks for one
fixed version of Stripe's interface, so a routine library update can no longer
quietly change how upgrades and receipts behave behind the scenes.
-
A saved review in the admin marketing panel no longer looks unsaved — the
row kept the text as typed while the server stored it trimmed, so the Save
button stayed lit and the input showed the old spacing until the page was
reloaded. The row now redraws with whatever was actually stored.
-
Your site no longer claims to be fully translated when a phrase is still
missing — if a translation gave up on one of your texts and a later, smaller
translation run finished cleanly afterwards, your dashboard would settle on
"translated" and never mention the text that never made it. It now keeps
saying a translation is outstanding until that text really has been
translated, so a gap on your guests' site is something you find out about
rather than something you discover later.
-
Turkish guides now name the right number of languages — nine articles said
LumiWed handled up to seven languages when it has long handled 17. They now say
17, and a new check keeps every translated article's figures matching the
English one it came from.
-
Guest addresses that can never receive mail are now caught when they are
entered, not after the invite bounces — placeholder addresses on reserved
domains like @email.test look valid, so they were saved, invited, reminded
and sent RSVP confirmations, each one failing silently at the mail server. The
guest add form now explains the address can never be reached and to share the
invite link instead, the CSV import keeps the guest and drops the address with
a warning, and invites, reminders and confirmations are no longer sent to one.
-
One map per address — when your ceremony and reception share an address,
your wedding site now shows a single map instead of two identical ones.
-
No more empty gap where the venue map should be — a ceremony or reception
saved with a name but no address used to reserve half its card for a map that
never appeared, on your wedding site and in the preview alike. The card now
uses the full width until there is an address to show, and the "Open in Google
Maps" link no longer appears when there is nothing to search for.
-
The couple dashboard builds again — a build-time guard that keeps
server-only loaders out of the browser bundle was reading the source text
Vite ships alongside each chunk, so a single code comment mentioning a
loader by name counted as a leak and failed every build. It now checks the
modules the bundler actually included. No shipped code changes; the guard
still fails when a loader really does reach the browser.
-
A clearer message when a page can't reach your wedding — instead of the
technical string "Forbidden: wedding access denied", the dashboard now says
what to do, in your own language.
-
Friendlier error screen on your wedding site — if your wedding site
hits a hiccup loading, guests now see a clear "please try again" message
instead of a raw technical error.
-
You can change your wedding URL again after an hour, not a day — and the
field now tells you how long is left. Clicking the address while it was
cooling down did nothing at all, which read as a broken field rather than a
locked one. It now answers with the wait time, counted in minutes, and the
wait itself is an hour.
-
Your old wedding URL keeps working after you change it. Renaming your
site used to break every link you had already shared — the previous address
stopped resolving, and nothing stopped another couple from taking it. It is
now reserved for you and forwards to your new address, guest invitation links
and all, until your wedding is archived.
-
Corrected our Wix and Squarespace comparison — the page said neither can
translate a wedding site. Both can, so we now say what is actually true: they
translate once, then the languages drift apart, and a guest still has to pick
their own language from a switcher.