Tuesday, June 3, 2025
9 changes · saas-18.3
Resolved issues and error corrections
This fix makes certain HTML editor tests run consistently across different developer machines by standardizing font behavior used in the checks. It reduces false test failures caused by local font differences, improving development reliability without changing end-user functionality.
Original PR description
odoo/odoo#202688 updated the handling of list padding, however it hard-coded padding sizes. Those sizes can vary slightly depending on font selection (as different fonts have slightly different character dimensions). So depending on the local setup / environment, tests at issue may always fail. Add a content cleaner property to `testEditor`, and use it to nuke the `inline-padding-start` property in various tests.
This fixes the employee card layout so the presence status indicator remains in the top-right corner even when an employee name wraps onto multiple lines. It keeps the employee overview visually consistent and easier to scan for HR users.
Original PR description
With this commit, on kanban view, if employee's name is on multiple lines the employee presence status is still on the right top and not on the right bottom 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
A recent change caused an error when opening the accounting dashboard for companies using the Turkish Nilvera e-Invoice integration. This fix corrects the check for the API key so the dashboard loads normally again.
Original PR description
5d69408548b30671b968c3c1ae1e8f444ac2d82e introduced overrides for the generic EDI fetch/update logic. It mistakenly copied a condition from the XML layer that checked `.raw_value` on the API key field. This caused a traceback when accessing the accounting dashboard. No task-ID
The partners page now lets visitors view partners from every country even when GeoIP location detection is enabled. This restores the expected country filter behavior and prevents users from being automatically limited to their detected country.
Original PR description
Before this commit, if GeoIP was enabled and no country was provided, the geolocation was used automatically. As a result, it was not possible to view partners from all countries. Now, we restore the previous logic by explicitly passing a parameter to show all countries. Note: On runbot, no difference is visible since GeoIP is not enabled. 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 a small issue in time off validation where the system could look up leave allocation details using the wrong reference. It helps ensure leave types are validated correctly when employees request or manage time off.
Original PR description
This commit fixes an issue in the `_compute_valid` method of the `hr.leave.type` model. The `leave_type.id` was changed to `leave_type`, since the key type in `allocation_by_leave_type` is a recordset, not an integer. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes Google address autocomplete so businesses using a custom setup can keep providing their Google API key from configuration. It restores expected address search behavior for those deployments without changing the standard setup.
Original PR description
Until now you cannot call anymore `/autocomplete/address` without api key. Move the short-circuit later, to allow override of `_perform_place_search` to inject their specific key if needed. After this commit, if you override the `_perform_place_search` to provide your key from a config file, it works as previously.
The message composer now only auto-selects text in AI composer conversations, where that behavior is intended. This prevents regular discussion composers from unexpectedly selecting all text when users focus them, reducing small but frustrating editing interruptions.
Original PR description
**Current behavior before PR:** The composer automatically selects all its text when focused. This behavior is only expected in threads where the channel type is `ai_composer` but currently applies to all threads. **Desired behavior after PR is merged:** The automatic text selection happens only in threads where the channel type is `ai_composer`. Other composers remain unaffected and behave normally.
This fixes inconsistent ordering of payments when generating Canadian CPA005 batch payment files. The file now follows the same payment order shown in the batch payment list, helping avoid automated build failures and unpredictable file output.
Original PR description
The order of a One2many field isn't well defined and depending on the situation the records may be in the order you added them or the order defined by `_order` on the model. Before 18.3, a hack was added to sort them using `id` which worked. In 18.3 it no longer works consistently. This explicitly orders the payments when generating the file using their default _order, which is the default order in which they appear in the batch payment list view. Fixes runbot build error 181847
This update makes an internal Studio test more reliable by giving navigation state a moment to finish updating before checks run. It helps reduce false failures in automated validation, supporting smoother releases without changing user-facing behavior.