-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rich Text Editor: Reproducible "The document has been changed outside of the editor. The changes cannot be applied." #1083
Comments
I use the android app to edit my notes and this happens every time I make a change to a note in the app and then open up the same note in the web UI. I would appreciate it if this could be fixed. |
Same thing here. No need to say that this kills collaboration, since it also happens when one user edits a shared note and another then also. |
@juliushaertl Issue is tagged with |
Any updates on this? |
same issue here. Additionally I have to choose between "Use current version" and "Use the saved version". |
Same issue here. Can I do anything which would help to solve this issue? For me it happens in Rich Text Mode even if I do not actively use the Android Notes app. |
Same here. |
Same issue here. I can reproduce it consistently by editing my root-directory A big help, though short of a fix, would be to improve the wording of |
29.0.3 without any office suite. When I create .txt file on synced dir, put Also, Is I reopen locally file with |
The Rich Text Editor continues to get in my way and provoking data loss due to lost changes. The main reason is that the editor shows the
The document has been changed outside of the editor. The changes cannot be applied.
-dialogue and leaves the user to picked the right button.There are several constellations this error occurs consistently in any of the following cases:
Steps to reproduce
Display mode
toOpen in edit mode
Display mode
back toOpen in rich text mode
On similar lines one can provoke/reproduce the same error for any of the other use-cases.
Expected behaviour
The rich-text editor should not keep any (outdated) cached version directly after save and claim potential data-loss or differences to the stored version.
Instead it should start fresh from the saved version in any case you left it saved.
Actual behaviour
Honestly: I don't understand the whole need for background caching across editor sessions.
Server
Please complete the following information.
Nextcloud configuration:
Client
Please complete the following information.
The text was updated successfully, but these errors were encountered: