-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Nextcloud sync: Very easy to cause data corruption with Nextcloud's rich text editor #9887
Comments
I feel this bug should also be reported to Nextcloud - this is quite bad that they save a file that hasn't been changed, even worse that they actually auto-change it when saving. |
Ideally we won't do this because we shouldn't have to because that's a lot of complexity to go around someone else's bug.
Actually this is too big a change probably, so let's not look into this for now. I feel it's a shame that Nextcloud is so popular and at the same time they do stuff like automatically breaking user's files. We shouldn't have to work to fix up their mistakes. |
Maybe something to investigate: Can we set a flag on WebDAV to make all these files hidden by default? Maybe we only leave a README.md in there that says "don't change any of these files - it will result in corruption". Or maybe we add such file anyway named "_IMPORTANT_READ_FIRST!!.md" so that it shows up at the top of the list |
I'm also experiencing this issue. Nearly every note is suffering from this |
I don't think so — it could make sense to report the issue either in their Related upstream issues: |
My nextcloud usecase is pretty limited to just Joplin at the moment, and I have no intention of editing files in the web console, so I am testing out this particular feature in case something is being weird with the rich text editor. I executed the two occ commands to disable rich workspaces and rich text editing to see if it would fix things. It definitely makes it easier to fix the files after they have been formatted with https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/text_configuration.html |
Adding to my comment above, I haven't had any corruption issues since making the two changes to the config, and I am syncing across 3 different devices without issue. |
Related: #9997 |
Operating system
Linux
Joplin version
2.14.12
Desktop version info
No response
Current behaviour
Currently,
becomes
Sync with Joplin then fails (key
type_
not found).Expected behaviour
Either
type_
->type\_
(comparebody_diff
andtitle_diff
above)..yaml
extension)Logs
No response
The text was updated successfully, but these errors were encountered: