Commit Graph

11 Commits

Author SHA1 Message Date
OCA-git-bot
90b65ef663 mass_mailing_partner 13.0.1.0.2 2022-01-01 16:22:48 +01:00
OCA-git-bot
2eca27cb57 mass_mailing_partner 13.0.1.0.1 2022-01-01 16:22:48 +01:00
Manuel Calero
7a5bc7090e [MIG] mass_mailing_partner: Migration to 13.0 2022-01-01 16:22:47 +01:00
Manuel Calero
eda99e3607 [IMP] mass_mailing_partner: black, isort 2022-01-01 16:22:47 +01:00
david
38ce378348 [FIX] mass_mailing_partner: prevent singleton error 2022-01-01 16:22:47 +01:00
Tonow-c2c
b313196ea2 [FIX][12.0][mass_mailing_partner] _check_email_mass_mailing_contacts loop not on self but partner 2022-01-01 16:22:47 +01:00
Sergio Teruel
8e47af7cbc [12.0][MIG] mass_mailing_partner: Migration to v12.0 2022-01-01 16:22:47 +01:00
ernesto
a5b869b487 [MIG] mass_mailing_partner: Migration to 11.0 2022-01-01 16:22:46 +01:00
David Vidal
a11a597edd [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
2022-01-01 16:22:46 +01:00
Jairo Llopis
646e0a8e00 [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.
2022-01-01 16:22:46 +01:00
David Vidal
89cfe6d1e9 [MIG] mass_mailing_partner: Migration to 10.0 2022-01-01 16:22:46 +01:00