LumiWed Changelog

What's new — August 30, 2026 #

This week's LumiWed product updates.

30 Aug 2026

Weekly

New

Lock guests to their language — on a private site, guests can now be locked to the language you set for them: their site opens in their language and the switcher disappears, so nobody stumbles into content that wasn't written for them. You'll find the toggle next to privacy mode in Settings.
One site, two audiences — keep a section on your English pages and leave it off your Spanish ones. Open the settings next to any section on Design and switch off the languages that don't need it; guests reading those never see the section, in the menu or on the page.
Multicultural weddings guide, now in every language — our article on blending wedding traditions across cultures reads in all 17 languages, not only English.
Preferred source button — you can now mark lumiwed.com as a preferred source in Google Search, from any blog article or the site footer.
A schedule per language — individual moments on your schedule can now be hidden for the languages that don't need them: keep the airport pick-up and the hotel transfer on your English pages while your local guests see a shorter day. Guests who can't see a moment aren't asked to RSVP for it either. You'll find the switches when editing any schedule moment on Content.

Improved

Remove the line above your names — the tagline above your names can now be taken off the page entirely, not just reworded: clear it with the × next to the field under Content → Website Settings. Changed your mind? "Use our default again" brings back the original line in every language.
Tidier language visibility on schedule moments — the per-language switches now live behind a small eye button in the moment's corner (crossed out when a language is hidden), opening the same panel style as the language picker — and they're available from every language view on Content.
Finnish Journal articles read properly in search results — the Finnish multilingual wedding website guides now show a complete title and summary instead of a sentence cut off partway, and the cheaper-tools comparison points you to the full guide when you want more than a price ranking.
Easier to tell our platform comparisons apart — the three Journal round-ups that compare wedding website platforms now show their full titles in search results instead of being cut off, and each one points you to the right companion article when you are answering a different question.
Clearer Journal articles in search results — two guides now carry titles short enough to show in full on Google instead of being cut off mid-sentence, and both answer a common question directly: whether you need a multilingual wedding planner, and whether a Minted wedding website can be published in more than one language.
Language-pair guides now say something useful in every language — the German, French, Polish, Spanish, Italian, Dutch and Portuguese versions of guides like English-French or German-Spanish used to repeat generic advice with the language names swapped. Each one now covers what actually differs for that pair: which ceremony is the legal marriage, the customs guests will not recognise, and how late the celebration really runs.
Language-pair guides now say something useful — the 21 English guides for pairs like English-French or German-Spanish used to repeat the same generic advice with the language names swapped. Each one now covers what actually differs for that pair: which ceremony is the legal marriage, the customs guests will not recognise, and how late the celebration really runs.
Per-language visibility joins Premium — hiding sections or schedule moments for individual languages is now part of the Premium plan. Anything you've already hidden keeps working, and switching a language back on is always free.
Publish straight from the preview — when your site is ready to go live, a small bar now slides up over the preview with a Publish button, so you no longer have to head back to the dashboard once you like what you see. Tap the × to send it away. Rolling out gradually.
Small labels are easier to read — the tiny uppercase captions across the dashboard (guest list cards, guest stats, the sidebar, the premium comparison) were a hair under the size we hold ourselves to, and now all clear it.

Fixed

