There's a lot to comment on in this thread, and I hope to when I have a gap, but wanted to hit some high points in here. See within:
On Jan 21, 2:02 am, ccahua <[email protected]> wrote: > I copied the TiddlyWebConfig from the system bag into 2 test bags: foo > and bar > > Then I changed config.defaultCustomField, "server.workspace": "bags/ > common" to "bags/foo" and "bags/bar" respectively. Yes. That's pretty much the way to do it. Anytime you create a wiki from a recipe the TiddlyWebConfig that comes from the last bag listed in the recipe is the one that will end up being in the TiddlyWiki and being active. This gets at a bit of the point of having recipes: you can keep some common content in one bag, use that bag in multiple recipes, and then use other bags to customize the TiddlyWiki that is generated. > I made the usual recipe of foo recipe = system + foo bag with imported > empty.html and bar recipe = system + bar bag with imwiki empty.html There's no need to imwiki empty.html. empty.html is included in TiddlyWeb. The only reason to import a wiki with imwiki is if the wiki you are importing has content that you needed to get into a bag quickly. For example yesterday I imported the basic teamtasks wiki into a bag in TiddlyWeb to see if teamtasks works in TiddlyWeb (and it does, I'll be making an announcement about it soon). > I then started the server and created a foo tiddler from the foo > recipe and saved > > Unfortunately when I checked the foo bag (not foo recipe) I didn't see > my foo tiddler. It got saved to the common bag even though I went on > the command line and edited it to bag/foo: It is highly likely that you are encountering some caching problems. TiddlyWeb, since it is trying very hard to be a good team player on the web, is very strict about caching. So a few things to think about: * After you change a configuration tiddler you most likely need to make sure you reload the wiki from the server. * It looks like you may sometimes be editing Tiddlers in place from the command line, directly on the filesystem. If this is the case, you need to make sure that you save a new revision of the file and increment the modified field on the tiddler, otherwise headers used for managing the browser cache when producing output will not be updated, and your browser will not get new content. The other option is to make your browser do a forced reload and/or flush the browser cache. Since it seems like editing tiddlers from the command line is becoming quite popular, a twanager plugin that does it would be handy. If someone wants to write this I can give some guidance, or will do it myself eventually. * You've mentioned needing to restart the server after editing a config tiddler. This is a red herring: the server will send whatever data it is asked for and doesn't use the config tiddlers for itself. Restarting is probably just getting you around some caching issues. > So it works but is a bit of a kludge as the user has to go on the > command line and edit the TiddlyWebConfig manually ie save was set to > common bag. One thing to keep in mind is that TiddlyWebConfig is only used for newly created tiddlers that have been created by the new tiddler or new journal button. If you edit an existing tiddler or create a new tiddler by following a link from an existing tiddler those tiddlers will use the fields of the existing tiddler and save according to the rules in there. This means that if you have an existing TiddlyWebConfig already in bag common, when you edit it, by default it will be written back to bag common. To get it to go somewhere else its server.workspace needs to changed to something else. I think FND has a plugin that can do this. > Sorry for all the long posts, but it helps to refer back when i need > to test again on the next iteration, hopefully beta! > I would have thrown these notes to the wiki, but i don't think it is > useful astiddlywebis still evolving. Putting stuff on the wiki is great if you feel like doing that: It can evolve too. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
