Skip to content

[18.0][FIX] mail_composer_cc_bcc: keep the "View <record>" button for internal user recipients - #265

Open
qgroulard wants to merge 1 commit into
OCA:18.0from
acsone:18.0-fix-mail_composer_cc_bcc_message_type-qgr
Open

[18.0][FIX] mail_composer_cc_bcc: keep the "View <record>" button for internal user recipients#265
qgroulard wants to merge 1 commit into
OCA:18.0from
acsone:18.0-fix-mail_composer_cc_bcc_message_type-qgr

Conversation

@qgroulard

@qgroulard qgroulard commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Solves #264

Every recipient added through the composer (original recipients, plus the cc/bcc partners) was unconditionally classified as "customer".

A side effect: the "View " button Odoo normally shows to internal user recipients was hidden for everyone, since that button is tied to the "user" notification group, which was never allowed to survive.

Let partners keep their real usage ("user", "portal" or "customer") Internal users now get their own notification email with the button, while external recipients still share a single button-less email. Thus we now have two mail.mail (one for users, and one for the others) sharing the same mail.message.
The To/Cc/Bcc headers stay identical on both, regardless of which notification group produced the mail.mail.

@OCA-git-bot

Copy link
Copy Markdown
Contributor

Hi @trisdoan,
some modules you are maintaining are being modified, check this out!

@OCA-git-bot OCA-git-bot added series:18.0 mod:mail_composer_cc_bcc Module mail_composer_cc_bcc labels Sep 10, 2026
…nal user recipients

Every recipient added through the composer (original recipients, plus
the cc/bcc partners) was unconditionally classified as "customer".

A side effect: the "View <record>" button Odoo normally shows to
internal user recipients was hidden for everyone, since that button is
tied to the "user" notification group, which was never allowed to
survive.

Let partners keep their real usage ("user", "portal" or "customer")
Internal users now get their own notification email with the button,
while external recipients still share a single button-less email.
Thus we now have two mail.mail (one for users, and one for the others)
sharing the same mail.message.
The To/Cc/Bcc headers stay identical on both, regardless of which
notification group produced the mail.mail.
@qgroulard
qgroulard force-pushed the 18.0-fix-mail_composer_cc_bcc_message_type-qgr branch from 0a4d80b to f182ce3 Compare September 10, 2026 11:54
@qgroulard

Copy link
Copy Markdown
Contributor Author

Hi @trisdoan,
Over the course of the last month I have proposed a series of fixes for the module mail_composer_cc_bcc that you are maintaining. Could you please have a look at them (#255 and #256) ?

I didn't expect that the installation of this module on my instance would lead to that many bugs. I think they are pretty serious side-effects that deserve to be reviewed quickly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:mail_composer_cc_bcc Module mail_composer_cc_bcc series:18.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants