Friday, January 16, 2026
4 changes · 17.0
Enhancements to existing features
This update ensures that Thai province names within Odoo are displayed in their native Thai language. This improves consistency and accuracy for users operating in Thailand, aligning with local naming conventions.
Original PR description
State names are not translatable in Odoo, so they should be stored in their native language for consistency. This PR updates all Thai provinces to use their native Thai names. task-5484432
Resolved issues and error corrections
This update fixes an issue where tooltips on the Contact Us page weren't displaying translated text. The fix ensures that saved website snippets, including their translations, are correctly applied when dropped on the Contact Us page, resolving a previous display problem.
Original PR description
Issue: Tooltip not retaining translations Steps to Reproduce : - Have a website with English as main lang and French as second lang. - Drop an image block and set a tooltip on it - Save and translate…
Issue: Tooltip not retaining translations Steps to Reproduce : - Have a website with English as main lang and French as second lang. - Drop an image block and set a tooltip on it - Save and translate the tooltip in French - In english, save the block with the image (to be able to reuse it elsewhere) - When you drop the block in a website pages or event pages, the tooltip keeps its translation, but if you drop it in the /contactus page, the tooltip has no translation. Before this PR: - A saved custom snippet would not retain its translations when dropped for the first time on the "Contact Us" page. - This occurred because the `ir.ui.view` model had only one record for `website.contactus` with `website_id=NULL`. When the snippet was dropped, a new `ir.ui.view` record was created for `website_id=1` (or the current website). During this process, only the English `jsonb` content of the snippet was added to the `arch_db` field of `ir.ui.view`. After this PR: - The saved custom snippet now retains its translations when dropped for the first time on the "Contact Us" page. Task-4543654 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update corrects a display issue in the Follow-up Levels list view. Previously, an activity was always shown even when 'Schedule Activity' was disabled. Now, the activity column only appears when 'Schedule Activity' is enabled, ensuring a cleaner and more accurate view of follow-up levels.
Original PR description
Currently, follow-up levels display an `activity` in the list view even when the `Schedule Activity` option is not enabled on the record. **Steps to reproduce:** - Install the `account_followup`…
Currently, follow-up levels display an `activity` in the list view even when the `Schedule Activity` option is not enabled on the record. **Steps to reproduce:** - Install the `account_followup` module. - Navigate to Accounting > Configuration > Invoicing > Follow-up Levels. - Click `New` and enter a `description`. - Open the `Activity tab`, `enable` Schedule Activity, set an Activity Type and Summary, then `save`. - `Disable` Schedule Activity, `save` the record again, and return to the `list view`. - Observe the `Activity` for the newly created follow-up level. **Observation:** The Activity column still shows a value in the list view, even though Schedule Activity is unchecked. **Root Cause:** At [1], `activity_type_id` is always shown in the list view without considering `create_activity`, causing the `activity` to remain visible even when `Schedule Activity` is `disabled`. **Fix:** This commit ensures that the `Activity` is displayed in the list view only when `Schedule Activity` (`create_activity`) is enabled for the record. [1]: https://github.com/odoo/enterprise/blob/d7882a8f97802d7302d81c1fa375a81bb4ca4717/account_followup/views/account_followup_line_views.xml#L13 opw-5476176
This update fixes a usability issue where the barcode on customer receipts was too narrow, making it difficult for staff to scan. The barcode width has been increased to ensure reliable scanning and streamline the order fulfillment process. This change enhances the overall customer experience.
Original PR description
Step to reproduce; - install pos_loyalty - create a loyalty program of type "next order coupon" with minimum spend of 1$. - open pos and settle a order, see receipt. Issue: - currently bar-code is too narrow, making it difficult for to be scanned Fix: - increase the width of barcode, so it can be easily scanned. <table> <tr> <td> <b>Before</b> </td> <td> <b>After</b> </td> </tr> <tr> <td> <img width="451" height="508" alt="image" src="https://github.com/user-attachments/assets/a0d1e95e-0a9d-4552-977a-0ad9686867b8" /> </td> <td> <img width="456" height="517" alt="image" src="https://github.com/user-attachments/assets/40d04ac4-9ffc-4f81-a063-31b3ea26b4e1" /> </td> </tr> </table> opw-5363916 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr