![]() I have not found any other solution than this… The only workaround I found is to tell all users to periodically “resync” ALL libraries in order to be shure that they have all files and no conflicts. I can not believe that all your customers are happy how you handle “read-only” which in fact is not (at least not for the sync client) It would have been nice to know a year ago that you will not change itĪnyway: you’re pushing customers away to go for other solutions that handle this properly I am still available to help you guys from a user perspective and I hold my credit card ready to upgrade our pro version to 20 users - but I must be sure this (imho) basic feature works You just have to find the time to see how the guys from Nextcloud did it, check if you agree and implement it. I think this is something that should be possible to implement.Īnd once again: I have explained in detail how it can work and even pointed you to the Nextcloud implementation and suggested to do it the same way… It’s actually very simple what the seafile client must do in a read only folder.ġ.) if a user deletes a file, it is synced backĢ.) if a user modifies a file, the original is also synced back and the modified must be renamed (conflict) - same as you have to do for other conflicts as wellģ.) if a user places a new file (or creates a conflict file) in a read only folder, the error message must be 100% clear and only go away once the problem is solved I like seafile - so please tell us that this will be fixed soonĪlso note that: Automatically syncing back the delete file will not recover the changed content, because it’s not uploaded to the server. There is no other feature that I really need compared to the community version - so I start to ask myself what real benefit do I get for the pro edition?Īctually I would like to upgrade to 20 users per year, but only if we have a proper read only handing… My subscription for the professional version must be renewed in April but I still have zero benefit except file search. (there is now a short time where the user sees a error - but just for the next sync - as soon as there is another sync from the client, the error message goes away and the folder seems to be perfectly in sync) I just tested 7.0.13 and still it is not possible to solve the basic read only functionįiles deleted from a read only folder are not automatically synced backĪdding files in a read only location does not show proper and easy to understand error message Read only function is great but I still do not see a solution - it seems you are busy with maintenance (good) and adding fancy features (debatable)… Hi Jonathan, hi post is dating from April 2019 and I am disappointed
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |