Odoo Changelog — 2023-09-29

Friday, September 29, 2023

3 changes · master

Bug Fixes(3)

Resolved issues and error corrections

[FIX] web_studio: element creation for insertion

Enterprisemasterweb_studio

This fixes a problem in Odoo Studio where adding content in the report editor could fail when the editor is embedded in a separate frame. Users should now be able to insert elements more reliably while editing reports, avoiding interruptions in report customization.

Original PR description

When the OdooEditor is mounted in an iframe, creating an element using the top document's `createElement` method produces a different result than creating one with the Editor's document. While the former is an instance of the top document's global `Node`, the latter is not (it is an instance of the iframe's global `Node` instead).

This commit fixes an undesired failed comparison using the `instanceof` operator in the editor's "insert" command, due to not using the Editor's document when creating a new element for insertion.

task-3521152

CE fw-port PR: https://github.com/odoo/odoo/pull/136597

#report editor#Odoo Studio#editing

[FIX] *: remove invalid groups on field

PR #47822

Enterprisemasteraccount_bacswhatsapp

This change corrects how certain fields are hidden or shown so they no longer conflict with newer validation checks. It helps prevent errors when filtering records in the BACS payment and WhatsApp account areas, without changing business workflows.

Original PR description

Because now (see https://github.com/odoo/odoo/pull/135111), we check
the field security groups used by a search domain.

The `groups='base.group_multi_company'` on the `allowed_company_ids`
field definition is for display only (hide the field if not needed).
And then it doesn't make sense to be set on the field itself that
enables group field security. Same for `groups='base.group_no_one'`
on the `bacs_submission_serial`.

#field visibility#validation#payments#whatsapp

[FIX] whatsapp_pos: receipt template field is not showing in setting

PR #48053

Enterprisemasterwhatsapp_pos

The POS settings now show the Receipt Template field when WhatsApp is enabled. This ensures businesses can select the required template needed to send receipts through WhatsApp.

Original PR description

Before this commit:
Navigate to POS settings -> Enable WhatsApp -> Receipt Template. There is currently no way to select the template.

After this commit:
If the "WhatsApp enabled" option is selected, the Receipt Template field will be displayed and a Receipt Template is required.

Task - 3508578

#whatsapp#pos#settings#receipts

When the OdooEditor is mounted in an iframe, creating an element using the top document's `createElement` method produces a different result than creating one with the Editor's document. While the former is an instance of the top document's global `Node`, the latter is not (it is an instance of the iframe's global `Node` instead). This commit fixes an undesired failed comparison using the `instanceof` operator in the editor's "insert" command, due to not using the Editor's document when creating a new element for insertion. task-3521152 CE fw-port PR: https://github.com/odoo/odoo/pull/136597

Because now (see https://github.com/odoo/odoo/pull/135111), we check the field security groups used by a search domain. The `groups='base.group_multi_company'` on the `allowed_company_ids` field definition is for display only (hide the field if not needed). And then it doesn't make sense to be set on the field itself that enables group field security. Same for `groups='base.group_no_one'` on the `bacs_submission_serial`.

Before this commit: Navigate to POS settings -> Enable WhatsApp -> Receipt Template. There is currently no way to select the template. After this commit: If the "WhatsApp enabled" option is selected, the Receipt Template field will be displayed and a Receipt Template is required. Task - 3508578