Saturday, June 28, 2025
9 changes · saas-18.4
Resolved issues and error corrections
Fixes a visual alignment issue in Discuss where live chat conversation items could appear off-center in the compact sidebar. This keeps the compact view cleaner and easier to scan for users managing chats.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/215447 PR above makes improvements to new livechat status feature, one of the improvement is to show the livechat status as floating icon on livechat conversation avatar in discuss sidebar when it's not in "in progress", i.e. "waiting customer" or "need help". At some point in dev, the icon was before the avatar when discuss sidebar was not compact. This was changed in last minute to floating icon too. However template kept lefovers of old design and mistakenly put a left margin in compact mode, leading to not centered discuss sidebar items in compact mode. This commit fixes the issue by reverting to original margin rules that was before the improvements made in PR above.
This fix restores several website builder controls for carousel card snippets so they display correctly and work as expected. Users can now adjust extra height, see the right tooltips, and view translated position labels, improving editing reliability for website pages.
This update fixes a calculation error that could interrupt electronic invoice generation when invoice line quantities are zero. It also reorganizes related invoice line processing to make future maintenance and improvements safer.
Original PR description
We recently refactored UBL generation in 840bd1832ed. This commit makes some bugfixes/improvements: - prevent a ZeroDivisionError when `base_line['quantity'] == 0` - factorize the invoice line node code into a `_get_invoice_line_node` method - add the `_add_document_line_period_nodes` and `_add_document_line_pricing_reference_nodes` helpers. task-none
This update adds extra logging when email template validation fails during setup. It helps support and engineering teams diagnose rare installation issues more quickly, reducing investigation time when the problem occurs.
Original PR description
The installation of auth_signup can fail when creating mail templates. This issue is hard to reproduce and only occurs when a worker enters some broken state. Adding some log to help to solve the issue.
Fixes an issue where saving a custom website snippet could include temporary visual elements that were only meant for editing interactions. This prevents reused snippets, such as countdown blocks, from displaying incorrectly and helps keep website building reliable.
Original PR description
**Problem** Before this commit, custom snippets were saved including elements inserted by interactions (marked with `data-skip-history-hack`). These elements are not intended to be saved, and their…
**Problem** Before this commit, custom snippets were saved including elements inserted by interactions (marked with `data-skip-history-hack`). These elements are not intended to be saved, and their presence in the custom snippet could disrupt the normal functioning of an interaction (see `s_countdown` example below). This happened because interactions were not stopped before saving a snippet. **How to reproduce** 1. Save a custom snippet including `s_countdown`. E.g. insert `s_text_block`, then insert `s_countdown` in it, and finally save it as custom snippet. 2. Place the newly generated custom snippet on the page. 3. PROBLEM: the countdown rings are not centered anymore. Inspecting the page, one can see that `s_countdown` includes 8 canvas, the first 4 being invisible. **Solution** This commit introduces two new resources: `on_will_save_snippet_handlers` and `on_saved_snippet_handlers`, which are called by `saveSnippet` before and after cloning a snippet for saving. `EditInteractionPlugin` installs two handlers which stop the interactions before saving a custom snippet and restart the interactions after saving it. This way: 1. snippets are saved correctly; 2. we have a system that can be used in future to do other processing before and/or after the saving; and 3. interactions are not directly touched by `saveSnippet`. task-4367641
This fixes an error that could occur when editing website content and changing the Discussion Group snippet option. The update makes the builder handle non-text values correctly, preventing interruptions during page editing.
Original PR description
In some cases the value passed might be not string (e.g. a number),
so we don't need to check if it starts with ('var(--)'). Also, since the data-* attributes
are always strings we need to convert the value to a string when comparing them.
To replicate the error, open website and start editing, drop a "Discussion Group" snippet,
click on it, go to the Discussion Group option and change its value to something else
=> We have an error.
This commit follows [the html_builder refactoring].
[the html_builder refactoring]: odoo/odoo@9fe45e2b7ddb
Related to task-4367641This fixes the styling of date picker header buttons so they better blend with different page backgrounds, including frontend pages and dark mode. The change removes awkward button backgrounds and borders while keeping a simple hover effect, making the interface look more consistent across Odoo editions.
Original PR description
After [1], each button is separated and therefore has its own border radius and background color. On the backend side, using the ´.btn-light´ class works well since it matches the background of our…
After [1], each button is separated and therefore has its own border radius and background color. On the backend side, using the ´.btn-light´ class works well since it matches the background of our views. However, on the frontend, the background color is dynamic and does not match the page background, leading to a visually awkward result. One possible solution is to reintroduce the ´.btn-group´ class, but only wrap the "Previous" and "Next" buttons, which makes sense. However, we preferred to simply remove ´.btn-light´, which eliminates background and border issues. We only want a hover effect, similar to the one already implemented for the modal "expand" button. The result is consistent across Community, Enterprise, Backend, Frontend, and Dark mode. Additionally, the font size has been removed to ensure consistent button height, and ´text-transform´ no longer seems necessary. [1]: https://github.com/odoo/odoo/commit/e2b78fca435f268515f9593c2af821616aff7ebb Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website headers now keep selected preset background and text colors after saving, instead of reverting to the default styling. This preserves the intended site appearance for users customizing headers in the website builder.
Original PR description
Steps to reproduce: - Open website builder and click on header - Set "Header Position" to "Over The Content" - Set the "Background" color to one of the suggestion (not from the arbitrary picker) - Set the "Text Color" to one of the suggestion from the "Custom tab" - Save - Bug: The colors of the header are reset to default This issue was introduced during the initial refactor of website builder Website refactor: 9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2 task-4367641
This update fixes failing automated builds caused by recent changes to the cash basis report. It updates the related tests so they match the current report structure and no longer rely on outdated behavior.
Original PR description
The builds were failing due to this PR: https://github.com/odoo/enterprise/pull/72675 The reason is that we removed one column of the report. Another issue is that a test was trying to call an old expand function which is not in use anymore. Build failing: https://runbot.odoo.com/odoo/runbot.build.error/226793/runbot.build.error/226793