Commit Graph

19 Commits (bac73d64ae91a33151b1f1aef5e8e397bef19ed1)

Author SHA1 Message Date
Minh Chien d1e1e29afe [MIG] mass_mailing_partner: Migration to 16.0 2023-03-24 15:12:25 +01:00
emagdalenaC2i f565e1078b [MIG] mass_mailing_partner: Migration to 15.0 2023-03-24 15:09:08 +01:00
david 30c28d4773 [FIX] mass_mailing_partner: wrong company implementation
See issue https://github.com/OCA/social/issues/776
2023-03-24 15:09:08 +01:00
Areeb Siddiqi 1196f3ad8c [MIG] mass_mailing_partner: Migration to 14.0
[FIX] super(Class, self) changed to super() in mass_mailing_partners
2023-03-24 15:09:08 +01:00
Areeb Siddiqi a1235e0e7b [IMP] mass_mailing_partner: black, isort, prettier 2023-03-24 15:09:08 +01:00
Alexandre D. Díaz b9850efe53 [FIX] mass_mailing_partner: Use correct button class
Before this commit, the buttons are displayed incorrectly in mobile dropdown buttons menu
2023-03-24 15:09:08 +01:00
Víctor Martínez 473a80be1a [IMP+FIX] mass_mailing_partner: Add partner_name in error constrain message + Add test related to write with multi-partner + Add sudo() to prevent user without mailing access try to merge contacts 2023-03-24 15:08:55 +01:00
Pedro M. Baeza 0f8777d45f [FIX] mass_mailing_partner: Don't match partner if no email
It doesn't make sense and even more, it crashed.

Fixes #644
2023-03-24 15:08:18 +01:00
Víctor Martínez a6b5558ea4 [FIX] mass_mailing_partner: Fix partner merge error (dupplicate mass_mailing contacts) 2023-03-24 15:08:18 +01:00
Jared Kipe 8268a8129d [FIX] mass_mailing_partner: Unsubscribe should not unlink the subscription.
Before, on the backend if you check the `opt_out` checkbox and saving on a `mailing.contact`, the entire row (`mailing.contact.subscription`) would be unlinked.  Combined with `mass_mailing_list_dynamic` this means the contact would just be re-subscribed over and over.

After, check `opt_out` will fill `unsubscription_date` and the row will stay.  Tests in `mass_mailing_list_dynamic` pass.
2023-03-24 15:08:18 +01:00
Manuel Calero 0b8f382614 [MIG] mass_mailing_partner: Migration to 13.0 2023-03-24 15:08:18 +01:00
Manuel Calero e4f5befac3 [IMP] mass_mailing_partner: black, isort 2023-03-24 15:04:56 +01:00
david 81e511df05 [FIX] mass_mailing_partner: prevent singleton error 2023-03-24 15:04:56 +01:00
Tonow-c2c c0080d59eb [FIX][12.0][mass_mailing_partner] _check_email_mass_mailing_contacts loop not on self but partner 2023-03-24 15:04:56 +01:00
Sergio Teruel f43148663e [12.0][MIG] mass_mailing_partner: Migration to v12.0 2023-03-24 15:04:56 +01:00
ernesto 938ae11587 [MIG] mass_mailing_partner: Migration to 11.0 2023-03-24 15:04:56 +01:00
David Vidal c4ab0a0222 [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
2023-03-24 15:04:56 +01:00
Jairo Llopis 1aaff0c4e2 [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.
2023-03-24 15:04:56 +01:00
David Vidal 7821cbc726 [MIG] mass_mailing_partner: Migration to 10.0 2023-03-24 15:04:56 +01:00