Introduction eLabFTW 5.1 has been released! This new version brings many new features, enhancements and a few bugfixes. This blog post highlights some of these changes, but the complete list of changes is available on the release page. Important change A breaking change has been introduced in APIv2: /team_tags has moved to teams/{id}/tags. If you have scripts using /team_tags, replace it with teams/current/tags to maintain the same behaviour. Video A video has been produced, summarizing some of the features:

Introduction The 5.0.0 release is a major release. You can tell because before it was 4.x.y now it’s 5.x.y. But what does it mean exactly? The major version number has been bumped because there is a breaking change: complete drop of APIv1. And that’s it, that is the only big thing that changes, and hopefully it won’t impact many users, as everyone is now using APIv2, right? right? Now, let’s talk about the other changes present in this release.

Introduction This is a relatively small release, but it contains a major change that impacts many aspects of the application: a rework of the status and categories. You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update (for Sysadmins) Update like usual: see documentation. New features Users features Rework of Status and Categories This work was sponsored by Vrije Universiteit Brussel, a big thanks to them!

Introduction This release contains at least a dozen bugfixes and many new features and improvements, all users should update. You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update (for Sysadmins) Update like usual: see documentation. New features Users features Improvements for extra fields Extra fields can now have units (for input of type “number”).

Introduction This release comes quickly after 4.6.1, and thus contains only a few bugfixes and new features. Normally the bugfixes would go in 4.6.2 and new features in 4.7.0, but this time it’s a bundle with both. So what’s new in this version? You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation.

Introduction This release features a major user interface redesign. We worked a lot on improving how the app looks and feel, and we hope you’ll like it. So what’s new in this version? You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation. New features General changes Interface redesign The first thing that you’ll notice is the improved interface.

Introduction This release comes quite fast after the release of 4.4. The goal being to bring new features and bugfixes to end users faster. So what’s new in this version? You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation. New features Users features Major feature: improved permissions system The permissions system has been overhauled.

So what’s new in this version? You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation. New features User features Reaction drawing Previously the chemical structure editor would only allow one molecule, now you can have several. Reactions can be saved as .chemjson files and re-imported in the editor.

I’m very pleased to announce that eLabFTW, the free and open source electronic lab notebook version 4.3 is now available for everyone! So what’s new in this version? You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation. New features General Soft delete: an entry will now be marked as deleted instead of being actually deleted from the database Same with uploaded files that are replaced More than 22 bugfixes!

I’m very pleased to announce that eLabFTW, the free and open source electronic lab notebook version 4.0.0 is now available for everyone! This new version is PACKED with new features! You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation. New features Users features Experiments/items can no have a visibility of “user only”, previously this corresponded to owner + admin(s).

I’m very pleased to announce that eLabFTW version 3.6.0 is now available for everyone! You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation. New features LDAP Authentication It is now possible to authenticate directly using LDAP. A much awaited feature (github issue). The documentation about this feature can be found here: https://doc.

I’m very pleased to announce that eLabFTW version 3.5.0 is available for everyone! This new version contains a lot of new things and a few fixes and improvements from the previous version. All users should upgrade! You can see the complete changelog on the release page. This blog post is more about going into details for some of the changes. How to update Update like usual: see documentation. New features Enforce read/write permissions by admin The Admin of a team can now enforce read and write permissions for experiments of users in their team.

I’m very pleased to announce that eLabFTW version 3.4.0 is finally available for everyone! This new version contains a lot of new things and a few fixes and improvements from the previous version. All users should upgrade! This version took a long time to get out because it involved a lot of work to make some major changes. I’m hoping now to have much more frequent releases. WARNING: to update, you need to call the db:updateTo34 command once the container is updated (or the new files are pulled).