Sean, The main way at present to handle multiple users is with a Bob server. It checks out tiddlers being edited by different tabs/windows, users and computers on a local area network.
The bobexe is a very east way to install and use bob. I and others are working on single file checkout for serial editors, and you can make use of existing document management systems such as sharepoint to leverage its check out system. Regards Tony On Sunday, 27 September 2020 10:50:24 UTC+10, Sean Hankins wrote: > > Ok, thanks for the tip! It helped but, unfortunately I'm still having > problems. From what I can tell, after making your suggested change, > the $:/StoryList is updated by the editing user only now, which means I > can't edit or browse with this user while someone else is using it and > pulling that list, lest they also receive the editing/browsing responses. > The other half of the problem is that every once in a while, the anonymous > browsing user's client requests this list again, and all open Tiddlys close > themselves and goes back to the last saved list, obviously disrupting the > user experience. > Perhaps there's a way to disable saving to or reading from the > $:/StoryList all together? Or would this even resolve the issue, or make > something else not work? > > On Saturday, September 26, 2020 at 4:31:09 PM UTC-7 Eric Shulman wrote: > >> On Saturday, September 26, 2020 at 4:03:54 PM UTC-7, Sean Hankins wrote: >>> >>> Hi! I'm having an interesting problem with my TW5 installation having to >>> do with the use of multiple anonymous users and a single editing user. >>> Whether logged in or using anonymously, when a user opens a Tiddly on their >>> local web browser, it opens the same one in all other users' instances as >>> well. This also happens when logged in as an editing user and editing; an >>> anonymous user (read-only) will get an editable Tiddly opened in their >>> browser, although any changes aren't saved permanently. >> >> >> Caveat: >> *I don't use the nodeJS server setup, so most of what I say below is just >> a guess...* >> >> Nearly every activity in TiddlyWiki has some effect on one or more >> underlying system tiddlers, used to track the current "state" of the >> interface. For example, whenever you view or edit a tiddler, the "list" >> field in $:/StoryList is updated. >> >> When using nodeJS, all tiddler changes are synced to the corresponding >> .tid files stored on your server. Then, because those .tid files have been >> updated, they are being pushed to any other users that are connected to the >> same nodeJS server. >> >> To work around this, try disabling the default "Autosave" setting to >> prevent your activities from being actively synced to the server. To turn >> off this setting, go to $:/ControlPanel, Saving, General tab and choose "Do >> not save changes automatically". >> >> If this works, then nothing you change in your instance of TiddlyWiki >> will be written to the server until you use the "Save changes" button in >> the Sidebar. >> >> Let me know how it goes... >> >> -e >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/89af503a-bb00-4f65-8c59-483f60b6673do%40googlegroups.com.
