Version 3.2.11

Post Reply
User avatar
rosarior
Posts: 457
Joined: Tue Aug 21, 2018 3:28 am

Version 3.2.11

Post by rosarior » Thu Nov 28, 2019 5:59 pm

Released: November 28, 2019

Checkouts

An issue with the request introspection of the API endpoint for checking in documents was causing server internal error (HTTP 500 error) has been fixed.
Database integrity

Database transaction improvements from the version 3.3 branch were backported. Document events now trigger inside the same database transaction as document changes. This change will ensure the expected behavior of other elements that rely on this event even under the most heavy system loads and severe database/network infrastructure problems.

Documentation

The example LDAP file was improved. This is a community contributed file and not officially supported. For LDAP integration be sure to check and select one of the official support and/or consultation alternatives (https://www.mayan-edms.com/support/).

The LDAP entry of the FAQ was expanded with user feedback.

All the requirements to build the documentation are now generated automatically using Mayan’s internal dependency system.

The documentation now provides a sitemap to help in indexing and searching for information.

A missing detail of the API integration example to upload new documents has been added.

The update instructions to upgrade the supervisord configuration file were improve to work around some Linux shell differences. This makes the instructions work for more users.

Permissions

The index create permission was removed as a possible permission to grant for existing indexes, as this is semantically incorrect.

An issue with reverse inheritance permission detection was fixed. It is now possible to grant document permissions via the document type under all situations and deployment types.

Statistics

In some situations where improper horizontal scaling is used, the statistics result model could end up with duplicate slug field entries. This field is meant to be unique. Although this is a external issue, the situation is now prevented by making the field unique at the database level, adding a data migration to fix existing installations experiencing this issue, and by adding code that will detect and self-heal future occurrences of this.

Other changes

The file patching code from the Dependency class to a generalized utility of the storages app. This code is now used in several places including the documentation global variable substitution.

Removals

None

Docker image available at: https://hub.docker.com/r/mayanedms/mayanedms

Python packages available at: https://pypi.org/project/mayan-edms/3.2.11/ and installable via:

Code: Select all

pip install mayan-edms==3.2.11
Release notes: https://docs.mayan-edms.com/releases/3.2.11.html

Post Reply