Testing the Multi Wiki Server Plugin

[well-noted]

I have been noticing something recently that suggests to me I may have a misunderstanding of MWS – discrepancies between the same tiddler when it is represented in different recipes.

For example, my TODO items are in one bag that is shared between two recipes – in one recipe, I tag an item as “Done” and am surprised to find that it is not also tagged as done in the context of the other recipe.

After some investigating, I discover that by changing the tag in one context, it creates a new tiddler in the top bag of the recipe to be used in the place of the same tiddler in the bag of lower items in the recipe.

Is this expected/desired behavior?

It was my sense that modifying a tiddler that is in one bag should preserve its place in that bag if modified, rather than creating a new tiddler in the first bag of the recipe in which it is being viewed

[pmario]

@well-noted

Is this expected/desired behavior?

It was my sense that modifying a tiddler that is in one bag should preserve its place in that bag if modified, rather than creating a new tiddler in the first bag of the recipe in which it is being viewed

That’s desired behaviour.

You may have a closer look at a reply at an other thread, where I do point out some “gotchas” for new users.

Low-cost multi-wiki solution for D&D game?

From my point of view, that multi-wiki-server MWS plugin still is highly experimental. Especially the access handling is still in flux and subject to change in backwards incompatible ways. I think your usecase can be solved with MWS, but you would be an early adopter.Which means there will be breaking changes in the code, which may set you back several steps, or even to “sqare one”. The access control list (ACL) configurations in TW is “role” based. But at the moment this system only knows how…

Cloning content into “higher level” bags has an advantage in the long run. – The main problem at the moment is, that we do not have any visual indication, what’s going on.

If you would have had the possibility to move the “new tiddler” and “overwrite” the “lower level” one in a convenient and visible way, it would have been an obvious feature.

Because we are still in early stages, it is an issue.

[JanJo]

Could this be cured with an overwritten tiddlers table where the overwritten tiddlers are listed per bag perhaps with a sort of automatized temporary renaming mechanism.

(Zut alors ! It sounded easy in the beginning….)

[well-noted]

Interesting. I will need to get my head around this somewhat.

In my case, I would like to have a general TODO list that stores all the TODOs from all my various wikis – it has access to all the bags of TODOs from the relevant recipes, and I had expected that I could interact with the TODO list and have those changes reflected across all the other recipes: instead, checking off a TODO item only generates a clone in the TODO List page template bag, which is not as useful to me, especially in the context of tracking projects.

@pmario

If you would have had the possibility to move the “new tiddler” and “overwrite” the “lower level” one in a convenient and visible way, it would have been an obvious feature.

I would propose going a step further and say allowing users to select from multiple handling depending on filter conditions would be most helpful.

For example, I don’t mind if my TODOs get shuffled into other bags, but ultimately I do want them to all aggregate toward the TODO-items bag.

Likewise, I want all my Index and Idea tiddlers to end up in my KnowledgeBase and my Sources to end up in my References.

@pmario

Cloning content into “higher level” bags has an advantage in the long run

State tiddlers are the only obvious example I can think of, in my case, for this, but perhaps I’ve overlooked something.