Tuesday, February 11, 2025
6 changes · saas-18.1
Resolved issues and error corrections
This fix stops Odoo from automatically reusing similar old translations when records are updated as part of an upgrade. It helps prevent misleading or misplaced translated text appearing after upgrades, reducing the need for manual translation checks.
Original PR description
[FIX] core: disable typofix translations when upgrade Before: The typofix feature treats terms in the old and new values with similar text content as the same term, migrating the translations of the…
[FIX] core: disable typofix translations when upgrade Before: The typofix feature treats terms in the old and new values with similar text content as the same term, migrating the translations of the old term to the new term. For example The old value has the mapping: `'Draft': 'Brouillon'` The new value contains the term: `'<span invisible="name or name_placeholder or quick_edit_mode">Draft</span>'` Since the old term and the new has the same text content `'Draft'`, after write, the new term will reuse the old translation of `'Draft'`. However, the translation `'Brouillon'` is always visible unlike its en_US term Since the old term and the new term share the same text content, `'Draft'`, after `write`, the new term reuses the old translation of `'Draft'`. However, the translation `'Brouillon'` is always visible, unlike its en_US counterpart. This behavior is acceptable in non-upgrade mode because the user writes the en_US value and is responsible for verifying translations afterward. However, it is problematic during upgrades because users cannot easily identify which records have changed and need to be rechecked. After: 1. Revert 7cd56fc as it is no longer needed. 2. Disable typofix translations during upgrades. 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 fix ensures hardware devices show their pairing code for the expected five minutes after startup, even when the system clock updates automatically. It also improves detection of the device access point so the connection process starts correctly during boot.
Original PR description
This PR contains 2 commits: - [FIX] hw_drivers: pairing code cleared on time change Before this commit, if the system time was changed while the connection manager was running, it could immediately…
This PR contains 2 commits: - [FIX] hw_drivers: pairing code cleared on time change Before this commit, if the system time was changed while the connection manager was running, it could immediately finish waiting and clear the pairing code. This happens quite easily due to the system time being set via NTP just after boot. After this commit, the 5 minute wait uses `time.monotonic()`, which is not affected by system clock changes. This ensures the pairing code can stay visible for the full 5 minutes. - [FIX] hw_drivers: is_access_point false positive Before this commit, `is_access_point` was using the loopback interface `lo` to determine if the access point was up. If it was the only interface present, it returned true. However, what this actually represented was whether no network connection was present. At boot, while waiting for an IP, the access point is not up but `is_access_point` was returning true. A side-effect of this was the `ConnectionManager` never starting, and therefore no pairing code appearing for the user. After this commit, `is_access_point` uses the status of the `hostapd` service to check if the access point is up. This in turn fixes the pairing code issue. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where the point of sale customer display could fail when configured to run on another device. Businesses using a separate customer-facing screen can now add products in POS without the display breaking due to an internal reference error.
Original PR description
Steps to reproduce: - Set the customer display feature on "another device" in the settings - Open the POS and add products Reason: The refactor in 59700feb8fb6e4ca993ffdd1eef6951b9203ca06 badly kept referencing `pos` as a class field instead of a function parameter. opw-4508838
The spreadsheet component was updated to the latest version, bringing fixes for pivot table behavior and a performance improvement. Business users should see more reliable pivot reports, including correctly displayed values after sorting, and smoother spreadsheet interactions.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/338d8a17e [REL] 18.1.7 Task: 0 https://github.com/odoo/o-spreadsheet/commit/a9cb6d010 [FIX] pivot_side_panel: drag and…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/338d8a17e [REL] 18.1.7 Task: 0 https://github.com/odoo/o-spreadsheet/commit/a9cb6d010 [FIX] pivot_side_panel: drag and drop of dimensions Task: 3817565 https://github.com/odoo/o-spreadsheet/commit/24b13bf34 [IMP] perfs: improve performance of `includesAll` Task: 4548168 https://github.com/odoo/o-spreadsheet/commit/aaf12a73c [FIX] pivot: display column values in sorted pivot Task: 4536075 Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com> Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
This fixes an access issue that prevented bookkeepers from viewing the General Info section for bank accounts and related accounting records. The update preserves the correct visibility settings so users with bookkeeping responsibilities can access the information they need.
Original PR description
The Book keeper was not able to see the General info of bank accounts and so on - The problem was that there was an xpath that overwrite the groups Task-4567218
Fixed an issue where users could not smoothly drag and drop pivot dimensions when many items were listed in the spreadsheet side panel. The panel now scrolls correctly during drag-and-drop, making spreadsheet pivot configuration easier and more reliable.