I am hoping to release TiddlyWiki v5.3.7 on Monday 7th July 2025. Before that happens we would appreciate as many people as possible helping with testing the new release.
This release is primarily made up of:
Over 20 bug fixes
Tweaks and fixes to the core palettes
Updates for Chinese, French, German and Japanese language plugins
There are several ways you can help with the testing:
Visit the prerelease on the web, explore the release note and try out the new features. Let us know if the release note or documentation is not clear
Use the prerelease upgrader at https://tiddlywiki.com/prerelease/upgrade.html to make a test upgrade of your own single file wiki and try out your usual workflows. It is suggested that you use a copy of your real life wikis, ie complex wikis that you’ve tweaked and personalised over a long time, so that the new version is tested under tough conditions
Please wait until the official release before updating your day-to-day wikis, and remember the first rule of TiddlyWiki: to make sure to take (and verify) backups before doing anything risky.
Best wishes
Jeremy
Update 17th July: As discussed elsewhere, the next time we ask for user testing we need to outline in more detail a good testing strategy, including testing critical functionality.
I’ve tested nine wikis I own, and found no regressions.
I will try to find time to test some of the updated features, but none looks likely to have any real effect on the wikis I write.
I have a few older wikis that I would like to test, but they are currently in broken/incomplete states, and it’s harder to test them; I’ll attempt to do so over the weekend.
At the moment I publish TiddlyWiki to npm using this batch script. It would be vastly preferable to use GitHub Actions, which would indeed give us more flexibility for publishing nightlies etc. Perhaps we can move this discussion to a GitHub ticket.
Are you still accepting translation PRs (i.e. language plugin updates) before the release please? I have translated 6/15 sections just today and should be able to complete more over the next few days.
If it won’t be possible to put it into 5.3.7, just let me know and I can take a bit more time with it.
Thanks, it is coming along well by the way. Looking forward to realising saver-less versioning in particular in this release, which was improved by PR 8956.
I assumed the lack of buttons was deliberate, since what’s being described isn’t a single button that performs an action, but two different buttons that toggle state (folded/unfolded). Depending on the state, you either get a vertical bar with ︽ or a horizontal bar with ︾ ).
How would you describe that in the tools option menu there?
It’s interface is not in alignment with the other tools though. All others appear as control buttons to the top right of a tid, whilst the fold/unfold never appears there, and itself changes appearance and location depending on the fold state.
I agree the idea that the UI could be improved, but to my mind the improvement would be in the direction of making it clearer that this isn’t a single button standard control like the others.
How’s this for an idea that should be simple to implement: The option be indented to nest under the ‘fold’ option above it (since it’s conceptually the same actions) and the fold/unfold buttons be incorporated into the text.
IMO this is just an option to switch on the global tiddler fold / expand options. It is there for convenience reasons. I think it does not really need a button.
Usually global options are berried in the ControlPanel → Settings tab, which imo has a lot of room for improvements. (Not to say: It is a complete mess)
Hi,
I’m not sure if this is the right place or the right time to bring this up again, but I wanted to mention that I often fall into the trap of opening and closing three curly braces {{{}}} in the test widget in order to fill it afterwards. This results in a freezing output (occurring since version 5.3.0 and also in the edit>preview). As I am not very experienced and do all my programming and testing directly inside TiddlyWiki, this keeps being an issue for me.
Just a friendly reminder that this bug is still present in the latest pre-release.
For reference on github: #8373[BUG] recursive failure in TestCaseWidget transclusion tests beginning with {{{}} · Issue #8373 · TiddlyWiki/TiddlyWiki5 · GitHub #8155 #8147https://github.com/Jermolene/TiddlyWiki5/issues/8147
Please let me know if I can provide any more information or help with testing. Thank you for your work!
