![]() ![]() The new created logfile is showing only an issue with a looked file on Dropbox, but nothing related to GD I just renamed the log file and reproduced the issue described above. Updated from an older ownCloud or fresh install: NO OwnCloud version (see ownCloud admin page): 9.1.0 ![]() ![]() If OC finds two or more files with the same name in the same GD folder, no file is shown in the OC web client and local files on the PC are deleted by the OC SyncClient. If this is not possible for whatever resons, I would expect that the old file on GD is deleted before renaming the uploaded temp file.Īfter Changing a file in OC web client or on a Win PC locally, which is connected to OC using the Win OC SyncClient, an additional file with the same file name is created in the GD storage. I would expect, that OC supports the versioning of GD, which would mean OC is just adding an new version to the existing file. When modifying a new uploaded file, the same issue affects this file afterwards Any new created file, which does not exist on GD, is uploaded correctly to GDģ. The issue is 100% reproducible for any file, which already exists on GD and were modified using OCĢ. I checked the local storage as well as Dropbox for the same issue, but there everything works fine.ġ. I'm not 100% sure if I maybe configured the new App connection somehow wrong, as the available tutorials for connection GD are not 100% consistant. The activity log in GD shows, that the modified file was uploaded with a temporarily filename and were renamed after upload was completed. It seems to me that OC breaks the versioning management of GD. Everytime when modifying a file stored at GD using the OC web interface as well as using the OC Windows SyncClient, the file disappears from the OC web client and gets deleted afterwards by the Win client on the local PC drive.Īfter some investigations I found out, that the file still exists on Google drive, but two times with the same file name. I've got an issue using Google Drive (GD) as external storage. ![]()
0 Comments
Leave a Reply. |