RegiBase - Releases

Encryption (master key)

• Reworked master-key management: set/change, remove (back to plain text), and sign-out are now clearly separated; terminology unified to "master key".
• Secret fields are now encrypted automatically when a collection's secret flag changes (background sweep) — the manual re-encrypt option was removed.
• New occ command regibase:master (status | set | change | remove).

Search & replace

• In-collection search can now use regular expressions (server-side PCRE: case-sensitive, (?i) supported, Unicode-aware).
• New Replace: bulk-replace text across matched records ($1 group references, undoable from Snapshots).
• Regex help ("?" chip): a two-page reference — token list plus worked examples.
• New occ option regibase:find --regex.

Snapshots (formerly Undo)

• "Undo" renamed to "Snapshots"; scope changed from a single global timeline to per-collection. Opened from ⚙️ Collection settings; roll back to any point. Richer summaries with icons and hover detail.

Display & editor

• Columns with no data are shown with a faint header in the list view.
• Each field shows a "filled / total" record count in the collection editor.
• Concatenation can wrap the target in parentheses (half- or full-width); fixed parentheses disappearing when a field was empty.

Layout & fixes

• The sort control ("Sort") moved next to Duplicate; search/replace box relaid out (aligned left edges, wraps on narrow widths).
• Fixed dark-mode select text being invisible and an oversized hover box.

Concatenation (display combining) — reworked

• In the collection editor, each field can pick a Concatenate with target — the next field to show it combined with — and its own separator (none / half-width space / full-width space / custom symbol) placed between them. Chain fields (A→B→C) for a 3-/4-way combine, e.g. last name → first name → “Yamada Taro”, or furigana last → first as a second group.
• The field being combined into shows a “Concatenated from …” note; combined columns are marked with 🔗 and pulled to the front in the table view, and appear as one item in the detailed list.
• This only changes how records are displayed — the stored data is never merged. (Field names are now required.)

Fixes

• Deleting a whole collection can now be undone — the ↶ Undo button appears after a collection delete.
• Switching the view or sort order no longer fills up the change history.

Undo & change history

• Every change — records, fields, collections, imports and moves — is now recorded and can be reverted with Ctrl+Z or the ↶ Undo button in the toolbar. A whole schema save (field changes together with any record-data migration) is undone in a single step.
• Settings has a change-history view and a configurable retention limit (default 100 changes; set 0 to turn history off). Changes beyond the limit are discarded oldest-first.

New field types

• Choices (radio) — pick one option from a set of radio buttons.
• Choices (checkboxes) — pick several options; the selected values are stored together.
• The previous Choices type is now labelled Choices (dropdown).

Concatenation groups

• In the collection editor each field can be given a Concatenate group number. Fields sharing a group are shown combined — joined in field order — as one column (table view) or one line (detailed list), e.g. last name + first name, and furigana last + first as a second group. This is independent of the Emphasis (title) setting; combined columns are pulled to the front.

Also included since the last release (0.14.x)

• Emphasis (record name): the list-title marker is now 🏷️ Emphasis (previously “★ Title”), and more than one field can be a key — their values combine in field order to form the record's name (e.g. first + last name), shown in bold, and optionally as one leading column in the table view with a chosen separator.
• New collections open in the table view by default.
• The collection editor is titled Edit collection; its field list auto-scrolls while you drag to reorder.
• Supports Nextcloud 33.
• Fix: reordering fields right after renaming one could prune that field's record data on save.

Emphasis (record name) fields

• The list-title marker was renamed to 🏷️ Emphasis, and a field list can now have more than one. When several fields are emphasized, their values are combined in field order to form the record's name (for example first name + last name), skipping any empty parts. Emphasized values are shown in bold. (The marker was previously “★ Title”.)
• Collection settings can combine the emphasized field(s) into a single leading column in the table view, with a chosen separator — none, a half-width space, a full-width space (offered for CJK languages), or a custom symbol.

Editing

• New collections now open in the table (spreadsheet) view by default.
• The collection editor is titled Edit collection, with a short note on what it changes.
• While reordering fields by drag in the collection editor, the list now auto-scrolls when the pointer nears the top or bottom edge.

Compatibility

• Supports Nextcloud 33.

Fixes

• Reordering fields by drag in the collection editor right after renaming one could, on save, leave a field's data mismatched and prune it. Field keys are now kept pinned to their field regardless of order, and the edited field is committed before a drag begins.

Edit lock (view-only collections)

• A collection's settings now include an Edit lock. While it is on, the collection is view-only: records and fields cannot be added, edited or deleted, and a 🔒 mark is shown next to it in the collection list. It is enforced on the server, not only in the interface.

Field editing

• Changing a field's type or its Secret setting, or removing a field, now migrates the existing record data instead of leaving it inconsistent: values are decrypted when Secret is turned off and encrypted when it is turned on; values that no longer fit the new type are cleared; a Select field keeps existing out-of-range values by adding them to its choices; and data and attachments left by removed fields are cleaned up.
• The effects are listed in a single confirmation first. Any change that deletes data now needs a checkbox confirmation rather than a single click.

Encryption

• Settings has a Re-encrypt secret fields action for secret values still stored as plain text (for example when encryption was enabled later). Turning a field into a secret field also offers to encrypt its existing values.
• The encryption section of Settings was rearranged so each action has a short description.

