Odoo Changelog — 2025-11-12

Wednesday, November 12, 2025

2 changes · master

Refactoring(2)

Code cleanup and technical improvements

[REF] *: cleanup ControlPanel buttons management

Enterprisemasteraccount_accountantaccount_reportsappointmentcrm_enterprisedocumentsequityhr_payrollknowledgel10n_ke_edi_oscu_posmrp_mpsmrp_workorderproject_enterprisequality_control_worksheetsignweb_cohortweb_ganttweb_gridweb_mapweb_studio

This update reorganizes how main action buttons are defined and displayed across many Odoo views, making future customizations more consistent and easier to maintain. It should have little direct impact on day-to-day users, but helps reduce complexity for teams maintaining or extending these screens.

Original PR description

tl;dr : if you want to customize view's buttons, look for `buttonTemplate`. Following last years development (MILK redesign, ControlPanel buttons structure and cleanup, responsiveness...), the…

tl;dr : if you want to customize view's buttons, look for
`buttonTemplate`.

Following last years development (MILK redesign, ControlPanel buttons
structure and cleanup, responsiveness...), the ControlPanel's slots
related to the main buttons (i.e. left part of the ControlPanel) became
redundant. Also, extending the views' buttons with custom JS ones (i.e.
not in the arch) wasn't the clearer to understand.

This commit's purpose is to both clean up and clarify how to manage
those buttons.

In a nutshell, the `control-panel-create-button`,
`control-panel-always-buttons` and `layout-buttons` slots have been
merged into a single `control-panel-buttons` slot. It makes it easier to
know where main buttons (in general) will go in the ControlPanel.

For the views, the goal was also to make it clearer how to extend/modify
the view's main buttons. The main customization point is the
`buttonTemplate` view's property as it allows to override the view's
buttons. Beside very specific case, the `control-panel-buttons`
shouldn't be touched for this purpose.

The Form view has its own specificity: it explicitly handles the buttons
used in dialog (also via the arch's `<footer>`) and in the ControlPanel.
To take this difference into account, a dedicated `buttonDialogTemplate`
property has been introduced for this view, allowing the same kind of
extension as the `buttonTemplate`.

Note: to match the global ControlPanel slots' naming scheme,
`layout-actions` has been renamed to `control-panel-actions`.

task-4277543

#control panel#buttons#views#cleanup

[REF] whatsapp: adapt channel_member_list patch

PR #99267

Enterprisemasterwhatsapp

The WhatsApp integration was adjusted to stay aligned with recent discussion channel changes. This is an internal cleanup that helps keep member lists working consistently without changing the user experience.

Original PR description

This commit adapt channel_member_list_patch to use the channel props instead of thread.

PR: https://github.com/odoo/odoo/pull/235287

#whatsapp#channel members#maintenance

tl;dr : if you want to customize view's buttons, look for `buttonTemplate`. Following last years development (MILK redesign, ControlPanel buttons structure and cleanup, responsiveness...), the ControlPanel's slots related to the main buttons (i.e. left part of the ControlPanel) became redundant. Also, extending the views' buttons with custom JS ones (i.e. not in the arch) wasn't the clearer to understand. This commit's purpose is to both clean up and clarify how to manage those buttons. In a nutshell, the `control-panel-create-button`, `control-panel-always-buttons` and `layout-buttons` slots have been merged into a single `control-panel-buttons` slot. It makes it easier to know where main buttons (in general) will go in the ControlPanel. For the views, the goal was also to make it clearer how to extend/modify the view's main buttons. The main customization point is the `buttonTemplate` view's property as it allows to override the view's buttons. Beside very specific case, the `control-panel-buttons` shouldn't be touched for this purpose. The Form view has its own specificity: it explicitly handles the buttons used in dialog (also via the arch's `<footer>`) and in the ControlPanel. To take this difference into account, a dedicated `buttonDialogTemplate` property has been introduced for this view, allowing the same kind of extension as the `buttonTemplate`. Note: to match the global ControlPanel slots' naming scheme, `layout-actions` has been renamed to `control-panel-actions`. task-4277543