New release: 1.3.2

I didn’t get any feedback concerning 1.3.2rc1 at all - I’m assuming that means that all is well with it and not that nobody tried it ;)

This a true maintenance release again, consisting of various improvements and fixes.

Some highlights from the release notes:

• Better handling of really long “dwell”/G4 commands on Repetier firmware - especially interesting for Wanhao D6/Monoprice Maker Select users, since for those printers end GCODE that sends a several minute long G4 before switching off the nozzle fan appears to be quite common and caused problems with OctoPrint running into timeouts before.
• The safe mode introduced in 1.3.0 is now way more accessible through a new entry in the “System” menu (if the restart command is configured). See below for a screenshot. You can learn more about safe mode in the documentation. Please also note that the bug reporting guide now instructs you to test if a bug you are reporting manifests in safe mode - if not it’s likely caused by a third party plugin and should be reported there.
• Better error resilience in various cases (wonky plugins, wonky printer firmware, wonky update configurations).
• Found a work around for a timelapse color distortion issue that has been plaguing some people for a long time now.
• OctoPrint now allows defining a shared nozzle for multi extruder setups in its printer profiles. If a shared nozzle is configured, OctoPrint will only track one hotend temperature in the temperature tab but still allow extruding from any of the configured extruders on the Control tab. See below for a short GIF on how to do that.
• When navigating into sub folders in the file list, OctoPrint will now display the path to the currently active folder beneath the “Back” button. This should help to not get lost in your file hierarchy ;) See below for a screenshot.

There is a heads-up for plugin authors who extend the JavaScript Client Library, to quote the Changelog:

If you maintain a plugin that extends OctoPrint’s JavaScript Client Library like demonstrated in e.g. the bundled Software Update Plugin you’ll need to update the way you register your plugin to depend on OctoPrintClient and registering your extension as shown here instead of directly writing to OctoPrint.plugins (like it was still done here). That way your extensions will be available on all instances of OctoPrintClient, not just the global instance OctoPrint that gets created on startup of the core web interface.

If all you plugin does with regards to JavaScript is registering a custom view model and you have no idea what I’m talking about regarding extending the client library, no action is necessary. This heads-up is really only relevant if you extended the JavaScript Client Library.

The full list of changes can of course be found in the Changelog - as always.

Also see the Further Information and Links below for more information, where to find help and how to roll back. Thanks!

Further Information

It may take up to 24h for your update notification to pop up, so don’t be alarmed if it doesn’t show up immediately after reading this. You can force the update however via Settings > Software Update > Advanced options > Force check for update.

If you don’t get an “Update Now” button with your update notification, read this or - even more specifically - this.

If you are running 1.2.7, get an “Update Now” button but the update is immediately reported to be successful without any changes, read this.

If you are running 1.2.16, get an “Update Now” button but the update is immediately producing an error message, read this.

If you have any problems with your OctoPrint installation, please seek support in the G+ Community or the Mailinglist.

Links

• Changelog and Release Notes
• FAQ
• Documentation
• Contribution Guidelines (also relevant for creating bug reports!)
• How to file a bug report
• How to roll back to an earlier release (OctoPi)
• How to roll back to an earlier release (manual install)

Images