We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Since updating to this version I keep getting this when start OctoPrint.
Optional plugins To get the real power of the Print Job History - Plugin you need the following plugins installed/enabled:
FilamentManager (missing) disable optional plugin check Close
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.
The text was updated successfully, but these errors were encountered:
Issue also reported here with more details from different users: #38
Sorry, something went wrong.
New Verison 1.7.2
c7d8410
#37, #38 NewFilamentOdometer missing in GitHub-Repository
No branches or pull requests
Describe the bug
Since updating to this version I keep getting this when start OctoPrint.
Optional plugins
To get the real power of the Print Job History - Plugin you need the following plugins installed/enabled:
FilamentManager (missing)
disable optional plugin check Close
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.
The text was updated successfully, but these errors were encountered: