ThirdFlow throwing dozens of errors

[kodomohimari]

My installation: standard TW5 (NodeJS version, installed globally on a Raspberry Pi, automatically launched at Raspberry reboot).

I discovered ThirdFlow this morning (http://thediveo.github.io/ThirdFlow/) and was sort of interested by the tag folders functionality so I tried dragging the .tid download (plugin) to my installation. The plugin (apparently) imported correctly, adding the folders tab in the Settings tab... and then I started getting dozens of error messages. Trying to use the tag folder functionality didn't work and eventually my installation broke down and I had to manually remove the plugin and a preference file it had created.

Is this soft still supposed to be relevant, and is there any reason in particular why it should have failed?

The error messages started with "Sync error while processing '$:/config/FileStorage/tagfolders thirdflow", if this is any help.

Thanks for reading,
kodomohimari

[PMario]

Hi,
ThirdFlow is quite old already and it changes a lot of system related tiddlers.

So imo it would be easier to go with: http://tiddlywiki.com/#Customising%20Tiddler%20File%20Naming ... which is part of the core now and does a similar thing.

have fun!
mario

[kodomohimari]

Ah, I actually saw that one earlier but I haven't been able to find a way to apply it retroactively... Is there any way for this method to dynamically re-check every tiddler in the TW instance and rename whatever deserves renaming?

Thanks a lot for the clarification about ThirdFlow.

[PMario]

On Monday, September 18, 2017 at 11:45:13 PM UTC+2, kodomohimari wrote:

Ah, I actually saw that one earlier but I haven't been able to find a way to apply it retroactively...

Not really. The settings work for new tiddlers only. .... but

 

Is there any way for this method to dynamically re-check every tiddler in the TW instance and rename whatever deserves renaming?

 - You can create an empty TW

 - Change the settings in a way that work for your

 - Drag and drop import an existing TW.

 - Importing should treat every tiddler as a new one, ...

That's the only way I can think of. ... but I didn't test it.

-m

[kodomohimari]

Alright, just tested. Actually this works shockingly well, better than I would have hoped. Process below:

- Backup the TW as .html (simpler to wield than a potentially huge amount of individual tiddler files).
- Create a new server instance (http://tiddlywiki.com/static/Installing%2520TiddlyWiki%2520on%2520Node.js.html using these instructions).
- Import your $:/config/FileSystemPaths tiddler by dragging the .html backup in that instance and unticking everything but that tiddler.
- Then, import the remainder of your .html backup by repeating the above step and ticking everything instead. (This is to make sure $:/config/FileSystemPaths is live by the time everything else gets imported). Most likely you'll want to overwrite everything when there's a conflict (assuming your backup had up-to-date code).

Because backing up the TW as .html ignores folder structure and thanks to TW's great plasticity, this process can probably be repeated ad infinitum (i.e. you can change your folder logic in $:/config/FileSystemPaths and then repeat the process as often as you'd like, incrementally remodeling your TW server into the shape of your desires).

Thanks a lot for the tip! This solved my problem, and them some.

kodomohimari