Commit Graph

9 Commits (a8c7627a0db16f3b95030dc14c0cadc8399da36a)

Author SHA1 Message Date
Manuel Calero 65b1a9a92a [MIG] mass_mailing_partner: Migration to 13.0 2020-02-10 11:49:12 +01:00
Manuel Calero d7ccc735c6 [IMP] mass_mailing_partner: black, isort 2020-02-10 11:35:23 +01:00
david db0195ad71 [FIX] mass_mailing_partner: prevent singleton error 2020-02-10 11:32:23 +01:00
Tonow-c2c 505d7830a9 [FIX][12.0][mass_mailing_partner] _check_email_mass_mailing_contacts loop not on self but partner 2020-02-10 11:32:23 +01:00
Sergio Teruel d1237ae13c [12.0][MIG] mass_mailing_partner: Migration to v12.0 2020-02-10 11:20:03 +01:00
ernesto c3993506cd [MIG] mass_mailing_partner: Migration to 11.0 2020-02-10 11:20:03 +01:00
David Vidal 1da60acca8 [FIX] mass_mailing_partner: compute fields performance (#271)
- In DB which use large amounts of records and intesive use of
mass_mailings, not optimized compute records lead to a drastical
decrease of performance
2020-02-10 11:20:03 +01:00
Jairo Llopis 436f18a737 [FIX] mass_mailing_partner: Allow unprivileged users to edit partners
Without this patch, users without access to reading and editing mass mailing contact records are now unable to change a partner's name or email. They'd recieve an exception such as:

    AccessError: Sorry, you are not allowed to access this document. Only users with the following access level are currently allowed to do that:
    - Mass Mailing/User

    (Document model: mail.mass_mailing.contact)

Restrictive ACLs shouldn't restrict normal user operation nor DB consistency, so using sudo mode now and testing behavior.
2020-02-10 11:20:03 +01:00
David Vidal fd69f41a49 [MIG] mass_mailing_partner: Migration to 10.0 2020-02-10 11:20:03 +01:00