v1.4.1

This patch release brings performance improvement and a configuration tweak.

• By refactoring the code for the /reports/ endpoint, they are loading much faster now. Moreover, there is a new query parameter include_help to indicate whether or not the help options should be returned as well. These two improvements combined will make the "Reports" page in Gramps Web much faster. Fixes #451.
• A new config option IGNORE_DB_LOCK is added. If true, an existing lock file in the Gramps database directory is ignored. Although Gramps Web doesn't write the lock file, an existing lock file can lead to issues. Since this is meant as a safeguard to not intefere with a running Gramps desktop instance on the same machine, the default remains false (so this is not a breaking change), but it is recommended to set it to true when deploying Gramps Web on a web server.

v1.4.0

New feature: text recognition (OCR)

The main new feature in this release is the addition of an endpoint for text recognition (OCR) from media files using Tesseract (via pytesseract)!

To use the feature, tesseract needs to be installed; it is already installed in the latest version of the default docker image. The endpoint, /api/media/{handle}/ocr, is documented in the API specification.

Other improvements

• The e-mail confirmation token (for a newly registered user to confirm their e-mail address) no longer expires, see #448
• The Docker base image has been updated from Debian 10 to Debian 12
• The Docker base image has been updated from Gramps 5.1.5 to Gramps 5.1.6

Bug fixes

• A missing translation was added (#452)

v1.3.2

This minor release fixes one issue and improves performance, in particular for large trees and when using PostgreSQL as database.

• Previously, accessing a note with a broken link (e.g. internal link to a non-existent object) would raise a server error. Now, the note is shown with an empty link instead (fixes #431)
• Sorting a list of Gramps objects or filtering by a date pattern was generating a larger number of database calls so far, which could lead to a drastic slowdown when loading Gramps Web in particular when using PostgreSQL as database and for large trees. Now, sorting and filtering is done in memory, which leads to a slightly larger memory footprint, but significantly faster processing 🚀 (fixes #433)

v1.3.1

This is a maintenenance release making two small improvements:

• Person profiles now contain the name suffix in an additional key, name_suffix, which was previously missing in the profile.
• The ancestor_handles and ancestor_profile of the DNA segment map endpoint introduced in v1.3.0 now no longer contain duplicate entries even if there are multiple connections to the same ancestor.

v1.3.0

DNA segment endpoint

This release adds a new endpoint to access chromsome segment data from DNA matches that are stored in the format used by the DNA segment map Gramplet.

Also, an issue with the media archive endpoint was fixed.

v1.2.1

While this is just a patch release, it brings significant performance improvements for Gramps Web users with "guest" permissions, as it speeds up access to Gramps' private proxy database.

In addition, an issue with editing source attributes, incorrect setting of the people usage, and a version conflict when using Python 3.7 (thanks @Samurai336) were fixed.

v1.2.0

This minor release introduces a few small API changes:

• The /api/metadata endpoint no longer returns the list of surnames by default. The previous behaviour can be restored with the query parameter surnames=1.
• The /api/transactions endpoint got a new optional query parameter force. If true, object updates or deletions are executed even if the object has been modified in the meantime.
• Missing media files no longer raise a server error (status code 500), but return status not found (404) now.

In addition, an issue affecting the media archive import (#412) was fixed.

v1.1.11

This release fixes an issue with images not showing up for users with role "guest" when using object storage for media files.

v1.1.10

This release fixes an issue with the Export endpoint.

v1.1.9

This release fixes an issue with the media archiv upload endpoint.