https://tiddlywiki.com/upgrade contains the upgrader to the latest stable release, which is great, but sometimes might feel limiting.
Take the Cardo thread example above. Quote:
it stopped working with newer versions of TiddlyWiki
So I assume if somebody takes the Cardo wiki from https://dyumnin.com/Cardo.html and runs it through the updater, the resulting wiki won’t work. Which makes me wonder, is there somewhere a full public list of updaters, one for each stable release of TiddlyWiki? Or a copy-pasteable command line incantation to generate all the updater versions from the TiddlyWiki Git repository? This could prove useful to somebody trying to revive a legacy wiki, by helping to narrow down the focus area. Having a list of updaters starting with version 5.1.19 and ending with latest 5.3.8, one could apply the Bisection (software engineering) - Wikipedia approach and in a few steps find the exact offending TiddlyWiki version that broke Cardo.
If you go to tiddlywiki.com and type in “Release” you get a long list of Releases and you may have to scroll down. I am not sure if this answers your question.
Your suggestion sounds like a good idea. I have not done so yet.
This rather complements it, since a brief release changelog is always useful as first read before diving into code diffs. Yet I don’t see how it answers my question. Take https://tiddlywiki.com/#Release%205.2.0 for example. It’s a long tiddler and I skimmed through it but I don’t see it linking to the upgrade page for that version. I have searched the tiddler page for “update” and “upgrade”, but found nothing relevant. If you had Cardo and wanted to upgrade it to 5.2.0 to see if it works, how’s that page useful?
You might want to check https://tiddlywiki.com/archive/, which has a list of all releases from v5.1.0 (20-Sept-2014) through v5.3.8 (07-Aug-2025).
Each release has a link to a “complete” version (i.e., including all tiddlers and documentation), and an “empty” version (just the TWCore tiddlers and shadows). However, it doesn’t include the corresponding updater for each release.
Nonetheless, the archived “empty” versions can still be useful for identifying which TWCore release caused a plugin to break.
Begin by downloading the “empty” for the last known working release and import/install the plugin(s) you need, and then test to confirm that it still works in that version.
Then, repeat the process with progressively newer releases until the plugin fails.
Once you’ve identified the release that triggers the problem, you can try to compare it with the immediately preceding release to determine which TWCore shadow tiddlers have changed and thus narrow down the culprit.
Sure… this process can be really tedious, but it might be the only way to identify the cause, especially when trying to “revive a legacy wiki” that might not have been actively maintained and upgraded for a very long time.
The links in the Version column of that table are all broken (404).
Fortunately, the Empty and Complete links for each version are functional and the workflow that you suggest (starting from the Empty wiki and importing into it) looks like a fair alternative to a straight upgrade of the legacy wiki.
So it needs some work after updating