Fixes

• Sorting a field of dotted values such as IP addresses treated them all as the same number and left them unsorted; they now sort in natural order.

Address field type

• The map link is now a dedicated Address field type instead of a per-field checkbox. Pick the Address type and its value gets a 🌐 button that opens it in your chosen map service (Google Maps / OpenStreetMap / Apple Maps). The built-in templates and the Contacts import now use this type for address fields.
• The map button uses a clearer 🌐 (globe) icon and sits before the copy button.

Reminders in your Calendar, and map links for addresses

• Add a reminder from a date. Date and year/month fields now show a 📅 button in the record detail. It opens Nextcloud Calendar's own new-event editor (in a popup) prefilled with that date as an all-day event, where you set the title, reminders and repeat and save. The button is shown but disabled when the Calendar app is not enabled.
• Map links for addresses. A new per-field option, 🗺 Map link, can be turned on for text fields (for example an address). Such fields show a 🗺 button in the record detail that opens the value in a map. Choose the map service — Google Maps, OpenStreetMap or Apple Maps — in Settings.

Fix: fields could share one value

Adding several fields at once — most often when their labels were non-Latin (Japanese, Chinese, and so on) — could give them the same internal key. Fields that share a key also share a single value, so editing one (for example a date) filled the others with the same entry. Field keys are now guaranteed unique at three levels: the client's key generator no longer collides within a single pass, the schema editor de-duplicates keys on save, and — the decisive guard — the server enforces uniqueness at the one place every field is written, so no import, restore, or future client regression can reintroduce a collision. Existing collections already affected are repaired by giving their duplicated fields distinct keys.

Password generator: choose the symbols and set per-class min/max

The generator now gives the same fine control KeePass does, with the constraints kept mutually consistent so you can never configure a request it cannot fulfil.

• Choose which symbols are allowed. The full symbol palette is shown as a grid; tap to include or exclude each one, with All / None shortcuts. Only the symbols you keep can appear. (A symbol that is also a look-alike, such as |, is struck through while "exclude look-alike characters" is on.)
• Minimum and maximum occurrences per character type. Each of uppercase, lowercase, digits and symbols has its own min and max. "min 2 / max 4 digits", "at least one symbol", "no more than one uppercase" — all expressible. A blank max means no limit.
• Exclusive (mutually-consistent) handling. Every change is reconciled so the request stays generatable: a max is never below its own min, the total of the minimums never exceeds the field's ceiling, and the length is clamped into the window the minimums and maximums allow. The length slider's own floor and ceiling move with the constraints, so an impossible combination simply cannot be entered.
• Guarantees hold exactly: with 5000 sample draws, every minimum is always met, no maximum is ever exceeded, and min == max produces exactly that count.
• Your choices (symbol set, per-class min/max, length) are remembered between uses, and a field's own input rule still wins — a digits-only or hexadecimal field ignores the controls that do not apply to it.

Emoji are drawn by the app, not by the viewer's device

0.12.11 bundled the full emoji set but kept it as a fallback behind the device's own font. That does not fix flags, and the reason is worth writing down: Segoe UI Emoji has glyphs for the regional indicator letters. It reports 🇯 and 🇵 as covered and simply draws them as two boxed letters instead of forming 🇯🇵 — so nothing is "missing", the browser never falls through, and the bundled font was never even downloaded. Taking only the flag code points away from the device font does not work either: U+200D has to travel with them or 🏳️‍🌈 🏳️‍⚧️ 🏴‍☠️ split into a bare flag, and once U+200D belongs to a different font than the base character, every ZWJ emoji comes apart — families, couples, professions, hair colours.

• All 1,849 emoji are now rendered from the bundled Noto Color Emoji subset (SIL OFL 1.1), on every platform. A device's own emoji font is kept behind it only as a safety net for a failed download.
• Verified on three simulated devices — a complete emoji font, a Windows-like one (has the regional indicator glyphs but cannot form flags), and none at all: all 1,849 render identically in each, flags and ZWJ sequences included.
• The font applies only to the elements that display an icon, so the app's own UI keeps the platform look and body text is untouched — characters such as © ® ™ ↔ stay plain text.
• Cost: one cached 1.7 MB download. Collections are shared, so consistent rendering is the point — everyone now sees the icon the person who picked it saw.

Emoji no longer depend on the viewer's device

0.12.10 shipped a flag-only font, which treated the symptom. The cause is that the app was letting whatever emoji font a device happens to ship decide whether an icon is readable — and flags are simply where that shows up first, because Windows has no flag glyphs on any version (Segoe UI Emoji draws 🇯🇵 as a boxed "JP" and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, a deliberate omission that updates will not fix). The same gap hits anything newer than the device's font: Segoe UI Emoji only gained the Unicode 13/14 additions (🫠 🫰 🫡 …) in Windows 11 22H2. Collections get shared, so an icon has to survive being viewed on someone else's screen.

