Skip to content

2024

3.1 Release

The most important part of release 3.1 are the the support of OpenLDAP and OAuth2 (Google and Github providers) authetication.

Adds

  • Support of OAuth2 authentication with Google and GitHub providers
  • Support for OpenLDAP (RFC 4510) authentication
  • Support for node's custom IDs Issue#325
  • Exclude document from OCR Issue#598

Fixes

  • Getting '500 - Internal Server Error' when patching node tags Issue#326
  • papermerge-cli import option --delete without any function Issue#592

The documentation for authentication part is here.

3.0.3 Release

Release 3.0.3 is a minor release which contains mostly bug fixes:

Fixes

  • Logging out doesn't bring up log in dialogue Issue#574
  • Ship spa, ita, fra, ron and por OCR languages data in docker image Issue#586
  • Fix create_token.sh throws an error Issue#314
  • Empty Folder on Second Page Issue#584
  • Include Dutch language OCR data in default docker image
  • Add Gujrati, Hindi and Sanskrit language codes Issue#583

Adds

  • [UI] Context Missing "Extract Pages" entry Issue#564

3.0.2 Release

Release 3.0.2 is a minor release which contains only bug fixes:

  • Fix create_user to work with MySql/MariaDB/sqlite3 Issue#579
  • Fix Error / Internal Server Error Issue#581
  • Fix Error thrown after successful login Issue#307
  • Fix wrong download URL for document version in viewer
  • Fix nodes pagination (num_pages int rounded up instead of down)

Papermerge 3.0.1 Release

I am happy to announce the release of version 3.0.1.

Among other things, this release fixes major issue related to DB connections. Let me provide short description of the problem. The access to specific REST API endpoints was leaving DB connection open. The problem is that open DB connection were accumulating up to the point (which depends on specific DB configuration) when DB was refusing to accept more DB connections, which resulted of course to the whole app going offline.

The root course of the problem is Django ORM and the way it handles DB connections. To mitigate the issue, we've decided start moving away from Django ORM to SQLAlchemy. Of course full transition to new ORM will span many releases, but the main point here is that for end users this transition is fully opaque.