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
can't open its settings or disable it from logseq's built-in plugins menu #8
Comments
It sounds like an issue with Logseq itself, not the plugin. BTW, you can also disable the plugin by toggling the switch on the right. |
I can open settings for all the other plugins though..? and actually the "thus I can't disable this plugin from the logseq interface" part is referring to the switch on the right. |
actually a week ago I also tried this plugin. At that time I had the same problems but I also tried manually editing its settings file, which did not work. Last week I couldn't even uninstall this plugin via the GUI --- I had to manually delete its folder. At least now that doesn't seem to be a problem anymore, but I doubt manually editing the settings file would work so I haven't tried that again yet. |
You should report this to the Logseq team, plugins themselves can't control installation and uninstallation. It seems that for some reasons, you files are corrupted. |
okay noted👌. your "TOC Generator" has been working fine for me so i thought it was weird. |
Just wanted to share that I'm facing the same problems with the latest version (clicking on "open settings" doesn't do anything; also can't disable the plugin using the provided switch). I'm not experiencing similar problems with other plugins. For now, I'm uninstalling it. Will try at a later time. |
@asifm I later realized it was caused by my own mistake (a trailing comma in the settings file after making my own changes). after removing the comma or whatever syntactical error it may have, relaunch logseq and it should fine. |
This button does not open the corresponding file, while the setting files themselves are empty, not even including the
{ "disabled": false }
part, and thus I can't disable this plugin from the logseq interface.Environment: Windows 10, logseq 0.6.3
The text was updated successfully, but these errors were encountered: