nextcloud / nextcloud/richdocuments
Send reliable timestamp for when "Document changed in storage" conflicts happen
@elzody is already working on this.
Since Jun 23, 2026.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Describe the bug
It seems - in some cases - users are seeing the "Document changed in storage" conflict dialog even though no one else touched the file. This could be due to how richdocuments produces/compares the timestamp as it seems a cached value is been passed.
LastModifiedTime is already sent but its value - in some cases - is unreliable due to stale cached mtime after putContent. Probably best to ask storage layer again for fresh metadata instead of trusting that cached value. This might not fix the issue but it will fix for that situation and make further chasing easier to do.
Related: https://gerrit.collaboraoffice.com/c/online/+/4918 from @mmeeks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.