Closed taker218 closed 3 years ago
This happened to me because of the UI customizer plugin hiding it. I 1) opened the UI customizer settings 2) hit save without changing anything 3) saving defaulted to not showing the Filament manager plugin for some reason.
Without saving the settings, UI customizer probably defaulted to show everything, but the settings window doesn't default everything to "on". After saving some of the UI components are turned off
Perhaps someone should file a bug report over there?
I think that's another problem @msEmmaMays
I can see the plugin and everything, but I can't select a spool. It doesn't show any spool to select, but the selection box is there. I know this is a problem of how the plugins are able to check for a network connection and I already tried to start octoprint after the network is online, but this didn't work. Octoprint would start at all like that.
This issue has been automatically marked for closing, because it has not had activity in 30 days. It will be closed if no further activity occurs in 10 days.
Hi @taker218,
is the selection box empty or not possible to select a single spool? Or is the box "greyed out" (disabled). Reason for disabled: printer state = printing or user is not logged in
please try the following:
PS. Sorry, for being late to the party, but I made a "Octoprint sabatical" (no coding, no printing) the last months.
Hi,
the selection box was empty, but right now I can't recreate the problem on any of my installations. I thought it was a a problem related to python 2 because I can't recall the problem to have happened with my python3 instances. But right now it doesn't happen any more.
nevermind, I just realised I havn't installed the psycopg2 on the new installation.
Describe the bug When I reboot the OctoPi instance (complete reboot, not just restart) I can't select any spool. I am using an external database for my instances and this is on every one of them. I know this might not be completely bound to this plugin, but maybe you have an idea how to work around this problem.
Once I restart octoprint (via webinterface) the selection is possible. It might have something to do with the way octoprint is starting. I don't know if the octoprint service is waiting for the network to come up. And as far as I know from the old plugin author, the plugin only checks on startup of the instance, if the remote database is available. If not, you don't get a selection.
Steps to reproduce
Expected behavior A clear and concise description of what you expected to happen.
Did the same happen when all other 3rd party plugins are disabled? If not which plugin is causing the issue?
Log file Drag and drop the octoprint.log here.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.