Today I took out MWS and played with it again. I also wrote a script with AI that allows me to edit TiddlyWiki and output tid file content at the same time. When I think the script is well written, I plan to configure my MWS well. Then during the process of importing plugins, I imported a relatively large plug-in, and the whole TiddlyWiki was stuck. Restart also has no effect.
Plugin is $:/plugins/custom/combined, this is a bundle plug-in, which is codemirror6 plug-in package, I did not find problems on my own running wiki, but when importing MWS there was a problem.
I’m not saying there can’t be a problem, but there’s no protection or fallback mechanism. Using the nodejs version of TiddlyWiki, it’s easy to implement this mechanism, after all, essentially loading those tid files, as long as you use git to fallback, there’s no problem.
There may be other options, but I don’t see them.
@Arlen22 may be able to help.
I didn’t write much of anything valuable, just configuring it. So I don’t really need to restore the database. But this protection mechanism should be necessary, at least to go back to a certain point in time. It’s best to save it every few minutes in the editing state. If it’s not editing state, it can be saved once a day.
I understand your problem is downstream of what you are trying to do, but;
I think when coding in this space you need to have a good understand of the save and export mechanisms in tiddlywiki. After all when you move to MWS you are specifically choosing a platform which has a different saving mechanism.
With 5.4.x there is a new mechanism for Background Actions which could be used when a tiddler is closed, in contrast to on each save/edit.
ie
There is always a risk if you come to tiddlywiki as a javascript coder, or now also as a LLM vibe coder in JavaScript that you will use javascript.
The saying is: “If all you have is a hammer, everything looks like a nail” (also known as the Law of the Instrument or Maslow’s Hammer). It means people tend to over-rely on familiar tools or methods to solve problems, even when they are inappropriate
like a hammer "
I really think a way to assist in avoiding this misuse of JavaScript in TiddlyWiki is to ask the community in a technology agnostic way. This will help you and the community;
- Provide solutions based on available methods
- Craft new solutions based on available methods
- Share prior work on this including existing plugins and JavaScript solutions
- Get the opportunity to identify if and when Gaps in TiddlyWiki are present and start the process of extending common plugins or the core to accommodate this in future.
- Get support from coders and vibe coders in such a way as they also understand the root problem you are trying to solve.
Perhaps you have already done this, but I just thought it timely to point this out again, this is particularly important when developing solutions that somehow alter the TiddlyWiki as a Platform itself, even if it is for your private use only.
To be clear, the wiki won’t load due to these errors, but the admin pages still work? If that’s correct, you could create a new empty bag, then change the wiki recipe to use the empty bag instead of the one with the problematic plugin bundle.
A way to directly edit bag contents in the admin interface has been requested, but hasn’t yet been implemented. If you’re comfortable with SQL, you can manually edit the database (I’ve done this to drop all tiddlers from a bag).
Also, how have you set up your MWS instance? The latest in GitHub may have some breakages that aren’t in the NPM package.
