Linus Rath 1cf9944b53 fix: keep the date of edited documents and open them in shared drives ...

Stalwart 1.0 treats a FileNode's `modified` as the client's: a content
update leaves it alone unless the patch asks for it. Saves from the
document editor therefore kept the old date in the file list, and the
editor's conflict check (409 with COOLStatusCode 1010) never noticed a
change made by another JMAP client. PutFile now sends `modified: null`,
which has the server stamp the save. 1.0 echoes the new time in
`updated`; 0.16.6+ answer `null` as before and the batched FileNode/get
reads it.

The editor also could not open a file in someone else's shared drive,
on any version: the Files app sent the listing's "<owner>:<id>" id for
the user's own account, and the launch failed with a 404. It now names
the owner's account and the node's own id, so owner and sharee join
the same editor session. A save uploads into the user's own account
and then points the owner's node at that blob, because Stalwart only
lets members of an account use a blob uploaded into it. The access
token carries that upload account; tokens minted before it upload into
the document's account as before.

The editor now also uses the cookie slot of the login the Pro shell is
browsing, not always the active one.

2026-09-25 18:30:08 +02:00

..

files/[fileId]

fix: keep the date of edited documents and open them in shared drives

2026-09-25 18:30:08 +02:00

launch

fix: keep the date of edited documents and open them in shared drives

2026-09-25 18:30:08 +02:00

status

feat: WOPI office document editing in Files (Collabora/OnlyOffice/EuroOffice) #425

2026-08-31 23:16:19 +02:00