Last time I said 4.0.6 would probably be the last release for a few weeks. That held for twenty-two hours. Two good bug reports arrived with screenshots attached, and it turns out I cannot leave those alone.
Calendar syncs on its own now (#43)
The server side has been finished since the calendar shipped. Nothing ever called it. AppData has been sending a CalendarSync interval this whole time and only the settings screen bothered to read it, so an event added on your CalDAV server stayed invisible until you pressed Sync by hand.
There is now a calendar store shaped like the contacts one, on the same sync_interval setting. It starts ten seconds after the contacts sync and offsets its interval, so a fresh login does not open two DAV conversations at once. A sync that brings something in also redraws an open calendar, rather than leaving the grid showing whatever the database held when you opened it.
Thanks to @m0urs, who read the logs and identified the cause correctly before filing.
Contact form, four faults (#44)
All four from @m0urs, with screenshots.
- The remove button sat on its own line. The input is 400px wide and the row was plain block flow, so there was nothing left for the button to occupy. It is a flex line now.
- The address type box was always empty. It was a select offering home and work, but vCard writes
TYPE=HOMEand can carry several types at once, so the stored value never matched an option. It is a free text box now, with those two as suggestions. An address book that writes something else keeps what it wrote instead of losing it to a fixed list. - Business tab labels started at different places, because Bootstrap right aligns them at a fixed width. Left aligned inside this form only, so the settings and admin forms keep the Bootstrap look.
- A note is prose and had a single line input. It is a textarea.
Nextcloud contact groups (#42), untested
Read this part before you get your hopes up.
Group names only ever came from the local address book. If you keep your contacts in Nextcloud, your groups were invisible to compose autocomplete. You could expand one by typing its exact name, but nothing would ever offer it. Suggestion drivers are now asked for matching category names alongside the local book, and the Nextcloud driver answers with an indexed CATEGORIES search. Expansion had to follow, because a group that is offered and then inserts nothing is worse than one that is never offered at all.
I have not run this against a real Nextcloud. It needs a server with several address books and at least one group, which I cannot reproduce here. The counting logic is tested on its own and the rest is reasoned through, but if you keep your contacts in Nextcloud, treat this as something to try rather than something that works. Reports welcome.
Update the Nextcloud plugin in your installation. It went to 2.39.0, and the version you have will not have any of this.
That plugin's "Ignore system addressbook" setting has a description now. The label reads as though it narrows which contacts get searched. It does not. It only drops the address book Nextcloud generates from your server's user accounts, and your own address books were always searched either way.
Smaller things
- Contact row deletes are a trashcan rather than an X.
- The remove button on a compose recipient chip was a bare
✖sitting in a class that is styled nowhere in the tree, so the system emoji font drew it. It is the same mask icon as everything else now. The X stays, though: dismissing a chip is not deleting anything.
Every fix here except the two Nextcloud pieces applies to SnappyMail as well.