Skip to content

Releases: gramps-project/gramps-web-api

v1.1.9

02 Aug 20:25
Compare
Choose a tag to compare

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

v1.1.8

27 Jul 09:05
0188c19
Compare
Choose a tag to compare

This release fixes an issue with report generation and XML export in cases where the Gramps database default person is deleted in a Gramps desktop synchronization.

v1.1.7

21 Jul 19:01
Compare
Choose a tag to compare

This maintenance release improves the file and media import endpoints by not loading the entire file into memory before writing it to disk.

v1.1.6

20 Jul 18:57
Compare
Choose a tag to compare
Version -> 1.1.6

v1.1.5

18 Jul 20:16
Compare
Choose a tag to compare

The purpose of this release is to update the default docker image after fixing an issue in the SharedPostgreSQL Gramps addon.

v1.1.4

18 Jul 10:12
Compare
Choose a tag to compare
Version -> 1.1.4

v1.1.3

18 Jul 09:37
Compare
Choose a tag to compare
Version -> 1.1.3

v1.1.2

16 Jul 18:33
Compare
Choose a tag to compare

This release fixes a minor issue with the tree owner creation endpoint in multi-tree setup. It also improves logging when using gunicorn as server, as flask logging statements are now correctly forwarded.

v1.1.1

13 Jul 08:44
Compare
Choose a tag to compare

This release fixes two small issues: the people quota not being updated in all cases and a data type mismatch for a configuration parameter relevant in a multi-tree setup.

v1.1.0

09 Jul 14:22
e0ac575
Compare
Choose a tag to compare

This release contains one new feature and improved error handling

New feature: media archive upload

Continuing to improve the ways to get data in and out of Gramps Web, this release contains a new endpoint /media/archive/upload/zip that allows uploading a ZIP archive of media files that already have existing media objects in the database. This is a typical case that will happen after importing a Gramps XML of an existing tree (but without media).

More verbose errors

So far, most errors only returned an appropriate HTTP status code, but no message. Now, almost all errors return a JSON payload of the form {"error":{"code":<code>,"message":<message>}, which hopefully improves debugging and allows providing more meaningful error messages in user applications.