Lumio v0.74.1

A pull is enough. Only the main server is affected.

Changed

• The "show/hide label" control in the client gallery is now a small eye icon next to the share button, instead of a wide text button on the left of the toolbar. In a presentation gallery there is no sorting dropdown and no filter chips, so the text button ended up standing alone on the left and reading like the page's main action — and on a phone it took up a whole row of its own.
• The control no longer appears in a gallery that has no files yet, where there was nothing to label.

Lumio v0.74.0

A pull is enough — no changes to .env or the compose command. The database migrates automatically on start. Only the main server is affected; worker nodes are unchanged.

Added

• Image labels can now be shown under each photo, in the studio and in the client gallery, and they can be turned off.
  • In the studio it is a per-device preference: a "Filenames" button in the gallery toolbar toggles the filename overlay in the grid, the lightbox and the proofing view. Nobody has to be given permission for this — internally the filename is a working tool, so each team member decides for their own view. The setting has no effect whatsoever on what clients see.
  • In the client gallery it is a per-gallery setting, because the filename carries information there. Three options: none (the previous behaviour), the real filename, or a neutral number ("Image 12 of 84"). The number is meant for the case where clients need to refer to a specific photo — a filename would reveal through its numbering how many shots were culled, and some studios carry internal shoot codes or client names in their filenames.
  • A second switch decides whether clients may show and hide the label themselves. They can only turn the label on and off, never change its type — what is displayed stays the studio's decision.
  • Both settings can be preset in a gallery template.
• The neutral number stays fixed to the gallery order. Filtering or re-sorting in the client gallery does not renumber the photos, so a number a client mentions still points at the same photo later.

Changed

• When a gallery does not show filenames to clients, the filenames are no longer sent to the browser at all, rather than merely being hidden in the display. Otherwise they would still be readable in the browser's network inspector, which defeats the point of hiding them.
• As a consequence, the "Sort by name" option no longer appears in client galleries that do not show filenames — there is nothing to sort by. Existing galleries default to not showing filenames, so this option disappears from them. Set the label to "Filename" for a gallery to get it back.

Lumio v0.73.5

A pull is enough — no changes to .env, the compose command or the database. The worker is affected, so all worker nodes need the update too, after the main server.

Fixed

• Downloading a gallery failed whenever it contained a file larger than 2 GiB — typically video. The download would run for several minutes and then report a generic build error. Cause: the archive entry for each file is opened before its contents are streamed in, and at that moment the packer had no size to go on, so it laid the entry out with 32-bit fields. It only noticed the overflow once the whole file had already been pulled from storage, and aborted. Splitting the gallery into several download packages did not help: a single file always lands whole in one package, no matter how small the size limit is set. The size is now known up front, and large entries use the ZIP64 layout. Archives that only contain photos are unchanged and stay maximally compatible with older unpacking tools.
• The same flaw affected the super-admin recovery archive for deleted objects; fixed alongside.

Lumio v0.73.4

A pull is enough — no changes to .env, the compose command or the database. The frontend is affected, so only the main server.

Fixed

• Opening the download menu in a gallery on a phone and then turning the device made the page flicker rapidly. The menu was capped using the window width, but a menu that overhangs makes the page wider, which changes the window width, which resizes the menu — during the rotation animation, when the browser recalculates continuously, that loop became visible. The menu also kept the alignment it had worked out before the turn, so it could end up on the wrong side. It now re-measures when the device is turned, and its width no longer depends on anything it can itself affect.

Lumio v0.73.3

A pull is enough — no changes to .env, the compose command or the database. Frontend and API are affected, so only the main server.

Fixed

• The print provider configuration fields showed German labels and help texts whatever language was selected — the currency field and the sandbox switch, along with their explanations. Technical names such as "API-Key" and "Client-ID" deliberately stay as they are.

Lumio v0.73.2

A pull is enough — no changes to .env, the compose command or the database. Frontend and API are affected, so only the main server.

Fixed

• The download menu in a gallery ran off the left edge of the screen on a phone, cutting off the first entry. The menu now works out which way it can open from where the button actually is, which matters because the toolbar wraps: how many actions are visible decides whether the button ends up mid-row or at the start of the next one. The gallery tile menu in the studio had the same arrangement and is fixed too.
• The engagement funnel under gallery statistics stayed German whatever language was selected — the heading and all four step labels. The steps come from the API, which is the third time a set of API-supplied labels has shipped untranslated.
• The dictionary check now also scans the API for the shape of an untranslated catalogue — a stable key next to a German label — rather than only checking the handful of files someone remembered to list. That is what would have caught this one, and it also turned up the print provider configuration fields.

Lumio v0.73.1

A pull is enough — no changes to .env, the compose command or the database. The frontend is affected, so only the main server.

Fixed

• The language setting was labelled "Language / Sprache" whatever language you were using, and its explanation was English only. German was there because there were once two languages; with four it just meant a Finnish studio was shown German. The heading now reads English plus your own language — "Language / Kieli" — and the explanation appears in both. The option names stay untranslated ("Suomi", not "Finnish"), which is the convention and the thing that actually helps someone who landed in a language they cannot read.
• The dictionary check was comparing German and Italian against English by name, so Finnish was not being checked at all and an incomplete file would have passed in silence. The list of languages now comes from the code.

Lumio v0.73.0

A pull is enough — no changes to .env, the compose command or the database. Frontend and API are affected, so only the main server.

Added

• Finnish is now available, for the interface and for email alike. All 2567 interface strings and 340 mail phrases translated, with dates, numbers and currency following Finnish convention. Contributed by @canja006.

Fixed

• The dictionary check was only comparing German and Italian against English by name, so a newly added language could have shipped incomplete without anything noticing. It now takes the list of languages from the code, so the next one is covered automatically.

Added

• scripts/lumio-check-ports.sh checks Lumio's ten TCP/UDP ports against the host before docker compose up, and offers to write an alternative into .env where a port has a dedicated variable. Without it a port conflict shows up as a container that quietly refuses to bind rather than as an error you can act on. Documented in docs/PORT-CHECK.md. Contributed by @manuzzi.

Lumio v0.72.0

A pull is enough — no changes to .env, the compose command or the database. Frontend and API are affected, so only the main server.

Added

• Emails are now available in Italian. All 338 mail phrases translated, so an Italian studio gets an Italian interface and Italian mail — the gap that remained after the interface translation landed. Contributed by @manuzzi.
• Italian can now be selected as the mail language, both for your own notifications and for the mail your customers receive.

Fixed

• Two lines in the print shop mails were German whatever language was selected — a heading and a closing line that never went through the translation layer at all. Found while translating around them.

Lumio v0.71.1

Pull genügt — keine Änderungen an .env, am Compose-Befehl oder an der Datenbank. Betroffen ist die API, also nur der Hauptserver.

A pull is enough — no changes to .env, the compose command or the database. The API is affected, so only the main server.

Fixed

• E-Mails kamen im Rahmen weiterhin in der Vorgabesprache der Instanz, auch wenn der Inhalt übersetzt war: Fußzeile und die Sprachkennzeichnung der Mail folgten nicht der angeschriebenen Person. Eine englische Mail auf einer deutschen Instanz hatte also englischen Text in deutschem Rahmen — was auch Vorleseprogramme und Spamfilter falsch informierte. Gemeldet und behoben von @manuzzi.

🇬🇧 English

• Emails still used the instance default language for their frame even when the content was translated: the footer and the mail's language attribute did not follow the recipient. An English mail on a German instance had English text in a German frame, which also misinformed screen readers and spam filters. Reported and fixed by @manuzzi.