Save Your TiddlyWikis Without A Saver Or Plugin

Hello Everyone.
You can have that dream TiddlyWiki in THREE SIMPLE steps:

  1. Create a tiddler named: $:/config/SaveWikiButton/Filename
  2. For the text in that tiddler write *some variation of: <<now "YYYY0MM0DD-0hh0mm">> My TiddyWiki
    *Adjust to suit your needs.
  3. Save Your TiddlyWikis And Reopen The New Ones
    [CTRL+S] To Save
    [CTRL+J] To Open The Recently Downloaded List
    Enjoy!
11 Likes

Apologies…
The snippet didn’t seem to appear between the <>.

<<now YYYY0MM-0DD0hh0mm>> My TiddlyWiki 

Hope that helps you!

1 Like

Very nice. I didn’t realize that you could do this. (Although I should have!)

And something else new to me. Very useful.

Thank you for sharing, and welcome to the talk.tiddlywiki.org community!

I suppose this implies a web browser and a desktop rather than a mobile context?

Great post, @AlfieA.

Just for fun, I asked ChatGPT what it thought of your method: https://chatgpt.com/share/6745e4e2-4748-8001-9d24-102b15c460ad

1 Like

Are you heading over to the dark side?

:rofl:

What do you mean, heading? I never left :wink:

1 Like

@EricShulman has recently shared a solution to have a custom save button. It can be used with your solution and create a magic save button.

If you use $:/config/SaveWikiButton/Filename with below content in the text, then you can only create maximum six backups, this will work similar to Timimi which reuses the first backup file when you created the maximum number of backups. Your folder will not be populated with many .html files.

{{$:/SiteTitle}}-backup{{{[<now mm>divide[10]floor[]]}}}

The minimum interval between two saves is 10 minutes (change it if you like), that means if you press save button in less than 10 minutes the file will be overwritten.

5 Likes

On Android, appears to work with Chrome and Kiwi browsers, at least if you are sending to the download directory. Works once with Firefox, but somewhat irrelevant since you can’t load a file back into Firefox.

Using the name “SaveNew.html” as the file name, I saved TiddlyWiki .com to a folder on my HD (my Firefox is set to “ask” where to save). Then I double clicked SaveNew.html and it opened fine in Firefox.

What was your method?

EDIT: Oh. Android. Nevermind.

Very kind of you, Scott. This is a great community.

It was fun reading you ChatGTP post, Coda. Thank you for doing that. Was very humbled.

1 Like

Thanks for the report, Mark.
I’d be interested to know how you use your phone for TiddlyWikiing.

1 Like

So, there’s a little problem with this approach.

On my test on two different chromium-based browsers, the minute part did not update. It appears to only update when the file is reloaded.

Does anyone know if there is a trick to force the $:/config/SaveWikiButton/Filename tiddler to update it’s internal value?

There are so many hassles on the phone, that I almost never use TW for note-taking there. I do use it for note-reading (like literature), and for checklist apps (travel lists). But use something else if I want to write a note, since browsers on phones/tablets will use any excuse to reload or clear your page, which leads to work loss. You can use it for notes, but you need to be hyper-vigilant about saving before leaving the page.

Mark, I have the same reloading issues with phones. At first I thought it may have been an old, cheap Android thing. But still happens with my new high-spec Android.
So… like you, I use the phone TiddlyWiki to take notes, but not to manage the TW. I export as .TID files immediately after drawing them up.

2 posts were split to a new topic: Idea - Using Time Based One Time Passwords (TOTP) on the Browser

@Mark_S : I ran into the same issue with the <<now>> macro not updating very regularly … however trying @Mohammad 's syntax up a few posts, {{{[<now ...>]}}} , seems to work better. I think the filtered transclusion forces a refresh when anything has changed but just a plain macro does not.

{{$:/SiteTitle}} - {{{[<now "YYYY-0MM-0DD-0hh0mm">]}}}

Works well for me.

/Mike

This is a problem with the core TW save-button. The action widget is evaluated inside the button-widget body. To solve that problem we will need to use <$button actions= parameter instead.

I’ll have a closer look at the code and will create a PR when I do have time.


Edit: I did create a PR at GitHub. Once that’s merged, it should be fixed in the next version