Commit Graph

20 Commits (2ad83c5cb2dce73ca63a1ea7b0828c2bc3e15fcb)

Author SHA1 Message Date
Mohamed Osman 005260d030 [MIG] mass_mailing_partner: Migration to 17.0 2024-03-27 16:18:43 +00:00
Minh Chien 0407c7cc82 [MIG] mass_mailing_partner: Migration to 16.0 2024-03-27 16:18:43 +00:00
emagdalenaC2i 9cc4512320 [MIG] mass_mailing_partner: Migration to 15.0 2024-03-27 16:18:43 +00:00
david 0b62ef8fad [FIX] mass_mailing_partner: wrong company implementation
See issue https://github.com/OCA/social/issues/776
2024-03-27 16:18:43 +00:00
Areeb Siddiqi 23ee44861d [MIG] mass_mailing_partner: Migration to 14.0
[FIX] super(Class, self) changed to super() in mass_mailing_partners
2024-03-27 16:18:43 +00:00
Areeb Siddiqi 2009ce45a5 [IMP] mass_mailing_partner: black, isort, prettier 2024-03-27 16:18:43 +00:00
Alexandre D. Díaz a8c9914ced [FIX] mass_mailing_partner: Use correct button class
Before this commit, the buttons are displayed incorrectly in mobile dropdown buttons menu
2024-03-27 16:18:43 +00:00
Víctor Martínez 0ad5deb7ee [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 2024-03-27 16:18:43 +00:00
Pedro M. Baeza 157ee5d0de [FIX] mass_mailing_partner: Don't match partner if no email
It doesn't make sense and even more, it crashed.

Fixes #644
2024-03-27 16:18:43 +00:00
Víctor Martínez db5c37726e [FIX] mass_mailing_partner: Fix partner merge error (dupplicate mass_mailing contacts) 2024-03-27 16:18:43 +00:00
Jared Kipe 60b079cc6c [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.
2024-03-27 16:18:43 +00:00
Manuel Calero 434e10fbe5 [MIG] mass_mailing_partner: Migration to 13.0 2024-03-27 16:18:43 +00:00
Manuel Calero 9ab0f87b50 [IMP] mass_mailing_partner: black, isort 2024-03-27 16:18:43 +00:00
david 49cb0e39f9 [FIX] mass_mailing_partner: prevent singleton error 2024-03-27 16:18:43 +00:00
Tonow-c2c c3e75f7f24 [FIX][12.0][mass_mailing_partner] _check_email_mass_mailing_contacts loop not on self but partner 2024-03-27 16:18:43 +00:00
Sergio Teruel 1303fbe895 [12.0][MIG] mass_mailing_partner: Migration to v12.0 2024-03-27 16:18:43 +00:00
ernesto 1754ee19f2 [MIG] mass_mailing_partner: Migration to 11.0 2024-03-27 16:18:43 +00:00
David Vidal d13815b808 [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
2024-03-27 16:18:43 +00:00
Jairo Llopis 5e74507d89 [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.
2024-03-27 16:18:43 +00:00
David Vidal 6953201f2a [MIG] mass_mailing_partner: Migration to 10.0 2024-03-27 16:18:43 +00:00