Thank you Roberto!  You are pushing out updates quickly!  Was then Cache 
Size addressed in this update?



On Tuesday, July 18, 2017 at 5:54:34 PM UTC-4, Roberto Rosario wrote:
>
> Mayan EDMS version 2.6 released, Docker image updated as well.
>
> Feature highlights:
>
> *Email*
>
>
>    - Support for emailing documents or document links to multiple 
>    recipients.
>    
>
>
> <https://lh3.googleusercontent.com/-oqCfNIZKeu8/WW6Cj9aY3oI/AAAAAAAA7g4/W9ACiDOYSrAdsS36A2Y5SmyYe3qe-4ClACLcBGAs/s1600/Selection_030.png>
>
>
>
> *Visual changes*
>
>
>    - Full width layout. 
>    
>
>
> <https://lh3.googleusercontent.com/-1idD55T4xp0/WW6CuCPwwqI/AAAAAAAA7g8/av-zWSy2vVYvh_65BeIjfv5MqepQH7c9ACLcBGAs/s1600/Selection_028.png>
>
>
>
>    - New list item view.
>    
>
>
> <https://lh3.googleusercontent.com/-19P4q2Rt49c/WW6Cywi5UzI/AAAAAAAA7hA/NzhsSrmUq584Z1cpzouGqfq39w5EuH_jwCLcBGAs/s1600/Selection_029.png>
>
>
> *Search*
>
>
>    - Support for searching users and groups via the API. 
>    
>
> *Logging*
>
>
>    - 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.
>    
>
> *Cabinets*
>
>
>    - 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.
>    
>
> *New permission*
>
>
>    - 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.
>    
>
> *ACL changes*
>
>
>    - 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.
>    
>
> *Testing*
>
>
>    - 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.
>    
>
> *Other Changes*
>
>
>    - Fix HTML mark up in window title. GitLab #397.
>    - Sort setting by namespace label and by global name second.
>    - Sort indexes by label.
>    - Switch the order of the DEFAULT_AUTHENTICATION_CLASSES of DRF. 
>    GitLab #400.
>    - Improve code to unbind menu entries.
>    - Increase the size of the mailing profile label field to 128 
>    characters.
>
>
> For the complete list of changes and a full explanation of the changes 
> mentioned
> above, visit the release notes: 
> http://mayan.readthedocs.io/en/v2.6/releases/2.6.html
>
> Many of the features added in this release were requested by support 
> subscribers.
> Prioritized feature requests, another benefit of the support plans: 
> http://www.mayan-edms.com/providers/
>
> Docker image README https://hub.docker.com/r/mayanedms/mayanedms/
>
> Facebook page: https://www.facebook.com/MayanEDMS/
> Mayan App store: http://www.mayan-edms.com/store/
>

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to