• RegiBase now carries all 1,849 emoji it offers, as a subset of Noto Color Emoji (SIL OFL 1.1) — the vector COLRv1 build, 1.7 MB where the bitmap build of the same coverage would be 4.4 MB.
• It is a fallback, not a replacement: the first @font-face is local() only and names the platform emoji fonts, so a device with a complete font uses its own and downloads nothing. Font fallback reaches the bundled file only for the glyphs the platform font turned out to be missing, and the browser caches it from then on.
• Measured on three simulated devices — complete emoji font: never fetched; Windows-like (emoji font present, no flags): fetched the first time a flag is drawn, not on app start; no emoji font at all: fetched on load, and every one of the 1,849 renders.
• The font pair applies only to the elements that display an icon, never to body text, so characters such as © ® ™ ↔ stay plain text everywhere else.

Flags now render on Windows

• Windows ships no flag glyphs: Segoe UI Emoji draws 🇯🇵 as a boxed "JP" letter pair and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, so the 269 flags in the icon picker were unusable there. RegiBase now carries a flag-only subset of Noto Color Emoji (SIL OFL 1.1) and declares it with a unicode-range limited to the flag code points: the browser fetches the file the first time a flag is actually drawn — not on app start — and then caches it. Every other emoji still comes from the system font, so nothing else changes.

The icon picker now holds every Unicode emoji

• The collection icon picker used to offer a hand-picked 425 emoji. It now contains the complete Unicode 14.0 set — 1,849 emoji, in the nine official Unicode groups (Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, Flags), in the official emoji-ordering sequence. Flags, arrows, numbers, professions, hair variants, family and couple sequences — all of them are now selectable. (Skin-tone variants are not listed separately, matching the Unicode emoji-ordering chart itself.) The curated Recommended set stays as the first tab.
• Search box: type to filter across all 1,849 by name or keyword, in your own language (CLDR names for all 12 UI languages). Japanese search is kana-insensitive, so "ねこ" finds ネコの顔.
• Group tabs replace one long scroll, and hovering an emoji shows its name.
• The emoji set is fetched only when the picker is first opened, so the app starts just as fast as before.
• The icon input accepts longer sequences (16 units instead of 8, and 16 instead of 4 in the CSV/JSON import step), so multi-codepoint emoji such as 🏴󠁧󠁢󠁷󠁬󠁳󠁿 or 👩‍❤️‍💋‍👩 can be typed or pasted without being cut off.

Translations

• The emoji category names and the picker tooltip were only translated into Japanese and English; they are now translated into all 12 languages.
• Fixed: Click to choose an icon was stored outside the translations block of l10n/ja.json and l10n/en.json, so it stayed English whenever the in-app language selector was used.

The picker is now available everywhere an icon is set

• The icon picker used to exist only in collection settings. It is now offered in the CSV / JSON import, the Contacts import, the Tables import and the template editor as well — the same picker, shared, so it always shows the same 1,849 emoji. Contacts and Tables imports previously had no icon field at all and always produced 👤 / the table's own emoji; you can now choose one up front.

Fixed: the Nextcloud user-status menu was broken on RegiBase pages

• RegiBase loads the "global" build of the Vue 3 runtime, which publishes window.Vue. A third-party library bundled into Nextcloud core (vue-resize) auto-installs into that global with the Vue 2 API — window.Vue.use(...) — which throws on a Vue 3 namespace and aborted the script that renders the user-status menu. RegiBase now keeps its Vue copy private and leaves window.Vue untouched.

• The collection list in the left sidebar can now be reordered by drag & drop. Drop targets are highlighted while dragging, and the new order is saved immediately (no save button). Collections shared with you by other users are not draggable.

Encryption (master key)

• Reworked master-key management: set/change, remove (back to plain text), and sign-out are now clearly separated; terminology unified to "master key".
• Secret fields are now encrypted automatically when a collection's secret flag changes (background sweep) — the manual re-encrypt option was removed.
• New occ command regibase:master (status | set | change | remove).

Search & replace

• In-collection search can now use regular expressions (server-side PCRE: case-sensitive, (?i) supported, Unicode-aware).
• New Replace: bulk-replace text across matched records ($1 group references, undoable from Snapshots).
• Regex help ("?" chip): a two-page reference — token list plus worked examples.
• New occ option regibase:find --regex.

Snapshots (formerly Undo)

• "Undo" renamed to "Snapshots"; scope changed from a single global timeline to per-collection. Opened from ⚙️ Collection settings; roll back to any point. Richer summaries with icons and hover detail.

Display & editor

• Columns with no data are shown with a faint header in the list view.
• Each field shows a "filled / total" record count in the collection editor.
• Concatenation can wrap the target in parentheses (half- or full-width); fixed parentheses disappearing when a field was empty.

Layout & fixes

• The sort control ("Sort") moved next to Duplicate; search/replace box relaid out (aligned left edges, wraps on narrow widths).
• Fixed dark-mode select text being invisible and an oversized hover box.

Concatenation (display combining) — reworked

• In the collection editor, each field can pick a Concatenate with target — the next field to show it combined with — and its own separator (none / half-width space / full-width space / custom symbol) placed between them. Chain fields (A→B→C) for a 3-/4-way combine, e.g. last name → first name → “Yamada Taro”, or furigana last → first as a second group.
• The field being combined into shows a “Concatenated from …” note; combined columns are marked with 🔗 and pulled to the front in the table view, and appear as one item in the detailed list.
• This only changes how records are displayed — the stored data is never merged. (Field names are now required.)

