New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank plugins preferences in git master #667
Comments
|
Ah yes. I forgot to strip the "Plugins" tab from the preferences dialog. The idea is to have only one place for "Plugins" which is the plugin installer available from menu via "Tools" -> "Plugins". |
|
But the plugin installer is itself a plugin. If it replaces the plugins preference tab, maybe it should be made part of the app first. |
|
It is a mandatory and hidden plugin. It cannot be disabled by the user. |
|
Now i have neither Tools->Preferences->Plugins nor Tools->Plugins. Am i missing some python dependency? |
|
@sillyslux Seeing the same thing. I don't think it's a missing dependency issue. Looks more like something was overlooked in afc3c04. Until properly fixed, you should be able to get/set active plugins via
|
|
@sillyslux @glitsj16 Above commit ensures the plugin installer cannot be disabled. I hope this helps. |
|
@lwindolf Thanks for looking in to this. There seems to be some confusion though. As sillyslux mentioned above, the issue is not that plugins aren't loaded/unloaded or accidentally disabled somehow. Current git master simply does not show a GUI menu item 'Tools > Plugins' (not even when including your latest commit). Looking at https://github.com/lwindolf/liferea/blob/master/plugins/plugin-installer.py now to figure out why that menu item is still missing. |
|
I think it should be loaded in |
|
Agreed |
By coincidence I wanted to check Liferea's plugins preferences, only to notice the view is empty (in Liferea compiled from current git master). Plugins still work though, only the
plugins preferences paneis affected.After some rebuilds and more testing it looks like this recent plugin-related commit is causing the issue for me (on both Arch Linux and Ubuntu 16.04 LTS). At least the issue disappears when reverting the aforementioned commit. I hoped to offer some kind of debug log, yet running with
--debug-alldidn't produce anything helpful (or I missed it). If anyone has pointers on how to debug this further, I would be more than happy to do so.Regards
The text was updated successfully, but these errors were encountered: