nextcloud / nextcloud/richdocuments
Edits to Collabora Online spreadsheets not getting saved; issue may be linked to "The server encountered a nodocloaded error while parsing the setviewreadonly command" error message
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 453
- Forks
- 147
- Avg merge
- 14h 54m
- Merged PRs (30d)
- 83
Description
Hi everyone, I was using the Collabora-based NextCloud Office tool, together with NextCloud AIO v13.2.1, to host some spreadsheets that I update on a regular basis. I found in late June that, after updating a spreadsheet, my changes would sometimes get lost when I next loaded the document. This issue occurred on both the NextCloud Android app and my mobile Android web browser; I don’t think I’ve had it happen on my Linux Mint desktop’s web browser yet.
I’m guessing this issue is linked to the following error message: “The server encountered a nodocloaded error while parsing the setviewreadonly command.”
I’ve been trying to make sure to save the document before exiting out of the spreadsheet viewer, but that doesn’t seem to help.
Any tips for resolving this issue would be greatly appreciated. Thank you!
(I've temporarily switched over to Euro-Office and haven't had any issues just yet with lost edits, but I'd love to get the Collabora-based setup working again, as its mobile spreadsheet editor works better than does Euro-Office's.)
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.
Research direction
Start by reproducing the lost spreadsheet edits with Nextcloud AIO v13.2.1 and the Collabora-based Nextcloud Office tool on the Android app and mobile browser. Check whether the “nodocloaded” error appears while parsing setviewreadonly, and verify that edits remain after saving, closing, and reopening the spreadsheet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100