Fixes

• Deleting a whole collection can now be undone — the ↶ Undo button appears after a collection delete.
• Switching the view or sort order no longer fills up the change history.

Undo & change history

• Every change — records, fields, collections, imports and moves — is now recorded and can be reverted with Ctrl+Z or the ↶ Undo button in the toolbar. A whole schema save (field changes together with any record-data migration) is undone in a single step.
• Settings has a change-history view and a configurable retention limit (default 100 changes; set 0 to turn history off). Changes beyond the limit are discarded oldest-first.

New field types

• Choices (radio) — pick one option from a set of radio buttons.
• Choices (checkboxes) — pick several options; the selected values are stored together.
• The previous Choices type is now labelled Choices (dropdown).

Concatenation groups

• In the collection editor each field can be given a Concatenate group number. Fields sharing a group are shown combined — joined in field order — as one column (table view) or one line (detailed list), e.g. last name + first name, and furigana last + first as a second group. This is independent of the Emphasis (title) setting; combined columns are pulled to the front.

Also included since the last release (0.14.x)

• Emphasis (record name): the list-title marker is now 🏷️ Emphasis (previously “★ Title”), and more than one field can be a key — their values combine in field order to form the record's name (e.g. first + last name), shown in bold, and optionally as one leading column in the table view with a chosen separator.
• New collections open in the table view by default.
• The collection editor is titled Edit collection; its field list auto-scrolls while you drag to reorder.
• Supports Nextcloud 33.
• Fix: reordering fields right after renaming one could prune that field's record data on save.

Emphasis (record name) fields

• The list-title marker was renamed to 🏷️ Emphasis, and a field list can now have more than one. When several fields are emphasized, their values are combined in field order to form the record's name (for example first name + last name), skipping any empty parts. Emphasized values are shown in bold. (The marker was previously “★ Title”.)
• Collection settings can combine the emphasized field(s) into a single leading column in the table view, with a chosen separator — none, a half-width space, a full-width space (offered for CJK languages), or a custom symbol.

Editing

• New collections now open in the table (spreadsheet) view by default.
• The collection editor is titled Edit collection, with a short note on what it changes.
• While reordering fields by drag in the collection editor, the list now auto-scrolls when the pointer nears the top or bottom edge.

Compatibility

• Supports Nextcloud 33.

Fixes

• Reordering fields by drag in the collection editor right after renaming one could, on save, leave a field's data mismatched and prune it. Field keys are now kept pinned to their field regardless of order, and the edited field is committed before a drag begins.

Edit lock (view-only collections)

• A collection's settings now include an Edit lock. While it is on, the collection is view-only: records and fields cannot be added, edited or deleted, and a 🔒 mark is shown next to it in the collection list. It is enforced on the server, not only in the interface.

Field editing

• Changing a field's type or its Secret setting, or removing a field, now migrates the existing record data instead of leaving it inconsistent: values are decrypted when Secret is turned off and encrypted when it is turned on; values that no longer fit the new type are cleared; a Select field keeps existing out-of-range values by adding them to its choices; and data and attachments left by removed fields are cleaned up.
• The effects are listed in a single confirmation first. Any change that deletes data now needs a checkbox confirmation rather than a single click.

Encryption

• Settings has a Re-encrypt secret fields action for secret values still stored as plain text (for example when encryption was enabled later). Turning a field into a secret field also offers to encrypt its existing values.
• The encryption section of Settings was rearranged so each action has a short description.

Fixes

• Sorting a field of dotted values such as IP addresses treated them all as the same number and left them unsorted; they now sort in natural order.

Address field type

• The map link is now a dedicated Address field type instead of a per-field checkbox. Pick the Address type and its value gets a 🌐 button that opens it in your chosen map service (Google Maps / OpenStreetMap / Apple Maps). The built-in templates and the Contacts import now use this type for address fields.
• The map button uses a clearer 🌐 (globe) icon and sits before the copy button.

Reminders in your Calendar, and map links for addresses

• Add a reminder from a date. Date and year/month fields now show a 📅 button in the record detail. It opens Nextcloud Calendar's own new-event editor (in a popup) prefilled with that date as an all-day event, where you set the title, reminders and repeat and save. The button is shown but disabled when the Calendar app is not enabled.
• Map links for addresses. A new per-field option, 🗺 Map link, can be turned on for text fields (for example an address). Such fields show a 🗺 button in the record detail that opens the value in a map. Choose the map service — Google Maps, OpenStreetMap or Apple Maps — in Settings.

Fix: fields could share one value

Adding several fields at once — most often when their labels were non-Latin (Japanese, Chinese, and so on) — could give them the same internal key. Fields that share a key also share a single value, so editing one (for example a date) filled the others with the same entry. Field keys are now guaranteed unique at three levels: the client's key generator no longer collides within a single pass, the schema editor de-duplicates keys on save, and — the decisive guard — the server enforces uniqueness at the one place every field is written, so no import, restore, or future client regression can reintroduce a collision. Existing collections already affected are repaired by giving their duplicated fields distinct keys.

Password generator: choose the symbols and set per-class min/max

