Friday, June 27, 2025
7 changes · saas-18.4
Resolved issues and error corrections
This fix prevents the website builder from failing when a site has no social media links configured. Users can now edit social media snippets normally on new or minimal databases, avoiding an error that interrupted page editing.
Original PR description
Steps to reproduce: - On a database without demo data (and no social links set) - Open website builder in debug - Click on a social media snippet (by default there is one in footer) - Traceback: Validation of props failed because of a `false` value for input text The implementation for the options of snippet `s_social_media` (made in the website builder refactor) did not correctly handle the case where there is no record and the server returns the `false` value instead of a string. Website refactor: 9fe45e2b7ddbbfd0445ffe25a859e67a316d02b2 task-4367641
The website editor now safely handles rapid repeated clicks on the remove slide button. This prevents a page crash and keeps carousel editing stable for users.
Original PR description
__Current behavior before commit:__ When pressing on Remove slide button twice rapidly the page crashes because it tries to access the closest `.carousel` element on a slide that has already been removed from the DOM. __Description of the fix:__ - Prevent calling `removeSlide` if the slide has already been removed from the DOM. - Add a test to check the remove slide behaviour.
This fix updates the live chat test mock server so it includes the same member type information used by live chat features. This helps prevent test gaps and reduces the risk of live chat behavior breaking when features depend on member roles or types.
Original PR description
Mock server was missing `livechat_member_type`, which can lead to issues when JS features are `livechat_member_type` aware.
This fix stabilizes an automated test for the image cropping feature in the HTML editor that was failing unpredictably. It helps keep quality checks reliable so future changes can be validated with fewer false failures.
Original PR description
After merging the commit [1] the test case is non-deterministically gets failed on runbot. This commit aims to fix the test case. [1]: https://github.com/odoo/odoo/commit/7ab5d4df393e9adf6736c60945197c174149be6a --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Several screens and documents now correctly translate user-visible wording that was previously left in the source language. This improves localization consistency across payment, sales, timesheet, recruitment, loyalty, and settings experiences for users working in other languages.
Original PR description
Content passed to a t-value directive is not translated. This commit redefines as text nodes human-readable content that was incorrectly placed in a t-value, so that it is now translated. *: pos_online_payment, sale_timesheet, web, website_hr_recruitment, website_payment, website_sale_loyalty Enterprise: https://github.com/odoo/enterprise/pull/88666
Spreadsheet dashboard filters now show selected text and boolean values in a more readable way. This makes dashboards easier to understand by displaying choices like “text1 or text2” and “Is set or Is not set” instead of raw comma-separated values.
Original PR description
… boolean filters Steps to reproduce: 1. Configure a spreadsheet dashboard with a text filter and a boolean filter. 2. Set these filters to at least two values. => Boolean filter is displayed as `true,false` instead of `Is set or Is not set` => Text filter is displayed as `text1,text2` instead of `text1 or text2` To ease the testing, the function `getFacetFor` has been moved to a helper (it's already the case in master). This commit also adds a test for the others filters (relation and date). Task: 4900910 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
This fixes untranslated wording in the project budget area by placing user-facing text where the translation system can detect it. Business users working in other languages should now see the affected labels or messages translated correctly, improving consistency for multilingual teams.
Original PR description
Content passed to a t-value directive is not translated. This commit redefines as text nodes human-readable content that was incorrectly placed in a t-value, so that it is now translated. Community: https://github.com/odoo/odoo/pull/216136