On Tuesday, December 29, 2015 at 1:17:25 PM UTC-8, Lynn C. Chiu wrote:
Today, instead of saving my TiddlyWiki5 with the "save" button from my Chrome browser, I went ctrl-S to overwrite the .html local file. This broke my wiki. When I opened it up again, the sidebar functions are clickable but not functionable. There seems to be an overlay of two wikis: my home view (with the default tiddlers) and those that were open when the file was last saved. I can close and edit the former but not the latter. I have attached a picture that shows the "overlay" on the upper right.
(1) Is using the "save" or "download" button the best ways to save the wiki?
As you've learned, you must not use the browser's 'save' command, as it does doesn't save the right stuff. Because the TW page display is dynamically generated, the browser's "page" includes both the TWCore and tiddler data that was loaded from the original file... PLUS the rendered output from processing that data. When you save the file with the browser's command, it saves the whole thing...TWCore runtime, tiddler data, and rendered output. When you then reload the file, it still runs the TWCore to render the tiddler data... but it also has a static 'snapshot' of the HTML that had been displayed when you saved the file. The results is, as you've noted, is that the document seems to render twice, with one rendering being interactive, the other static (and rendered on top of each other, due to application of CSS rules).
(2) Is it possible to easily retrieve imported notes from, say, the source code, of my wiki?
NO WORRIES! Your data should still be intact within the damaged TW5 file. To confirm this, I used ctrl-S (browser save) with one of my own TW5 files to reproduce the problem. Then I dragged that 'broken' TW5 file onto an empty TW5.... and it can still find and IMPORT all the tiddlers from that file into a fresh, unmangled TW5. You can then save that file locally.
Note: one possible area I was not able to confirm: do international (multi-byte) characters survive this recovery process intact? You should try using some multi-byte characters in your content and see if the browser's save stored them correctly.
enjoy,
-e
Eric Shulman
TiddlyTools / ELS Design Studios
Inside TiddlyWiki: The Missing Manuals