The generator now gives the same fine control KeePass does, with the constraints kept mutually consistent so you can never configure a request it cannot fulfil.

• Choose which symbols are allowed. The full symbol palette is shown as a grid; tap to include or exclude each one, with All / None shortcuts. Only the symbols you keep can appear. (A symbol that is also a look-alike, such as |, is struck through while "exclude look-alike characters" is on.)
• Minimum and maximum occurrences per character type. Each of uppercase, lowercase, digits and symbols has its own min and max. "min 2 / max 4 digits", "at least one symbol", "no more than one uppercase" — all expressible. A blank max means no limit.
• Exclusive (mutually-consistent) handling. Every change is reconciled so the request stays generatable: a max is never below its own min, the total of the minimums never exceeds the field's ceiling, and the length is clamped into the window the minimums and maximums allow. The length slider's own floor and ceiling move with the constraints, so an impossible combination simply cannot be entered.
• Guarantees hold exactly: with 5000 sample draws, every minimum is always met, no maximum is ever exceeded, and min == max produces exactly that count.
• Your choices (symbol set, per-class min/max, length) are remembered between uses, and a field's own input rule still wins — a digits-only or hexadecimal field ignores the controls that do not apply to it.

Emoji are drawn by the app, not by the viewer's device

0.12.11 bundled the full emoji set but kept it as a fallback behind the device's own font. That does not fix flags, and the reason is worth writing down: Segoe UI Emoji has glyphs for the regional indicator letters. It reports 🇯 and 🇵 as covered and simply draws them as two boxed letters instead of forming 🇯🇵 — so nothing is "missing", the browser never falls through, and the bundled font was never even downloaded. Taking only the flag code points away from the device font does not work either: U+200D has to travel with them or 🏳️‍🌈 🏳️‍⚧️ 🏴‍☠️ split into a bare flag, and once U+200D belongs to a different font than the base character, every ZWJ emoji comes apart — families, couples, professions, hair colours.

• All 1,849 emoji are now rendered from the bundled Noto Color Emoji subset (SIL OFL 1.1), on every platform. A device's own emoji font is kept behind it only as a safety net for a failed download.
• Verified on three simulated devices — a complete emoji font, a Windows-like one (has the regional indicator glyphs but cannot form flags), and none at all: all 1,849 render identically in each, flags and ZWJ sequences included.
• The font applies only to the elements that display an icon, so the app's own UI keeps the platform look and body text is untouched — characters such as © ® ™ ↔ stay plain text.
• Cost: one cached 1.7 MB download. Collections are shared, so consistent rendering is the point — everyone now sees the icon the person who picked it saw.

Emoji no longer depend on the viewer's device

0.12.10 shipped a flag-only font, which treated the symptom. The cause is that the app was letting whatever emoji font a device happens to ship decide whether an icon is readable — and flags are simply where that shows up first, because Windows has no flag glyphs on any version (Segoe UI Emoji draws 🇯🇵 as a boxed "JP" and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, a deliberate omission that updates will not fix). The same gap hits anything newer than the device's font: Segoe UI Emoji only gained the Unicode 13/14 additions (🫠 🫰 🫡 …) in Windows 11 22H2. Collections get shared, so an icon has to survive being viewed on someone else's screen.

• RegiBase now carries all 1,849 emoji it offers, as a subset of Noto Color Emoji (SIL OFL 1.1) — the vector COLRv1 build, 1.7 MB where the bitmap build of the same coverage would be 4.4 MB.
• It is a fallback, not a replacement: the first @font-face is local() only and names the platform emoji fonts, so a device with a complete font uses its own and downloads nothing. Font fallback reaches the bundled file only for the glyphs the platform font turned out to be missing, and the browser caches it from then on.
• Measured on three simulated devices — complete emoji font: never fetched; Windows-like (emoji font present, no flags): fetched the first time a flag is drawn, not on app start; no emoji font at all: fetched on load, and every one of the 1,849 renders.
• The font pair applies only to the elements that display an icon, never to body text, so characters such as © ® ™ ↔ stay plain text everywhere else.

Flags now render on Windows

• Windows ships no flag glyphs: Segoe UI Emoji draws 🇯🇵 as a boxed "JP" letter pair and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, so the 269 flags in the icon picker were unusable there. RegiBase now carries a flag-only subset of Noto Color Emoji (SIL OFL 1.1) and declares it with a unicode-range limited to the flag code points: the browser fetches the file the first time a flag is actually drawn — not on app start — and then caches it. Every other emoji still comes from the system font, so nothing else changes.

The icon picker now holds every Unicode emoji

• The collection icon picker used to offer a hand-picked 425 emoji. It now contains the complete Unicode 14.0 set — 1,849 emoji, in the nine official Unicode groups (Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, Flags), in the official emoji-ordering sequence. Flags, arrows, numbers, professions, hair variants, family and couple sequences — all of them are now selectable. (Skin-tone variants are not listed separately, matching the Unicode emoji-ordering chart itself.) The curated Recommended set stays as the first tab.
• Search box: type to filter across all 1,849 by name or keyword, in your own language (CLDR names for all 12 UI languages). Japanese search is kana-insensitive, so "ねこ" finds ネコの顔.
• Group tabs replace one long scroll, and hovering an emoji shows its name.
• The emoji set is fetched only when the picker is first opened, so the app starts just as fast as before.
• The icon input accepts longer sequences (16 units instead of 8, and 16 instead of 4 in the CSV/JSON import step), so multi-codepoint emoji such as 🏴󠁧󠁢󠁷󠁬󠁳󠁿 or 👩‍❤️‍💋‍👩 can be typed or pasted without being cut off.

