Odoo Changelog — 2025-03-21

Friday, March 21, 2025

2 changes · saas-18.2

Bug Fixes(2)

Resolved issues and error corrections

[REF] mail: be more defensive in default or suggested recipients

PR #202472

Coresaas-18.2accounthr_recruitmentmailmicrosoft_calendartest_mailwebsite_event_boothMedium

Odoo now avoids suggesting internal alias, bounce, catchall, and similar system email addresses as recipients or followers. This reduces accidental emails to technical mailboxes and improves the relevance of reply-all suggestions across chatter, accounting, recruitment, calendar, and event flows.

Original PR description

Rationale

Now that more emails and partners are suggested in chatter flow since
https://github.com/odoo/odoo/pull/185240 it highlights issue notably with aliases or alias
domains specific emails. We should ensure those are never proposed,
either as email or as partners.

Specifications: defensive email / partner fetch

Consider all emails coming from alias domains (catchall, bounce, default
from) are like aliases and should not be suggested.

Filter suggested partners whose emails match aliases or alias domain
emails.

Specifications: filter discussion message when replying to all

Filter before sorting, in order to keep only relevant messages. Also
add missing filter on subtype, which should be 'comment' or creation
subtype for incoming emails.

Indeed logged notes, even with pings, should not be considered as a
reply-all as purpose is to include customers and external people
involved in emails and discussions.

Then sort only based on date, considering most recent message is the
most important. No need to sort based on email or discussion as
date is the only relevant criterion.

Specifications: be sure addons use dedicated mail tools

Avoid aliases and alias domains emails added as follower or recipients
by using the correct tools.

Links

Followup of odoo/odoo#185240
Followup of odoo/odoo#198173
Followup of odoo/odoo#198095

Task-4656218

#email#recipients#chatter#aliases

[FIX] website: display video iframes

PR #202361

Coresaas-18.2websiteMedium

This fix restores proper display of embedded videos on website pages when the video iframe needs to be generated. It prevents missing or broken video embeds by checking for the iframe safely and using the correct stored video source information.

Original PR description

Since the function `generateIframe` can return nothing, we need to check that there is an iframe before checking the attributes on it.

When we need to generate an iframe, we need to check the attribute `data-oe-expression` instead of `oe-expression` otherwise it won't find the source and won't generate an iframe.

The element we need to give to the function `manageIframeSrc` is the iframe itself and not the parent.

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#website#video#iframe#embed

Rationale Now that more emails and partners are suggested in chatter flow since https://github.com/odoo/odoo/pull/185240 it highlights issue notably with aliases or alias domains specific emails. We should ensure those are never proposed, either as email or as partners. Specifications: defensive email / partner fetch Consider all emails coming from alias domains (catchall, bounce, default from) are like aliases and should not be suggested. Filter suggested partners whose emails match aliases or alias domain emails. Specifications: filter discussion message when replying to all Filter before sorting, in order to keep only relevant messages. Also add missing filter on subtype, which should be 'comment' or creation subtype for incoming emails. Indeed logged notes, even with pings, should not be considered as a reply-all as purpose is to include customers and external people involved in emails and discussions. Then sort only based on date, considering most recent message is the most important. No need to sort based on email or discussion as date is the only relevant criterion. Specifications: be sure addons use dedicated mail tools Avoid aliases and alias domains emails added as follower or recipients by using the correct tools. Links Followup of odoo/odoo#185240 Followup of odoo/odoo#198173 Followup of odoo/odoo#198095 Task-4656218

Since the function `generateIframe` can return nothing, we need to check that there is an iframe before checking the attributes on it. When we need to generate an iframe, we need to check the attribute `data-oe-expression` instead of `oe-expression` otherwise it won't find the source and won't generate an iframe. The element we need to give to the function `manageIframeSrc` is the iframe itself and not the parent. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr