Fixed
- A Norwegian browser or system that reports
noornngets Norwegian instead of English.
Norwegian Bokmål ships asnb, but many browsers and systems announce the general codeno
(no-NO,LANG=no_NO.UTF-8), and that fell through to English. The same went for Nynorsk
(nn), which has no translation of its own: it now gets Bokmål, the closer language, rather
than English. This holds for the app, the web installer, the command-line installer and the
langparameter of the API. An explicit language choice in the settings is not affected. - A loan created from "New entry" in the budget overview can say how many installments are
already paid (#1648, reported by @ramonbresco). The field existed only in the "New loan" dialog
of the Loans tab; choosing the type "Loan" in the overview's dialog left it out, so a running loan
entered there started at zero. Both dialogs now build their loan fields from one list, so a field
can no longer land in one and miss the other. The same repair makes the suggestion work that
2.29.0 announced and never delivered: moving the first due month into the past fills in the number
of months since then, never more than the loan has installments, and stops as soon as you set the
field yourself. For a loan with interest that limit is the term shown in the preview; until the
preview has one, the field stays at 0. It was wired to the dialog that did not have the field. - Housekeeping: "today" and "last visit" read a visit's check-in as a point in time. Only
visits the app did not write itself are affected: rows imported by hand with a time that has
no zone, and the demo data. They were compared and sorted as text, so such a visit could be
missing from the helper's "today" or counted on the neighbouring day, and the earlier of two
visits could be shown as the latest - in the module, its visit lists and the overview tile.
All of them now compare the time on the household's clock. Stored values are not changed. - Editing a shared expense shows the amount in your household's number format. The amount
field came pre-filled the way the server stores it, with a point:12.50in a field whose
placeholder says0,00, and12.5when the expense was handed over from a budget entry.
The same held for the exact shares and percentages of an existing split and for the open
debt in "Register payment". They now use the decimal separator and digits of the household
region, like the placeholder next to them, and are read back unchanged when you save. - A wrong address below the pairing or invitation page no longer ends on the sign-in page
(#1640). Opening something like/pair/extraor/join/extrawithout being signed in led to
the sign-in page, because the app fell back to the overview, which needs a session. It now
goes to the page above it,/pairor/join, as it already did for someone who is signed in.
A wrong address below a page that needs a session still leads to the sign-in page first. - Guests of a shared-expense group are no longer stuck behind the back button (#1640). A
guest only sees the budget, so every other address sends them there. That hand-over kept the
address they came from in the history and put the budget on top of it, so the back button led
straight into the same hand-over again. The address is now replaced. While the budget was still
loading, a second tap could also start a second page change next to the first; it now waits.
And when a guest opened an address that does not exist, the short message about it was lost on
a fresh start, because it came before the page that shows it; it now appears. In a household
that has switched the budget module off, a guest is no longer sent to it: until now the app
kept sending them back and forth between the budget and the overview until the page gave up. - "Access denied. Please sign in again." is gone (#1640). An error screen or message for a
refused request used this second sentence, which advised signing in again although the session
was fine. It now says "You do not have permission to do that", the same sentence as everywhere
else, in all 26 languages. - Closing an event dialog on a wide screen no longer moves the address to the page you came
from. In the day, week and month views an event opens in a small card. Choosing "Edit" or
"Delete" there closes the card and opens the next dialog a moment later - the form, or the
question whether a change applies to this event, this and following ones, or the whole
series. The app gives back its "Back closes this dialog" history entry when the card closes
and takes a new one for the dialog, and it took the new one before the browser had finished
giving back the old. The browser then stood one entry lower than the app believed, so
closing the dialog - "Only this event", Cancel, Escape, any way out - stepped back once too
often: the calendar stayed on screen while the address bar already showed the previous page,
a reload opened that page, and the next Back skipped one. Deleting a recurring event from
the card did this every time; editing did it whenever the form opened quickly enough. The
app now waits for the browser to finish before it takes the new entry. - A direct link to a module that is switched off opens the overview, not the module. Opening
the address of a module the household has switched off, from a bookmark or after reloading the
page, still showed that module, complete and usable, although it was gone from the navigation.
Inside the running app the same link already led to the overview. It now does so on a fresh
start as well, for members and for guests of a shared-expense group, and the module's address
is not kept in the history. - A refused request explains itself in your language (#1640). Three refusals still reached
you as the server's English sentence: changing a locked task as someone who is neither its
creator nor an admin, editing or deleting a recipe that is mirrored from Mealie or Tandoor, and
saving from a page that had been open so long that its security token no longer matched. Each
now has its own sentence in all 26 languages; the last one asks you to reload the page, and you
only see it after the app has already fetched a fresh token and tried once more by itself. The
refusal for changing the email addresses of a household member's contact uses the hint the form
already shows. And where the app already knew the more precise reason, for example read-only
access to a module, the error screen no longer replaces it with the general "You do not have
permission to do that".