As an early christmas present 🎄 I’m happy to present you OctoPrint 1.3.6. This a true maintenance release again, consisting of various improvements and fixes. It was made possible only through your continued support of my work 💕.

The most important thing first: This release introduces a potentially breaking change with regards to how JS plugin assets are bundled - you can read all the gritty details here. Not many plugins should be affected by this, but some are and for that I also added a little (temporary) feature toggle that will allow you to go back to the old way of bundling (with all its downsides) until those plugins that are affected and that you rely on are updated. You can find that toggle under “Settings > Features > Enable legacy plugin bundling”. Affected plugins will produce errors in the JS console and most likely stop working in the browser - so if you encounter that for a plugin after updating to this version, try enabling that flag, saving and restarting your server and see if that fixes things - and if so best report the incompatibility to the plugin author. The plugins that so far are known to be affected by this are

Navbar Temp up until version 0.8 - version 0.9 is fixed!

Fullscreen Webcam up until version 0.0.3 - version 0.0.4 is fixed!

With that out of the way, on to some highlights from the release notes:

Over the course of the past couple of months I saw a lot of support requests about failing updates that turned out to be caused by corrupted git checkouts, which OctoPrint so far relied on to update itself. Starting with this version I’m going to take out the middleman (unless you are running explicitly on commit based tracking) and just use pip . That should remove a lot of potential reasons for failure from the equation in the future.

. That should remove a lot of potential reasons for failure from the equation in the future. A new centralized plugin blacklist allows to prevent plugins/certain versions of plugins known to cause crippling issues with the normal operation of OctoPrint to be disabled from loading, if the user has opted to do so in the settings/wizard.

The aforementioned change in the JS plugin asset bundling will better isolate plugins from each other and greatly reduce the risk of them interfering with each other - which was the reason this was added to begin with.

File and folder names now support the full UTF8 character set (at least in the file list itself - on disk they’ll still stick to ASCII to reduce the likelihood of cross platform issues). So if you want to have a folder named “Favorites 🌟” or a file named “Ümläutmadneß.gcode”, that’s now a possibility. See below for an example.

The API key fields and the Terminal tab now have shiny new copy buttons that should make it so much easier to get their contents quickly.

The GCODE viewer now also exposes a couple of more advanced options that might help with the one or other GCODE file, and its options are now persisted in your browser so you don’t have to reset them every time you reload.

The new “OctoPi Support Plugin” - which will only load if an OctoPi instance is detected as the underlying OS - will now make sure to add the OctoPi version to the version string reported in the lower left corner of the UI. That should hopefully clear up a lot of the usual version confusion I’ve seen in the past. Additionally this and a couple of other info snippets about the detected environment (like python & pip version and underlying OS) will now be logged on startup to ensure this information is easier accessible in case of reported bugs or on support requests with accompanying octoprint.org . This may not look like something exciting, but it will make helping each other so much easier going forward.

. This may not look like something exciting, but it will make helping each other so much easier going forward. Of course I also fixed some bugs as usual. That also includes working around some issues in Firefox (drag-n-drop not properly terminating under certain conditions and the API key not being copy-able due to FF interpreting the disabled flag on input fields differently than all other browsers), solving some problems with temperature reporting on shared nozzle setups, handling a specific kind of communication error correctly and being more error resilient against unexpected firmware responses and corrupted data in general.

flag on input fields differently than all other browsers), solving some problems with temperature reporting on shared nozzle setups, handling a specific kind of communication error correctly and being more error resilient against unexpected firmware responses and corrupted data in general. … and much more

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.

And last but not least a special Thank you! to everyone who reported back on the release candidates this time: andrivet, b-morgan, bjarchi, chippypilot, ChrisHeerschap, cosmith71, Crowlord, ctgreybeard, fiveangle, goeland86, jbjones27, jneilliii, JohnOCFII, Kunsi, Lordxv, malnvenshorn, mcp5500, ntoff, ripp2003 and schorsch3000.

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 were running 1.3.6rc1 or 1.3.6rc2, downgraded back to 1.3.5 and now can’t update and/or select your release channel, please read this.

If you get an error about “no suitable distribution” during update, please read this.

If you have any problems with your OctoPrint installation, please seek support on the Mailinglist.