I haven't found much information on the backstage Sync ability.
Yes, it's rather poorly documented I'm afraid.
Contributions welcome:
http://tiddlywiki.org/wiki/Synchronization
How does this sync work? Does the sync work both ways?
That depends on the adaptor (and thus the backend) being used.
The FileAdaptor, which is the default and used to interact with other
TiddlyWiki documents (whether local or on the web) only works one way,
passively consuming content. That's because there are no facilities to
to process data on the receiving end (it's just a static file).
However, the TiddlyWebAdaptor, ccTiddlyAdaptor, MediaWikiAdaptor et al.
allow for two-way communication. That means local changes can be pushed
to the server (the ServerSideSavingPlugin, used by both TiddlyWeb and
ccTiddly, simply uses the sync mechanism).
It's worth noting that there is no conflict resolution (yet?). So if you
import a tiddler, modify it in your local document while it has also
been changed on the server, there is no automated merging.
This issue comes up when users import a plugin, change its tags (which
constitutes a modification of the tiddler) and later want to upgrade to
the latest version.
I've noticed that the sync dialog displays "linked" tiddlers. These
links were made while importing tiddlers from another file. Can I
remove those links? Undo them?
You can disable that link by removing the respective tiddler's extended
fields (in particular "server.host" and "server.type") - e.g. using
Pascal's FieldsEditorPlugin*.
-- F.
* http://visualtw.ouvaton.org/VisualTW.html#FieldsEditorPlugin
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/tiddlywiki?hl=en.
