Disabling Wallabag and Other Plugins Through Code

Maimun Ahmed · 03-17-2024, 09:46 PM

Hi there Mobileread friends, I have a question to ask. I don't often use some of the plugins in KOReader (eg, wallabag) and I am willing to disable (or better, remove) them. I think there is an option in KOReader called plugin management that allows me to disable them, but why not completely remove it from the code. Is that possible to do so?

My current working solution is to detect the widget.name and prevent its pcall if it's the widget I don't want in filemanagermenu.lua and readermenu.lua.

pazos · 03-18-2024, 10:29 AM

You can remove them but they will get downloaded again on each new update.

And makes no sense to remove them: all the plugins together are less than 2MB size. So, unless you need those megabytes you're better disabling them via the plugin management system.

Or, if you want them removed, make yourself a "0" userpatch that does that. See https://github.com/koreader/koreader...tches#overview

Half-backed solutions like the one suggested in OP give no real benefit over disabling plugins by usual means, and shall not be used.

nixR3ad · 03-18-2024, 10:49 AM

Removing them might be necessary if he is developing patches or his own plug-ins. Plug-ins s are "plugged in" because they can break new distribution development at times
.

Frenzie · 03-18-2024, 01:45 PM

You can remove the plugins, but as stated any update will put them back. If you want to hack on them it's generally better to duplicate it and name it for example wallabag2. Disable regular Wallabag with the plugin manager.

Maimun Ahmed · 03-22-2024, 01:24 PM

Quote:

Originally Posted by pazos

You can remove them but they will get downloaded again on each new update.

Yeah, the update will bring back all the default plugins but I have made some other customisations to the source codes which will anyways break KOReader upon updating. So yeah, I won't be updating KOReader anyways.

Would have been great if there was a direct solution, like removing it from source code altogether.

Edit: Seems like I got the solution. Please reply below if anyone is also searching for the solution.

03-17-2024, 09:46 PM	#1
Maimun Ahmed Mr. Developer Posts: 24 Karma: 10 Join Date: Feb 2024 Device: Kindle Voyage	Disabling Wallabag and Other Plugins Through Code Hi there Mobileread friends, I have a question to ask. I don't often use some of the plugins in KOReader (eg, wallabag) and I am willing to disable (or better, remove) them. I think there is an option in KOReader called plugin management that allows me to disable them, but why not completely remove it from the code. Is that possible to do so? My current working solution is to detect the widget.name and prevent its pcall if it's the widget I don't want in filemanagermenu.lua and readermenu.lua.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[Metadata Source plugins] Calibre internal plugins fail	igorius	Plugins	1	05-28-2023 12:42 PM
Wallabag feeds	Jedi	KOReader	4	01-08-2023 08:06 PM
Free server for wallabag?	amin021023	Android Devices	6	09-23-2022 04:10 PM
Systemwide installation of plugins / Discovery of installed plugins via pkg_resources	t-8ch	Development	8	11-14-2020 10:25 AM
Getting PyCharm code completion while writing Calibre plugins	trying	Development	6	03-30-2014 06:47 AM

03-18-2024, 10:29 AM	#2
pazos cosiñeiro Posts: 1,330 Karma: 2200073 Join Date: Apr 2014 Device: BQ Cervantes 4	You can remove them but they will get downloaded again on each new update. And makes no sense to remove them: all the plugins together are less than 2MB size. So, unless you need those megabytes you're better disabling them via the plugin management system. Or, if you want them removed, make yourself a "0" userpatch that does that. See https://github.com/koreader/koreader...tches#overview Half-backed solutions like the one suggested in OP give no real benefit over disabling plugins by usual means, and shall not be used.

03-18-2024, 10:49 AM	#3
nixR3ad Enthusiast Posts: 25 Karma: 10 Join Date: Jan 2024 Device: Sage / rm2	Removing them might be necessary if he is developing patches or his own plug-ins. Plug-ins s are "plugged in" because they can break new distribution development at times .

03-18-2024, 01:45 PM	#4
Frenzie Wizard Posts: 1,675 Karma: 730583 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	You can remove the plugins, but as stated any update will put them back. If you want to hack on them it's generally better to duplicate it and name it for example wallabag2. Disable regular Wallabag with the plugin manager.

Advert

Advert