Thursday, July 2, 2026
4 changes · 18.0
Resolved issues and error corrections
The preview of the 2FA login email now opens correctly in Settings instead of failing with a rendering error. This keeps the security safeguard in place while avoiding a traceback when users or administrators preview the template.
Original PR description
**Steps to reproduce:** - Install auth_totp_mail_enforce module - Go to Settings in debug mode - Go to Technical > Email Templates - Find `Settings: 2Fa New Login` template - Click on preview - Error `Failed to render QWeb template` **Issue:** Assertion was added in `_get_totp_mail_code` to avoid seeing the code directly in the preview (see [1]), but doing so breaks the rendering with a traceback. **Fix:** Change the assertion to a condition returning default empty values. [1] https://github.com/odoo/odoo/commit/3d85efaa2a069f81ce145aa6d4b85d350d793e96 opw-6246390
The 2FA login email template can now be previewed without triggering an error. This change makes template testing and resets work properly again, improving the admin experience when managing authentication emails.
Original PR description
Issue: ---------------------------------------- Clicking "Preview" on the template "2Fa New Login" causes an error. Steps to reproduce: ---------------------------------------- - Search for the mail template "Settings: 2Fa New Login" - Click "Preview" - Error in terminal - From 17.0+ the error shows in UI - From saas-18.3+, a traceback occurs whe resetting the template Cause: ---------------------------------------- There is an assert the method `_get_totp_mail_code()` to ensure it's used during 2FA. But when passing by rendering this template in preview we aren't in sudo and the assert in `_get_totp_mail_code()` raises. Solution: ---------------------------------------- We replace the `assert` by a `if` which will return fake results. opw-6333887 Forward-Port-Of: odoo/odoo#273125
This change fixes a flaky test in the HTML editor so it no longer fails unpredictably during double- and triple-click actions. It improves the reliability of automated checks without changing how the toolbar works for users.
Original PR description
### Description of the issue/feature this PR addresses: - Resolve non-deterministic failures in the 'toolbar should not open between double and triple click' Hoot test. - Because browser-level selectionchange events are dispatched asynchronously in the event loop, asserting on the presence of `.o-we-toolbar` in the DOM leads to timing race conditions. ### Solution: - Resolves the flakiness by introducing a wrapper method `triggerDebouncedUpdateToolbar` in `ToolbarPlugin` and refactoring the test to track method call sequences instead of asserting on DOM elements. This verifies the scheduled debounced updates in a deterministic sequence. task: https://runbot.odoo.com/odoo/error/243145 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Documentation and clarification updates
This update fixes the license metadata for several community modules so they are marked with the correct LGPL-3 license instead of an enterprise license. It helps ensure the modules are labeled consistently and accurately for legal and distribution purposes.
Original PR description
Before this commit, the license set on manifest of some modules uses the enterprise license instead of `LGPL-3` license since it is a community module. This commit changes the license to set `LGPL-3`. Fixes #205134