But still, I think renaming a local file should be avoided. Storage backend (external storage): Client configurationĭe Qt version used by client package (Linux only, see also Settings dialog): Client package (From ownCloud or distro) (Linux only):ĭefault: /Applications/nextcloud.app LogsĪh, I see: " The client resolves this conflict by creating a conflict file of the older of the two files and saving the newer file under the original file name." So not always the local file is renamed, but it is always the OLDER file that is renamed. Then you get a feeling how frustrated I was when I finally realized that no data was saved! -) Server configuration (*): Please do, like I did, a LOT of very important changes, about 2 hours of work.
#Notecasepro comparison pro
See, that in NoteCase Pro the changes are not persistent (selecting another note and then the modified note again -> changes are gone!).In NoteCase Pro, file still open, make changes to the file and save (*).Start the owncloud client and let it sync the file, renaming the local version.Make changes to the local version of the file, to also trigger a sync.I have not modified the file on the server or any other client - a server bug? But not relevant here.)
Trigger, that owncloud/nextcloud wants to sync the file in both directions (in my case, the reason was, that I moved the entire data repository to a new directory and updated the server for some reason, occ wanted to sync "down" the server version of the file then.a file created with NoteCase Pro ( using the ncdb file format (not the other formats, as they are not SQLite-based!) into an owncloud-synced directory. Instead, my suggestion would be that the server version of the file, that's downloaded, is saved under the local name ".conflict." instead. The client should not rename local files (because they could be in use). If an SQLite file, that's currently open in its application, is synced and the client resolves a conflict by downloading the server version of the file, saving it under the original file name in the local folder and renames the local file to ".conflict.", the application that uses the file has troubles accessing the file and data is lost.
Closed there, because it's a client issue and those should be tracked here, I was told.
0 kommentar(er)