Translations

• The emoji category names and the picker tooltip were only translated into Japanese and English; they are now translated into all 12 languages.
• Fixed: Click to choose an icon was stored outside the translations block of l10n/ja.json and l10n/en.json, so it stayed English whenever the in-app language selector was used.

The picker is now available everywhere an icon is set

• The icon picker used to exist only in collection settings. It is now offered in the CSV / JSON import, the Contacts import, the Tables import and the template editor as well — the same picker, shared, so it always shows the same 1,849 emoji. Contacts and Tables imports previously had no icon field at all and always produced 👤 / the table's own emoji; you can now choose one up front.

Fixed: the Nextcloud user-status menu was broken on RegiBase pages

• RegiBase loads the "global" build of the Vue 3 runtime, which publishes window.Vue. A third-party library bundled into Nextcloud core (vue-resize) auto-installs into that global with the Vue 2 API — window.Vue.use(...) — which throws on a Vue 3 namespace and aborted the script that renders the user-status menu. RegiBase now keeps its Vue copy private and leaves window.Vue untouched.

• The collection list in the left sidebar can now be reordered by drag & drop. Drop targets are highlighted while dragging, and the new order is saved immediately (no save button). Collections shared with you by other users are not draggable.

Encryption (master key)

• Reworked master-key management: set/change, remove (back to plain text), and sign-out are now clearly separated; terminology unified to "master key".
• Secret fields are now encrypted automatically when a collection's secret flag changes (background sweep) — the manual re-encrypt option was removed.
• New occ command regibase:master (status | set | change | remove).

Search & replace

• In-collection search can now use regular expressions (server-side PCRE: case-sensitive, (?i) supported, Unicode-aware).
• New Replace: bulk-replace text across matched records ($1 group references, undoable from Snapshots).
• Regex help ("?" chip): a two-page reference — token list plus worked examples.
• New occ option regibase:find --regex.

Snapshots (formerly Undo)

• "Undo" renamed to "Snapshots"; scope changed from a single global timeline to per-collection. Opened from ⚙️ Collection settings; roll back to any point. Richer summaries with icons and hover detail.

Display & editor

• Columns with no data are shown with a faint header in the list view.
• Each field shows a "filled / total" record count in the collection editor.
• Concatenation can wrap the target in parentheses (half- or full-width); fixed parentheses disappearing when a field was empty.

Layout & fixes

• The sort control ("Sort") moved next to Duplicate; search/replace box relaid out (aligned left edges, wraps on narrow widths).
• Fixed dark-mode select text being invisible and an oversized hover box.

Concatenation (display combining) — reworked

• In the collection editor, each field can pick a Concatenate with target — the next field to show it combined with — and its own separator (none / half-width space / full-width space / custom symbol) placed between them. Chain fields (A→B→C) for a 3-/4-way combine, e.g. last name → first name → “Yamada Taro”, or furigana last → first as a second group.
• The field being combined into shows a “Concatenated from …” note; combined columns are marked with 🔗 and pulled to the front in the table view, and appear as one item in the detailed list.
• This only changes how records are displayed — the stored data is never merged. (Field names are now required.)

Fixes

• Deleting a whole collection can now be undone — the ↶ Undo button appears after a collection delete.
• Switching the view or sort order no longer fills up the change history.

Undo & change history

• Every change — records, fields, collections, imports and moves — is now recorded and can be reverted with Ctrl+Z or the ↶ Undo button in the toolbar. A whole schema save (field changes together with any record-data migration) is undone in a single step.
• Settings has a change-history view and a configurable retention limit (default 100 changes; set 0 to turn history off). Changes beyond the limit are discarded oldest-first.

New field types

• Choices (radio) — pick one option from a set of radio buttons.
• Choices (checkboxes) — pick several options; the selected values are stored together.
• The previous Choices type is now labelled Choices (dropdown).

Concatenation groups

• In the collection editor each field can be given a Concatenate group number. Fields sharing a group are shown combined — joined in field order — as one column (table view) or one line (detailed list), e.g. last name + first name, and furigana last + first as a second group. This is independent of the Emphasis (title) setting; combined columns are pulled to the front.

Also included since the last release (0.14.x)

• Emphasis (record name): the list-title marker is now 🏷️ Emphasis (previously “★ Title”), and more than one field can be a key — their values combine in field order to form the record's name (e.g. first + last name), shown in bold, and optionally as one leading column in the table view with a chosen separator.
• New collections open in the table view by default.
• The collection editor is titled Edit collection; its field list auto-scrolls while you drag to reorder.
• Supports Nextcloud 33.
• Fix: reordering fields right after renaming one could prune that field's record data on save.

Emphasis (record name) fields

• The list-title marker was renamed to 🏷️ Emphasis, and a field list can now have more than one. When several fields are emphasized, their values are combined in field order to form the record's name (for example first name + last name), skipping any empty parts. Emphasized values are shown in bold. (The marker was previously “★ Title”.)
• Collection settings can combine the emphasized field(s) into a single leading column in the table view, with a chosen separator — none, a half-width space, a full-width space (offered for CJK languages), or a custom symbol.

Editing

• New collections now open in the table (spreadsheet) view by default.
• The collection editor is titled Edit collection, with a short note on what it changes.
• While reordering fields by drag in the collection editor, the list now auto-scrolls when the pointer nears the top or bottom edge.

Compatibility

• Supports Nextcloud 33.

Fixes

• Reordering fields by drag in the collection editor right after renaming one could, on save, leave a field's data mismatched and prune it. Field keys are now kept pinned to their field regardless of order, and the edited field is committed before a drag begins.

Edit lock (view-only collections)

• A collection's settings now include an Edit lock. While it is on, the collection is view-only: records and fields cannot be added, edited or deleted, and a 🔒 mark is shown next to it in the collection list. It is enforced on the server, not only in the interface.

Field editing

• Changing a field's type or its Secret setting, or removing a field, now migrates the existing record data instead of leaving it inconsistent: values are decrypted when Secret is turned off and encrypted when it is turned on; values that no longer fit the new type are cleared; a Select field keeps existing out-of-range values by adding them to its choices; and data and attachments left by removed fields are cleaned up.
• The effects are listed in a single confirmation first. Any change that deletes data now needs a checkbox confirmation rather than a single click.

Encryption

• Settings has a Re-encrypt secret fields action for secret values still stored as plain text (for example when encryption was enabled later). Turning a field into a secret field also offers to encrypt its existing values.
• The encryption section of Settings was rearranged so each action has a short description.

Fixes

• Sorting a field of dotted values such as IP addresses treated them all as the same number and left them unsorted; they now sort in natural order.

Address field type

• The map link is now a dedicated Address field type instead of a per-field checkbox. Pick the Address type and its value gets a 🌐 button that opens it in your chosen map service (Google Maps / OpenStreetMap / Apple Maps). The built-in templates and the Contacts import now use this type for address fields.
• The map button uses a clearer 🌐 (globe) icon and sits before the copy button.

Reminders in your Calendar, and map links for addresses

• Add a reminder from a date. Date and year/month fields now show a 📅 button in the record detail. It opens Nextcloud Calendar's own new-event editor (in a popup) prefilled with that date as an all-day event, where you set the title, reminders and repeat and save. The button is shown but disabled when the Calendar app is not enabled.
• Map links for addresses. A new per-field option, 🗺 Map link, can be turned on for text fields (for example an address). Such fields show a 🗺 button in the record detail that opens the value in a map. Choose the map service — Google Maps, OpenStreetMap or Apple Maps — in Settings.

Fix: fields could share one value

Adding several fields at once — most often when their labels were non-Latin (Japanese, Chinese, and so on) — could give them the same internal key. Fields that share a key also share a single value, so editing one (for example a date) filled the others with the same entry. Field keys are now guaranteed unique at three levels: the client's key generator no longer collides within a single pass, the schema editor de-duplicates keys on save, and — the decisive guard — the server enforces uniqueness at the one place every field is written, so no import, restore, or future client regression can reintroduce a collision. Existing collections already affected are repaired by giving their duplicated fields distinct keys.

Password generator: choose the symbols and set per-class min/max

The generator now gives the same fine control KeePass does, with the constraints kept mutually consistent so you can never configure a request it cannot fulfil.

• Choose which symbols are allowed. The full symbol palette is shown as a grid; tap to include or exclude each one, with All / None shortcuts. Only the symbols you keep can appear. (A symbol that is also a look-alike, such as |, is struck through while "exclude look-alike characters" is on.)
• Minimum and maximum occurrences per character type. Each of uppercase, lowercase, digits and symbols has its own min and max. "min 2 / max 4 digits", "at least one symbol", "no more than one uppercase" — all expressible. A blank max means no limit.
• Exclusive (mutually-consistent) handling. Every change is reconciled so the request stays generatable: a max is never below its own min, the total of the minimums never exceeds the field's ceiling, and the length is clamped into the window the minimums and maximums allow. The length slider's own floor and ceiling move with the constraints, so an impossible combination simply cannot be entered.
• Guarantees hold exactly: with 5000 sample draws, every minimum is always met, no maximum is ever exceeded, and min == max produces exactly that count.
• Your choices (symbol set, per-class min/max, length) are remembered between uses, and a field's own input rule still wins — a digits-only or hexadecimal field ignores the controls that do not apply to it.

Emoji are drawn by the app, not by the viewer's device

0.12.11 bundled the full emoji set but kept it as a fallback behind the device's own font. That does not fix flags, and the reason is worth writing down: Segoe UI Emoji has glyphs for the regional indicator letters. It reports 🇯 and 🇵 as covered and simply draws them as two boxed letters instead of forming 🇯🇵 — so nothing is "missing", the browser never falls through, and the bundled font was never even downloaded. Taking only the flag code points away from the device font does not work either: U+200D has to travel with them or 🏳️‍🌈 🏳️‍⚧️ 🏴‍☠️ split into a bare flag, and once U+200D belongs to a different font than the base character, every ZWJ emoji comes apart — families, couples, professions, hair colours.