Fix your partner's name or photo any time — once your partner has joined your wedding, you can still update their name, nickname, photo, and other details from your dashboard. You no longer have to ask them to log in just to fix a typo.
Journal articles no longer show a cut-off summary in Google — every article in all 17 languages now has a search summary short enough to appear in full, instead of stopping mid-sentence. A few German, French, Spanish and Portuguese summaries that read awkwardly have been rewritten properly too.
Journal articles no longer show a cut-off title in Google — every article in all 17 languages now has a title short enough to appear in full in search results. Previously most of them were chopped mid-sentence, so a result could read "Multilingual Wedding Planner: How to Plan a" and stop there.
Steadier wedding-site loads — the wedding date on your guest site's opening screen now settles in cleanly on first load, fixing a brief glitch some guests saw when the page first opened.
Cleaner content editor — the "last saved" time in your content editor now settles in cleanly on first load, fixing a brief glitch some couples saw when the page first opened.
Steadier content editor — the website settings page no longer briefly glitches for couples who recently changed their site link, so the "time left before you can change it again" note now settles in cleanly.
Analytics — page views in the couple dashboard and on wedding sites were only counted when a page was loaded from scratch, so moving between pages inside the app recorded nothing. Every page is counted now.
Delete and self-invite buttons — removing a schedule item, travel tip, love-story moment, content block or RSVP question now shows a spinner while it saves, so a slow connection no longer looks like the click was ignored. The "send myself an invite" button on your guest list does the same.
Internal — the goodwill watchdog now ignores the team's own test sign-ups (mirroring the analytics internal-user filter), so internal testing can never trigger an automatic discount.
Guest invite links — a guest opening an old invite link now sees a friendly "we couldn't find your invitation" screen instead of an error page.
Wedding site reliability — when a guest's invite page fails to load correctly on their phone, we now capture what went wrong instead of losing the report, so we can fix it faster.
Steadier wedding-site loads — the schedule times and love-story dates on your guest site now settle in cleanly on first load, fixing a brief glitch some guests saw (most often on iPhones) when the page first opened.
Add-your-first-guest reminder now actually arrives — couples who finished setting up their wedding without adding any guests yet now get a friendly nudge email pointing them to the guest list.
Legal page links — Privacy, Terms, Cookies, and Imprint links now open the page instead of a "not found" error, wherever you follow them from: the blog, your dashboard, and the sign-up screen. Old links keep working too.
Trust Center — the legal pages now link straight to the Trust Center, so our subprocessors, security, and compliance details are one click away.
Search results show the full description again — on some language-guide and invitation pages the summary Google displays was long enough to get cut off mid-sentence in Czech, Croatian, Romanian and Slovak. The wording is now tighter so the whole line shows.
Sign-in and sign-up buttons stop inviting a second tap — while your details are being checked, the button and the Google/Apple sign-in buttons no longer light up under the cursor as though they were still waiting to be pressed.
Publish button answers straight away — tapping Publish right after opening a page no longer looks like nothing happened: the publish window now appears immediately and fills in as soon as your site details load.
No more double welcome emails — a rare timing issue could send new couples their "welcome to LumiWed" email twice. You'll only get it once now.
Occasional duplicate welcome email — a rare timing race between two signup paths could create your contact record twice, so you'd get the founder welcome note in your inbox twice a few minutes apart. Fixed: only one path can ever process a given signup now.
Onboarding — right after signing up, the guided tour could pop up on top of the first setup questions (language & formats, demo content) and cover the very forms it was pointing at. The tour now reliably waits until both questions are answered. Country dropdowns also open on a typed letter or arrow key now and pick up the letter as the first search character, and tapping the field label opens them too.
Portuguese language-pair guides keep their cover image and translation link — six guides briefly pointed at an image filename that does not exist and at a translation key that no Portuguese post used, which would have shown a broken cover and served the English version to Portuguese readers.
Analytics — the couple dashboard checked which premium features are switched on before the analytics tools knew who the couple was, which counted one couple as two and blurred the numbers behind those features. That check now waits until the couple is identified.
Languages translate right away on Premium — adding a language to a Premium wedding now starts the AI translation immediately, draft or published, instead of quietly waiting for the next publish. The preview also shows its "not translated yet" notice whenever a language has no AI translation (a single hand-edited string used to hide it), and on free weddings the notice now says that publishing is what translates the site.
Analytics — the premium upgrade modal could enter a couple into its layout A/B test before the analytics tools knew who they were, which counted one couple as two and muddied the result. The modal now waits until the couple is identified before picking a variant.
Internal — the two git push safety hooks no longer misread git push origin HEAD. They took the refspec literally and asked the remote about a branch called HEAD, which no remote has: the landed-push guard reported every such push as lost, and the force-with-lease guard blocked pushes to branches that were sitting on the remote all along. Both now resolve HEAD to the branch it stands for, and both still catch the real failures they exist for — a push killed mid-flight, and a lease against a deleted branch.
Language switching from the RSVP card — picking a language inside the RSVP card now switches the whole wedding site with it, so your guests no longer see the page behind it stay in a language they cannot read.
Saving after your session expires — if your dashboard tab was open long enough for the sign-in session to expire, saving a field now tells you "Session expired — please sign in again" in your language instead of showing a generic save error.
Signing in no longer logs you straight back out — when your session was still being set up, the dashboard could decide you were signed out and end the session for good, leaving you stuck on "Loading secure sign-in…" with a valid login. Your session is now kept while it finishes, so signing in carries you through instead of dropping you at the login form.
Invite links open in your guest's language — tapping the magic link in an invite now shows the site's menus, buttons and RSVP form in the language you set for that guest, the way the RSVP page already did. Before, guests who arrived from their invite saw the whole site in the wedding's default language.
Internal — the payment-related background jobs now pin the exact Stripe API version they were tested against, so a future account-level API upgrade cannot quietly change how discount codes are created or how payments are reconciled.
Wedding site menu — on wide screens the menu bar now hugs its links instead of stretching across the page to the language picker.