Released: July 18, 2017
Support was added to send a document as an attachment, or a link to a document to multiple email recipients. To use this feature enter a comman separated list of email recipients in the "Email address" field.
This release adds users and groups to the list of objects that are searchable via the API. The current list of searchable objects is: metadata types, users, groups, tags, documents, document pages, and cabinets.
The logging configuration was improved to create a log for critical errors when running on production mode. The default location for this log file is: /mayan/error.log. This path can be changed with the COMMON_PRODUCTION_ERROR_LOG_PATH setting. This log file will capture application errors and request exceptions.
The access control for cabinets has been fixed in some regards and improved in others. The permission to add and remove documents can now be applied to individual root cabinets instead of globally for a role. Also, the permission to add or remove documents from cabinets must also now be granted to a document or document type. In other words, to add a document to a cabinet, the user's role must have the permission to add documents to cabinet, for the cabinet to recieve the document and for the document about to be added.
The patch to add a permission to view a document's version list was backported from the development branch to make it accesible now. Like cabinets, the tag access control now works on two levels. Now to attach a tag to a document, the permission to attach tags must be granted to the tag to attach and to the document that will receive the tag.
The document type permissions namespace was renamed from "Document setup" to "Document types" for clarity. Along with that change, support was added for granting the document type edit, document type delete, and document type view permissions to individual document type instances instead of just globally.
The documents app view tests now test for view access and not just permission. Testing against access is more robust and also tests for permissions implicitly.
Type in the console:
$ pip install -U mayan-edms
the requirements will also be updated automatically.
If you installed Mayan EDMS by cloning the Git repository issue the commands:
$ git reset --hard HEAD $ git pull
otherwise download the compressed archived and uncompress it overriding the existing installation.
Next upgrade/add the new requirements:
$ pip install --upgrade -r requirements.txt
Migrate existing database schema with:
$ mayan-edms.py performupgrade
Add new static media:
$ mayan-edms.py collectstatic --noinput
The upgrade procedure is now complete.