Odoo Changelog — 2025-09-15

Monday, September 15, 2025

3 changes · 19.0

Refactoring(3)

Code cleanup and technical improvements

[FIX] *: tests - avoid imports to _framework

Core19.0google_address_autocompletehtml_editorim_livechatmailpoint_of_salepos_restaurantspreadsheetwebwebsite

This update reorganizes internal test code so shared web testing helpers are accessed through one central place. It should make future maintenance easier and reduce conflicts without changing day-to-day product behavior for users.

Original PR description

This commit reduces imports to the 'tests/_framework/' subfolder, which is meant to be accessed through the 'web_test_helpers' module as to reduce the amount of imports, as well as centralizing all web helpers to have a quick overview of the available helpers.

Enterprise: https://github.com/odoo/enterprise/pull/94074

Originally contained within the following pull request: https://github.com/odoo/odoo/pull/225744
But has been separated for convenience sake since the original PR was involving security overrides, and would be consistently interrupted by conflicts ensuing from this specific commit.

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

Forward-Port-Of: odoo/odoo#225974
Forward-Port-Of: odoo/odoo#225865

#tests#maintenance#web_helpers

[REF] mail_enterprise, *: clean discuss assets bundle [part 1]

PR #94493

Enterprise19.0aiai_livechatai_website_livechatapprovalsmail_enterprisevoipwebsite_helpdesk_livechatwhatsapp

This update reorganizes how several enterprise add-ons load their Discuss and live chat resources, removing an unused VoIP public asset bundle. The change is mainly internal maintenance, helping keep the product easier to maintain without introducing expected functional changes for users.

Original PR description

Enterprise counter-part.

https://github.com/odoo/odoo/pull/226643

#discuss#livechat#assets#maintenance

[REF] mail, *: clean discuss assets bundle

PR #226643

Core19.0cloud_storagecrm_livechathrhr_holidaysim_livechatmail

The Discuss-related asset setup has been reorganized so modules can add related changes in one clearer place instead of repeating them across several page bundles. This reduces maintenance effort and lowers the risk of inconsistent behavior when future messaging, live chat, or portal updates are made.

Original PR description

Currently, each module is responsible of adding discuss overrides into each of the top level bundle (backend, public page, livechat, portal). This means when adding one folder in a new module, it…

Currently, each module is responsible of adding discuss overrides into each of the top level bundle (backend, public page, livechat, portal). This means when adding one folder in a new module, it might need to be added into 4 different bundles.

This requires knowledge of the bundles and forgetting one of them might lead to unexpected behavior. The bundle name also does not match with the path of the file, which adds confusion.

This also doesn't give much granularity for where overrides are applied: they are always applied after all files of the dependent modules, but this might not always be desirable.

This commit refactors the discuss bundles so that one bundle = one path. The intent of the path was already correct (to match the top level bundle), which is unchanged. The only change is now having matching intermediate bundle names.

As an example: overrides of `core/web` in a module can directly be included in `mail.assets_core_web` (matching name, single line in manifest) rather than having to override each of the top-level bundle separately (backend, public page, livechat embed, portal) to add the new folder.

https://github.com/odoo/enterprise/pull/94493

This commit reduces imports to the 'tests/_framework/' subfolder, which is meant to be accessed through the 'web_test_helpers' module as to reduce the amount of imports, as well as centralizing all web helpers to have a quick overview of the available helpers. Enterprise: https://github.com/odoo/enterprise/pull/94074 Originally contained within the following pull request: https://github.com/odoo/odoo/pull/225744 But has been separated for convenience sake since the original PR was involving security overrides, and would be consistently interrupted by conflicts ensuing from this specific commit. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#225974 Forward-Port-Of: odoo/odoo#225865

Currently, each module is responsible of adding discuss overrides into each of the top level bundle (backend, public page, livechat, portal). This means when adding one folder in a new module, it might need to be added into 4 different bundles. This requires knowledge of the bundles and forgetting one of them might lead to unexpected behavior. The bundle name also does not match with the path of the file, which adds confusion. This also doesn't give much granularity for where overrides are applied: they are always applied after all files of the dependent modules, but this might not always be desirable. This commit refactors the discuss bundles so that one bundle = one path. The intent of the path was already correct (to match the top level bundle), which is unchanged. The only change is now having matching intermediate bundle names. As an example: overrides of `core/web` in a module can directly be included in `mail.assets_core_web` (matching name, single line in manifest) rather than having to override each of the top-level bundle separately (backend, public page, livechat embed, portal) to add the new folder. https://github.com/odoo/enterprise/pull/94493