Disabling a plugin is easy. Control Panel → Plugin → Disable.
How does one uninstall/ remove a plugin?
Also, are there any benefits of uninstalling over disabling or vice-versa?
1 Like
A plugin is a tiddler. Click on it and it opens in the story river as any other tiddler. Open it for edit and delete it. Save your tiddlywiki and refresh and it is all gone.
Disable/enable of plugin is easy if you need it again.
Deleting a plugin - you will need to find it and import it again - if need be.
If you have many plugins they will make your tiddlywiki grow fast and you have the risk of some plugin interfering with other of your plugins.
Everything Birthe said.
An in-between solution is to maintain a tw file as a library of plugins. Then you can delete ones you don’t want from your working TW file, but drag and drop it back in when you need it again. Lately I’ve started using the plugin library mechanism, so I can import from my own library of plugins just the way I can from the official plugin library.
@Mark_S did you automate the library creation process?
I am looking to do so, on top of single file wikis so I and anyone can easily move plugins and other content to a library they can access locally, along with the opportunity to publish. I would do this via the Generation of a Zip tiddler contain the appropriate files.
Exactly my thinking. I install a plugin and don’t find it useful. But it is still lying around. After a while, there are many such. Will disabling these will produce the same result as deleting them with respect to the responsiveness of TiddlyWiki and interference with other plugins?
Disabling the plugin should be enough. I just do not understand why you would keep a plugin, you do not use. Why not just make a note of where you got it from - link. Then you can always install it again, if you so wish.
No matter if you disable or delete plugins, you have to make sure, they are not leaving anything behind. That happens if any of the plugin tiddlers are overwritten in use. Just look at the content of the plugin and you will be able to tell the difference.
It is easy to leave something that will make finding the cause of errors more difficult. You are the only one knowing what is in your own wiki if it is not shared .
I’m not sure what would qualify as “automate”. I’ve modified the library build command so it removes core plugins and puts the resulting library I where I want.
The real problem is finding the source plugins, downloading, and moving out the plugin portion. Sometimes this means downloading the zip from gh, extracting, moving. And since I’m using GH, I have add each new author to GH tracking.
And of course if the library exists only as a tiddler, it needs to be exploded first.
So far my “library” consists of four plugins 
Thanks @Mark_S
I want to avoid the use of the “library build command” and do this from the single file wikis.
I have some good workflows without node, so I don’t have the same troubles such as;
- Finding source plugins
- Moving out the plugin (not necessary)
I would be happy to share these practices however they are all based on single file wikis.
My automation desire is in a single file wiki containing all the necessary plugins and other tiddlers that a list or filter combination selects the tiddlers, and a button click generates the library in a ZIP file. Then extract this on the host, then drag and drop the generated library tiddler on the host wiki. From there all one needs to do is share the library tiddler.
Later I would consider some possible version control for updates.