Friday, April 4, 2025
3 changes · saas-17.4
Resolved issues and error corrections
The self-ordering kiosk now correctly displays product names and interface text in the language selected by the customer. This prevents confusion for multilingual kiosks, especially when website language settings differ from Point of Sale kiosk settings.
Original PR description
The self-ordering kiosk does not correctly display translations for product names and other UI elements when switching languages. Some elements remain in English or the database language, even when…
The self-ordering kiosk does not correctly display translations for product names and other UI elements when switching languages. Some elements remain in English or the database language, even when translations are available. ### Steps to Reproduce 1. Open **Point of Sale** and navigate to **Configuration > Settings**. 2. Select a POS configuration that has **Kiosk/Self-ordering** enabled. 3. Add additional languages to the Kiosk and save the changes. 4. Open a product available in the Kiosk POS and add translations for its name. 5. Start a new Kiosk session, switch to the Kiosk window, and change the language. 6. Notice that product names and other UI elements remain in English instead of switching to the selected language. ### Cause - The `/pos-self/data/<config_id>` route was missing `website=True`, preventing it from receiving the correct frontend language setting. - Adding `website=True` fixes this issue, allowing the POS frontend to receive the correct language. ### Secondary Issue - After adding `website=True`, another problem emerged when the **website module** is installed. - In this case, the available languages were taken from the **website settings** instead of the **POS settings**. - This means that if the website only supports English but the POS Kiosk supports both English and French, switching the Kiosk language to French would fail. The system would always revert to English because language validation was still based on website settings rather than POS settings. ### Solution 1. **Fix the original issue** by adding `website=True` to ensure the POS self-ordering system receives the correct language. 2. **Work around the secondary issue** by checking the **Referer** header to determine if the request comes from a POS self-ordering session. 3. **Ensure language validation is based on POS settings**, not website settings, by retrieving available languages from the POS configuration when necessary. This solution follows a similar approach to the fix in **cd69a32503f4dcd11851908e2c983e1d49a1c2a8**, but in this case, the problematic route (`/website/translations`) is not strictly POS-related. Therefore, we must check the referer to extract the correct POS information. opw-4557569 opw-4471819 opw-4436306
The spreadsheet component was updated to a newer version with improvements to how text spacing and line breaks are processed. This should make spreadsheet editing and formula handling feel faster and more reliable for users.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/2937d9918 [REL] 17.4.29 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/2937d9918 [REL] 17.4.29 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/186b1f284 [PERF] tokenize: faster space tokenize [Task: 4684215](https://www.odoo.com/odoo/2328/tasks/4684215) https://github.com/odoo/o-spreadsheet/commit/970f7360d [REF] tokenize: extract new line tokenize [Task: 4684215](https://www.odoo.com/odoo/2328/tasks/4684215) 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 how German balance sheets calculate profit or loss for the current and previous fiscal years. It helps ensure carried-forward results and yearly net income or loss are shown accurately for reporting and compliance.
Original PR description
Backport of https://github.com/odoo/enterprise/pull/82748 Profit and loss from previous year was not well calculated on the balance sheet. With this commit, we change the date scope for the `Net profit/loss for the year` line from `normal` to `from_fiscalyear`. We also change the way we calculate `Profit carried forward/loss carried forward` and `Net income/loss for the year` lines. opw-3663626