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.
Thanks for the report, Mark.
I’d be interested to know how you use your phone for TiddlyWikiing.
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.
@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
Will this be a solution that bypasses a need to have an extension (like Timimi) for local saves using a browser as editor?
IF so, will further progress be added to this thread? And if not, how can I receive a notification for this?
The OP uses the default browser save mechanism, which is activated by the green [Download] button at GettingStarted.
TiddlyWiki uses browser extensions like TiddlyFox (now obsolete) and Timimi since a very long time already, so we (the TW users) are used to use “single click” save options. We are not used to use the browser default saver, which needs several clicks instead of one.
I am trying to get this workingm and it will not work for me. Every time it saves, it uses the old filename and append a (1) to the end of it. The minutes never seem to update, even when I use @Mohammad solutrion
Yes. I don’t see how @Mohammad 's solution could work. The default download behaviour is to append (#) to each download filename that matches an existing filename. So unless there’s a setting to override this behaviour, or unless you bring up the save dialog every time, you’re going to get the (#) numbered files.
If you use @mwiktowy 's solution above, and don’t save more often than once a minute, then you can avoid the (#) numbering. But this whole solution will fill your download directory with files that have to be cleaned out.
I was using the Native Saver plugin, but 2 days ago it threw an error and told me it could not save the file and I ended up with a file that was 0 KB in size. Lost everything. But I was still in “experiment” mode, so I think I only lost one note.
I was trying to find a way to save, and have it create a backup before it saves to prevent this from happening again. This looked like a possible solution.
Well, the minutes updated, but you may have to use save as, once your browser detect a duplicate.
I’ve been using the Native Saver plugin for Timimi notes. So that is worrisome.
Remember if the saver doesn’t work, you can go the advanced search and select the “Tiddlers modified since last reload” and then save your recent work as a JSON file. Of course this assumes you have a backup before the last reload. You could probably just download all your tiddlers separately and load them into an empty TW file later.
So apparently people in firefox can turn off auto-numbering ( file (1).txt, file (2).txt) but people in Chrome can’t.
I forgot that there are extensions that can fix that. Here’s one that seems to be getting good reviews (from a tiny fan base):
You can not deactivate auto-numbering in FireFox. You have to use the native Save As dialogue, that lets you overwrite existing names.
If you keep your wiki files in the download directory or any download/subdirectories you can use my file-backups add-on for FireFox only
I personally use the F: drive as my browser default downloads drive. So I can save my wikis in any directory on drive F.
Sadly, I can’t install Chrome plugins on my work computer. Locked down environment.