• All 1,849 emoji are now rendered from the bundled Noto Color Emoji subset (SIL OFL 1.1), on every platform. A device's own emoji font is kept behind it only as a safety net for a failed download.
• Verified on three simulated devices — a complete emoji font, a Windows-like one (has the regional indicator glyphs but cannot form flags), and none at all: all 1,849 render identically in each, flags and ZWJ sequences included.
• The font applies only to the elements that display an icon, so the app's own UI keeps the platform look and body text is untouched — characters such as © ® ™ ↔ stay plain text.
• Cost: one cached 1.7 MB download. Collections are shared, so consistent rendering is the point — everyone now sees the icon the person who picked it saw.

Emoji no longer depend on the viewer's device

0.12.10 shipped a flag-only font, which treated the symptom. The cause is that the app was letting whatever emoji font a device happens to ship decide whether an icon is readable — and flags are simply where that shows up first, because Windows has no flag glyphs on any version (Segoe UI Emoji draws 🇯🇵 as a boxed "JP" and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, a deliberate omission that updates will not fix). The same gap hits anything newer than the device's font: Segoe UI Emoji only gained the Unicode 13/14 additions (🫠 🫰 🫡 …) in Windows 11 22H2. Collections get shared, so an icon has to survive being viewed on someone else's screen.

• RegiBase now carries all 1,849 emoji it offers, as a subset of Noto Color Emoji (SIL OFL 1.1) — the vector COLRv1 build, 1.7 MB where the bitmap build of the same coverage would be 4.4 MB.
• It is a fallback, not a replacement: the first @font-face is local() only and names the platform emoji fonts, so a device with a complete font uses its own and downloads nothing. Font fallback reaches the bundled file only for the glyphs the platform font turned out to be missing, and the browser caches it from then on.
• Measured on three simulated devices — complete emoji font: never fetched; Windows-like (emoji font present, no flags): fetched the first time a flag is drawn, not on app start; no emoji font at all: fetched on load, and every one of the 1,849 renders.
• The font pair applies only to the elements that display an icon, never to body text, so characters such as © ® ™ ↔ stay plain text everywhere else.

Flags now render on Windows

• Windows ships no flag glyphs: Segoe UI Emoji draws 🇯🇵 as a boxed "JP" letter pair and 🏴󠁧󠁢󠁷󠁬󠁳󠁿 as an empty box, so the 269 flags in the icon picker were unusable there. RegiBase now carries a flag-only subset of Noto Color Emoji (SIL OFL 1.1) and declares it with a unicode-range limited to the flag code points: the browser fetches the file the first time a flag is actually drawn — not on app start — and then caches it. Every other emoji still comes from the system font, so nothing else changes.

The icon picker now holds every Unicode emoji

• The collection icon picker used to offer a hand-picked 425 emoji. It now contains the complete Unicode 14.0 set — 1,849 emoji, in the nine official Unicode groups (Smileys & Emotion, People & Body, Animals & Nature, Food & Drink, Travel & Places, Activities, Objects, Symbols, Flags), in the official emoji-ordering sequence. Flags, arrows, numbers, professions, hair variants, family and couple sequences — all of them are now selectable. (Skin-tone variants are not listed separately, matching the Unicode emoji-ordering chart itself.) The curated Recommended set stays as the first tab.
• Search box: type to filter across all 1,849 by name or keyword, in your own language (CLDR names for all 12 UI languages). Japanese search is kana-insensitive, so "ねこ" finds ネコの顔.
• Group tabs replace one long scroll, and hovering an emoji shows its name.
• The emoji set is fetched only when the picker is first opened, so the app starts just as fast as before.
• The icon input accepts longer sequences (16 units instead of 8, and 16 instead of 4 in the CSV/JSON import step), so multi-codepoint emoji such as 🏴󠁧󠁢󠁷󠁬󠁳󠁿 or 👩‍❤️‍💋‍👩 can be typed or pasted without being cut off.

Translations

• The emoji category names and the picker tooltip were only translated into Japanese and English; they are now translated into all 12 languages.
• Fixed: Click to choose an icon was stored outside the translations block of l10n/ja.json and l10n/en.json, so it stayed English whenever the in-app language selector was used.

The picker is now available everywhere an icon is set

• The icon picker used to exist only in collection settings. It is now offered in the CSV / JSON import, the Contacts import, the Tables import and the template editor as well — the same picker, shared, so it always shows the same 1,849 emoji. Contacts and Tables imports previously had no icon field at all and always produced 👤 / the table's own emoji; you can now choose one up front.

Fixed: the Nextcloud user-status menu was broken on RegiBase pages

• RegiBase loads the "global" build of the Vue 3 runtime, which publishes window.Vue. A third-party library bundled into Nextcloud core (vue-resize) auto-installs into that global with the Vue 2 API — window.Vue.use(...) — which throws on a Vue 3 namespace and aborted the script that renders the user-status menu. RegiBase now keeps its Vue copy private and leaves window.Vue untouched.

• The collection list in the left sidebar can now be reordered by drag & drop. Drop targets are highlighted while dragging, and the new order is saved immediately (no save button). Collections shared with you by other users are not draggable.