Another option might be tweak the syncFilter in $:/config/SyncFilter to not sync $:/StoryList
The publishFilter may only apply to the single file version and not on node. On Thursday, April 16, 2020 at 6:38:18 PM UTC+2, Saq Imtiaz wrote: > > This is a consequences of a change in behaviour in syncing of system > tiddlers. > > A workaround is to use the publishFilter to exclude the storyList from > being saved. > > Eric provides instructions here: > > https://groups.google.com/forum/#!searchin/tiddlywiki/publishfilter%7Csort:date/tiddlywiki/4Q21AiOrDmg/ilgUkcP-AwAJ > > On Thursday, April 16, 2020 at 5:26:27 PM UTC+2, HokieGeek wrote: >> >> Sorry if I missed this being brought up, but I am running TW 5.1.22 on >> node.js and a change to the StoryList has caused what I think is an >> unintended consequence. Or perhaps there is a setting that I need to change. >> >> In the past, whenever I pointed a browser instance to my TW instance, it >> would create a new StoryList. >> The effect was that I could be browsing the wiki with one set of tiddlers >> open, and on a separate browser instance (mine or another user's) could >> have a different set of tiddlers open. >> When I updated to 5.1.22, the behavior I see now is that the StoryList >> gets updated from the server to all client copies so that all instances >> will have the same tiddlers open. >> >> Has anybody experienced this? >> >> >> -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1920c902-b573-43d7-adb7-57171e0a881f%40googlegroups.com.
