I see that a subset of those third party plugin libraries link to their home pages (CPL does not). Would be nice if we updated the header of that thread so all libraries there link to their home pages, in case the attached .json files become outdated.
I tried to refactor CPL to be a TW nodejs server route based plugin, seems I break the old HTML version. But only break the UI for human, you could still load plugin list inside TW, if you have its client side plugin installed.
This is my original concern. Where does a hypothetical first time user find it online? If you exclude this official forum, what’s the site that hosts the .json file that has to be downloaded and imported into a wiki to be able to use the plugin library?
Welcome to the ‘’[TiddlyWiki Chinese Community Plugin Source]‘’!
This plugin source is maintained by the [[TiddlyWiki Chinese Community]] and is dedicated to collecting all TiddlyWiki5 related plugins on the web, hoping to provide a one-click installation and update plugin experience for TiddlyWiki users in China and around the world.
If you don’t know how to use TiddlyWiki and this source, you are welcome to read the plugins related section in the [[TiddlyWiki Tutorials for Chinese Communities|https://tw-cn.netlify.app]]. As mentioned above, both the plugin source and the tutorial are open source projects, you can find them in [[GitHub|https://github.com/tiddly-gittly\\]] and participate in contributing! If you like, you can join us through QQ groups and other means, see the Chinese tutorials mentioned above for details.
To add this plugin library to your Wiki, just drag this link with your mouse into your Wiki: <$link to=<>>{{!!caption}}</$link>
Note: The source version of this plugin is a version accelerated by netlify.app, which is more friendly to China mainland users, but there is a delay in updating. There is also another version that uses the GitHub Page server directly, which is faster to update, but may require technology to overturn the GF@color.
@@color:red;‘‘Please remember to back up your Wiki before installing any plugins, this plugin source cannot be held responsible for personal losses caused by plugins!’’@@
And soon, the Node.js TiddlyWiki server version will be online; I will host it on my own server on my company using FRPC to securely reverse proxy to a volcengine ECS and publish as online Tiddlywiki website + NodeJS server route API. API will be used for rating plugins or get old version of plugins.
For an empty 5.4.0 wiki, I can go to Control Panel → Plugins , click on the blue button “Get more plugins”, click on the green “Open plugin library” and install plugins.
After installing CPL, after going to Control Panel → Plugins and selecting “Official TiddlyWiki Plugin Library” tab, I get no access to official plugins anymore. Instead it says “For a better experience, we recommend you ‘Open CPL to install plugins’”.
Is this a bug?
Note that CPL has its own tab in that window, why is it interfering with the official plugins like this?
The tiddler you’re linking to mentions Node.js. I am using single HTML file wiki. Perhaps you can add a hint about temporarily disabling CPL if one needs to install official plugins after having CPL in a single file wiki. This requires a bit of additional work, but at least less technically competent users like me will know (or remember, because I’ll likely forget this in a couple of months) what to do.
It is the old stuff that not recommending install plugin from plugin library in NodeJS wiki, should we just remove it? We discussed it 5 years ago.
Because new recommended way is just use Plugin library to install anything, when user don’t have CPL plugin installed. If have CPL, could even just only use CPL.
@vuk About your original post, a new site https://cpl.tidgi.fun is now hosted on one of my spare server, and I will migrate it to my k3s server cluster today, servers are distributed located from north to south in China, and will auto re-hosted when one of server offline by using “k3s”.
The outlet of k3s server cluster is a cheap 4C4G volcengine, ¥ 145 a year (20$).
