Odoo Changelog — 2025-09-12

Friday, September 12, 2025

4 changes · 19.0

Refactoring(4)

Code cleanup and technical improvements

[REF] html_builder, *: update `assets_edit_frontend` bundle name

Core19.0html_buildermass_mailingportalwebsitewebsite_mailwebsite_mail_groupwebsite_mass_mailingwebsite_paymentwebsite_profilewebsite_sale

The technical asset bundle used by the website and email builders was renamed to better reflect that it now supports more than website editing. This is an internal cleanup that makes the platform easier to maintain without changing business workflows.

Original PR description

*: mass_mailing, portal, website, website_mail, website_mail_group, website_mass_mailing, website_payment, website_profile, website_sale

The new html_builder is used by both website and mass_mailing. While the old name `[html_builder|website].assets_edit_frontend` makes sense in the context of the website builder, where the iframe is indeed used to "edit the frontend", it is not the case in mass_mailing, where the email being composed is not a "frontend". A more generic name is more appropriate.

#assets#website#email-builder#maintenance

[REF] web_tour: lazy load hoot-dom in tours

PR #224571

Core19.0barcodespos_restaurantweb_tour

The web tour testing tools now load a supporting component only when a tour starts, instead of including it upfront. This reduces the size of the web tour assets, helping limit unnecessary load for users and improving overall efficiency.

#performance#asset-size#web-tours

[REF] ai_website_livechat: update `assets_edit_frontend` bundle name

PR #94435

Enterprise19.0ai_website_livechat

This update renames an internal asset bundle used by the AI website live chat feature so it better fits shared use beyond website editing. The change supports broader reuse with the newer builder tools while keeping business impact minimal.

Original PR description

The new html_builder is used by both website and mass_mailing. While the old name `[html_builder|website].assets_edit_frontend` makes sense in the context of the website builder, where the iframe is indeed used to "edit the frontend", it is not the case in mass_mailing, where the email being composed is not a "frontend". A more generic name is more appropriate.

This commit is linked to the community PR that updates the bundle name everywhere.

#livechat#website#builder#asset-naming

[REF] mrp_workorder, stock_barcode: add tour_helpers in manifest

PR #94150

Enterprise19.0mrp_workorderstock_barcode

This update registers supporting tour helper files for the Manufacturing Work Orders and Barcode apps. It is an internal maintenance change that helps automated guided flows and tests load the right resources, with no expected direct impact on day-to-day users.

Original PR description

In this commit, we add tour_helpers file in manifest.

#maintenance#testing#guided flows

*: mass_mailing, portal, website, website_mail, website_mail_group, website_mass_mailing, website_payment, website_profile, website_sale The new html_builder is used by both website and mass_mailing. While the old name `[html_builder|website].assets_edit_frontend` makes sense in the context of the website builder, where the iframe is indeed used to "edit the frontend", it is not the case in mass_mailing, where the email being composed is not a "frontend". A more generic name is more appropriate.

The new html_builder is used by both website and mass_mailing. While the old name `[html_builder|website].assets_edit_frontend` makes sense in the context of the website builder, where the iframe is indeed used to "edit the frontend", it is not the case in mass_mailing, where the email being composed is not a "frontend". A more generic name is more appropriate. This commit is linked to the community PR that updates the bundle name everywhere.