[18.0][MIG] mail_tracking: Migration to 18.0 #1476

* [ADD] mail_tracking addon * Add description icon * Fixes remarked * Fix Travis error * Remarks fixed

…ent events (OCA#82) [IMP] mail_tracking: Speed installation time, discard concurrent events and other fixes

* Improve tests * Show trackings even if partner removed * Disable CSRF protection to webhooks controllers

…s and contacts to bounce (OCA#133)

As regular users can't access this object.

* [FIX] Only one data-odoo-tracking-email tag in each email * [FIX] Get status even in multicompany instances

On our server, queries based on "mail_tracking_event"."tracking_email_id" improved from 501,924 ms to 1,840 ms queries based on "mail_tracking_email"."mail_message_id" improved from 167,436 ms to 3,223 ms The last ones are run several times when a thread has many messages

Currently translated at 100.0% (82 of 82 strings) Translation: social-11.0/social-11.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-11-0/social-11-0-mail_tracking/fr/

Closes OCA#303

For giving more priority to other buttons like the invoices one.

Currently translated at 96.3% (79 of 82 strings) Translation: social-11.0/social-11.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-11-0/social-11-0-mail_tracking/ca/

Or infinite recursions will happen on other `write` overwrites, like the one that happens on `mass_mailing_partner`.

…ng the creation of a new document.

Bad P2 > P3 conversion

Currently translated at 33.3% (29 of 87 strings) Translation: social-12.0/social-12.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-12-0/social-12-0-mail_tracking/es/

- Any model inheriting from mail.thread will have a filter available to obtain records with errors in their messages trackings. - The messages can be marked as done to avoid false positives when the issues are solved.

…iewed Previous this commit, failed messages widget data wasn't updated properly when you set as reviewed/retry the last message displayed. This commit resolve the problem and improves the "set as reviewed" action to avoid multi-user inconsistencies (don't toggle the value).

…' field Before this commit, some methods with views crashes trying to process 'failed_message_ids' field. After this commit the 'failed_message_ids' field description is properly generated.

The state will be 'opened' after first time email is opened. Each successive open triggered warning, because state was already 'opened' and thus did not match domain state in (sent, delivered). Forward-port #d9ad3464

…eck for this

When a user try to resend message gets an error stating that it's only allowed for users who belong to the Administration/Settings group

…y show confirmation if needed

Fix OCA#701, following idea from https://kb.mailwizz.com/articles/low-score-in-spamassassin-because-of-the-rand_mktg_header-rule/ to avoid matching the regexp explained in https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7888#c5 @Tecnativa TT29674

A filter_domain was added in the sender and recipient fields to be able to handle a more specific filter when using mail tracking.

This commits is using the field recipient_address in filter of search view of mail.tracking.email in order to use the same field used in computed method: https://github.com/OCA/social/blob/147eda96a56c199602c619b5bac3a9911605e918/mail_tracking/models/res_partner.py#L27

In migration OCA#873 the classes DiscussController and MailController which are the result of an upstream functionality split are merge altogether in this module override causing undesired side effects in other modules trying to extend those (i.e.: portal) TT41432

Mass mailing are tracked from mail.trace as the don't store a message in the db. In order to gather the message_id and be able to do manual checks to mailgun, that's the table where we should get the message id. TT40816

Up until now, the `sent` event type was never processed, probably because it "made no sense", as an unsent email would never trigger an event. However, it makes sense to process it because you may have a local relay that transmits mails over to the mail provider. In those circumstances, you should have 2 "sent" events (one from the relay and another one from the provider). Also marked some useless parts of code for removal. @Tecnativa TT32365

Refine which mail tracking record is allowed to see. We can rely on the ACLs of the related records so we minimize inconvenient message subject leaks. A regular user can read these mail.tracking.email records: - Those with a linked mail.message that the user can read - Those with a linked mail.mail that the user can read - Those with no message/mail link but a linked partner that the user can read. - Those with no linked records. TT31399

…estions

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: social-15.0/social-15.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-15-0/social-15-0-mail_tracking/

Currently translated at 29.8% (34 of 114 strings) Translation: social-15.0/social-15.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-15-0/social-15-0-mail_tracking/it/

This is to resolve the following issue: * OCA#1121

If a user tries to read a thread on a record and one message is from a partner on which he has no permissions, there will be an exception as this method tries to fetch info from such partner. TT43075

In the forward port of the permission check, a column was dropped from the tuple, but the following code wasn't adapted to the new tuple length. For clarity sake we also name the tuple unpacking into proper variables. TT43453

- As the tracker img in the body is currently also used to set the X-Odoo-MailTracking-ID mail header we can remove the tag only after this is done - Added tests to check for the presence and absence of the tracking image tag depending on the new configuration parameter

- Recover the failed messages box in the mail.thread - Fix failed message box template issues - Remove dead code - Fix send_email() method signature - Fix patch methods js files paths - Update roadmap TT44683

The following changes were implemented: 1 - Added Failed Message component and related components to reuse the Message component when rendering failed messages. This allows us to dispose of the messagefailed JS model altogether, since failed messages are now just regular messages that were marked as failed. 2 - Added Owl reactivity to failed message actions so that browser does not have to be reloaded each time a message is marked as reviewed or resent. 3 - Fixed 'Retry' and 'Set as reviewed' flows for failed messages. 4 - Fixed `Failed sent messages` filter on models by overriding `get_view` instead of `_fields_view_get` 5 - Refactored folder structure to more closely resemble the `mail` module's folder structure. 6 - Refactored module to utilize `Command` as a means to create, write, etc. instead of `[0, ...]`, `[4, ...]`. 7 - Fixed and added unit tests. 8 - Removed dead/unused code from `v15`.

Currently translated at 100.0% (125 of 125 strings) Translation: social-16.0/social-16.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-16-0/social-16-0-mail_tracking/es/

Currently translated at 27.2% (34 of 125 strings) Translation: social-16.0/social-16.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-16-0/social-16-0-mail_tracking/it/

Currently translated at 82.4% (103 of 125 strings) Translation: social-16.0/social-16.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-16-0/social-16-0-mail_tracking/pt_BR/

Currently translated at 29.8% (34 of 114 strings) Translation: social-15.0/social-15.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-15-0/social-15-0-mail_tracking/it/

Currently translated at 100.0% (125 of 125 strings) Translation: social-16.0/social-16.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-16-0/social-16-0-mail_tracking/fr/

TT49060

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: social-17.0/social-17.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-17-0/social-17-0-mail_tracking/

Currently translated at 100.0% (128 of 128 strings) Translation: social-17.0/social-17.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-17-0/social-17-0-mail_tracking/it/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: social-17.0/social-17.0-mail_tracking Translate-URL: https://translation.odoo-community.org/projects/social-17-0/social-17-0-mail_tracking/

Add autovacuum to mail_tracking_email that removes old records based on new configuration variable mail_tracking_email_max_age_days. Due to possibly a large number of records to be deleted on first run, set a default limit of 5000 per run.

Commits on Oct 17, 2024

[MIG] mail_tracking: Migration to 18.0

trisdoan committed Oct 17, 2024

Configuration menu

View commit details

Copy full SHA for 794a168

Browse repository at this point

Copy the full SHA

794a168 View commit details

Browse the repository at this point in the history

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[18.0][MIG] mail_tracking: Migration to 18.0 #1476

[18.0][MIG] mail_tracking: Migration to 18.0 #1476

Commits on Oct 10, 2024

Commits on Oct 17, 2024

[18.0][MIG] mail_tracking: Migration to 18.0 #1476

Are you sure you want to change the base?

[18.0][MIG] mail_tracking: Migration to 18.0 #1476

Commits on Oct 10, 2024

Commits on Oct 17, 2024