Hi Willy, To answer your question, the android client does sync back cached (downloaded) files that are modified on the phone. In particular, the tiddlywiki file modified on the phone will be uploaded to the server and become available on other devices. Now, I have been using this feature to go back and forth between TW on my desktop and phone for the last two years, so the feature has been there for a while. I also just confirmed this by a fresh empty.html from tiddlywiki.com and it works. I have the impression that the iphone client somehow doesn't do this file-watching and automatic upload and the difference between the mobile clients is indeed quite intriguing.
Nevertheless I guess with webdav working well, having that feature on your iphone is not that critical for you. I know the thread is mainly for discussion of the Seafile's webdav feature and I don't want to go too much off topic here but for the sake of completeness, here are the steps of the workflow to achieve what I described above. Works on Android with a Seafile server without webdav enabled. 1. Download the TW file to the phone using the Seafile app. The downloaded file will have a orange checkmark at the corner when viewed in the Seafile app and will be located in `Seafile\<your account name>\path\to\file` under device storage partition. 2. Modify the file: Option 1 (recommened): Open with AndTidWiki. Upon editing, auto-saves in place and directly modifies the file. Option 2: Open with your favorite browser, make edits and click `save` in TW. A new file will be downloaded. Copy and replace the original file with the downloaded file using your device file explorer (this option is not fun to do and not very useful in practice). 3. Go back and check the status of the file in Seafile app. The last modified timestamp will change indicating that Seafile app recognizes the local modification of the file and it will silently upload the file back to server. 4. Allow ~1 min for changes to propagate. Access the file on another device. You will see the updated file with the recent changes made on the phone. What this doesn't do: automatically download the files to the phone that were changed elsewhere. you need to download again to get the up-to-date version. Luckily Seafile app keeps track of that and if you try to open the file in the app, it will download the file only if the file on the server is different than the local copy. As I said, when webdav server in Seafile works properly as you described, it pretty much eradicates the need for the file sync mechanism that the mobile client provides. I fixed the save issues on my webdav setup thanks to PMario's comment below and will probably use it almost exclusively for TW sync from now on. Best wishes, Altug On Wednesday, August 29, 2018 at 2:05:55 AM UTC-4, Willy Tanner wrote: > > Hi Altug > > ah, I see, we got our wires crossed here. As I mentioned in my first post, > Seafile is many things in one, first and foremost it is a file > synchronisation tool, which can be used to keep files and folders in sync, > with version history, optional web interface, sharing links etc etc. The > behaviour you describe is normal for the Seafile companion app (except a > little detail about which later), the file is downloaded to your phone and > once saved also synced back to the server and any other machines that are > connected to that repository. > > The point of this thread, however, is that Seafile can if you so wish be > configured as a Webdav server. In the process you designate a folder on the > server which then can be accessed from the outside (via your phone or > another computer) without the need to download the file first. This > obviously only works when online but if so, one can edit the file and the > save is done directly on the server. Importantly, the file will be accessed > via a special URL directly in the browser, not through the Seafile app on > the phone. > Note that the Seafile server is by default off but once on, the edits on > the phone or some other computer are autosaved back and instantly available > anywhere. > > > Question to you, Altug, you were reporting the behaviour of a Tiddlywiki > file after calling that file from the Seafile app on your phone, correct? > Can you please check if any saves on your phone were indeed saved back to > the server by accessing that file from a different computer (not your > phone, in case the edited file still sits in the cache)? On the iPhone at > first glance it looks like saving an edit on a local file via the Seafile > app back to the Seafile repo on the server works but it is purely in the > phone's cache. No other computer sees that edit nor the phone once you > force it to reload the content from the server. > If this were different indeed on Android I'd be surprised. > > Cheers > Willy > > >>>>> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ea20defa-3417-4578-a593-85f6dcdbb64f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
