I'm primarily using node.js client-server TW5. I've just finished migrating my plugins from individual client wikis to the server (under the default location of /usr/local/lib/node_modules/tiddlywiki/plugins). Today I upgraded node.js TW5 from 5.1.20 to 5.1.21 and got a rude surprise when it silently deleted all plugins from this default directory and (re)installed only the core plugins. I very thankfully had a backup so this was trivial for me to recover from, but it was still unexpected and potentially very inconvenient.
The best way to avoid this problem would be to quarantine non-core plugins during the upgrade process. The next best solution would be to build a warning into the upgrade process if non-core plugins are detected in the default location, with an option to abort. Failing either of those, I suggest a prominent warning be added to documentation tiddler [[Upgrading TiddlyWiki on Node.js]]. Since this near miss I have moved my plugins out of the TW5 server install tree and set environmental variable TIDDLYWIKI_PLUGIN_PATH accordingly. It might be worth explaining in documentation tiddler [[Environment Variables on Node.js]] that a major benefit of relocating non-core plugins (and themes, etc.) from their default locations is to avoid silent deletion during upgrades. Regards, David Note: By 'non-core' plugins I mean plugins other than those installed under /usr/local/lib/node_modules/tiddlywiki/plugins/tiddlywiki. I realise they are not 'core' in the sense of being necessary for ordinary TW functioning. There is probably a more accurate label I could use. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/5683bfe7-6d46-42fe-b87d-76ba60b0e604%40googlegroups.com.
