Daily updates from Odoo
Sunday, January 11, 2026
14 changes
3 changes
Resolved issues and error corrections
This update fixes an issue where accepting UrbanPiper online orders in multiple POS locations resulted in duplicate preparation tickets being printed. The fix ensures that preparation tickets are printed only once, regardless of the number of open POS sessions, improving order processing efficiency and reducing printing costs. It also cleans up local order records when an order is rejected.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103906 Forward-Port-Of: odoo/enterprise#100280
This update fixes a UI issue where long email messages would overflow their display bubbles, causing a broken user experience. The change makes email content scrollable within the message bubble, ensuring all information is visible and the interface remains functional.
Original PR description
Current behavior before PR: When the email template (message_type = `comment`) has content that is longer (in width), the content tends to overflow out of the bubble which breaks the UI. Desired behavior after PR is merged: This commit fixes the issue by making the content scrollable inside the bubble. Task-5363388 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#243034 Forward-Port-Of: odoo/odoo#237878
This update corrects a display issue where subscription delivery periods (e.g., 'Every Month') were shown in English instead of the user's selected language. The team leveraged existing translation mappings to ensure consistent, localized text on the website for subscription products. Further improvements are planned in the main branch.
Original PR description
This commit[^1] introduced a "Deliver Every [period]" text on the website for subscription consumable products, but used the raw selection key that was not translated. As a result, people would see only the "Deliver Every" part in their language, and the period in English. To fix this in stable, we used the already existing translation mapping for billing periods to also translate the delivery period on the website. In master, we can improve this further by using a computed field with a properly translatable string. Issue reported by support. [^1]: https://github.com/odoo/enterprise/commit/beb7238882eda1fd36aa22bdb6441b8bd5556ef3 Forward-Port-Of: odoo/enterprise#103645
1 change
Resolved issues and error corrections
This update fixes an issue where accepting UrbanPiper online orders in multiple POS locations resulted in duplicate preparation tickets being printed. The fix ensures that preparation tickets are printed only once, regardless of the number of active POS sessions, streamlining order fulfillment and reducing printing costs. It also cleans up local order records when an order is rejected.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103894 Forward-Port-Of: odoo/enterprise#100280
2 changes
Resolved issues and error corrections
This update fixes an issue where accepting UrbanPiper online orders in multiple POS locations resulted in multiple preparation tickets being printed. The fix ensures that preparation tickets are only generated once upon order acceptance, streamlining the process and reducing printing costs. It also removes local order records when an order is rejected.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103915 Forward-Port-Of: odoo/enterprise#100280
This update fixes a visual issue where milestone deadlines weren't shown in the Project list view. The fix ensures that milestone names now include the associated deadline, providing a clearer view of project timelines. This improves project management clarity.
Original PR description
**Steps to Reproduce:** - Install the Industry FSM module. - Navigate to Project Configuration. - Enable Milestones. - Go to the Project list view. - Observe that the Next Milestone does not display the deadline along with the milestone name. **Issue:** The milestone display name is incomplete and does not include the deadline date. **Cause:** The required context was not passed in the overrided action's context, so the display_name computation did not add the deadline to the milestone name. **Fix:** Pass the appropriate context in the action to correctly compute and display the name along with its deadline. Task: 5255295 Forward-Port-Of: odoo/enterprise#103157
8 changes
Resolved issues and error corrections
This update fixes a display issue in the Project Configuration module. Previously, milestone names in the Project list view were missing the associated deadline date. The fix ensures that milestone names now accurately show both the name and the deadline, improving clarity and usability for project managers.
Original PR description
**Steps to Reproduce:** - Install the Industry FSM module. - Navigate to Project Configuration. - Enable Milestones. - Go to the Project list view. - Observe that the Next Milestone does not display the deadline along with the milestone name. **Issue:** The milestone display name is incomplete and does not include the deadline date. **Cause:** The required context was not passed in the overrided action's context, so the display_name computation did not add the deadline to the milestone name. **Fix:** Pass the appropriate context in the action to correctly compute and display the name along with its deadline. Task: 5255295
This update resolves a minor issue within the sign flow process. Previously, selecting a specific dropdown item could result in an incomplete menu display. The fix ensures the menu always shows all available styles, improving the user experience and preventing potential confusion.
Original PR description
In this tour, when we want to select the third dropdown item in style list menu, we must wait that the rpc get_fonts/ is done, or else, it has only one item in the menu. When the menu is opened before the call is completed, there is only one style. When it is opened after, there is all styles loaded. runbot-error-id~232652
This update prevents unnecessary email reminders for timesheet approvals. The system now only sends reminders when there are actual timesheets awaiting approval, ensuring users aren't overwhelmed with notifications. This change optimizes the approval workflow and reduces email clutter.
Original PR description
prevent cron from sending approver reminder if no timesheet assigned to approver Send the reminder email if: - there are timesheets to validate - AND if the user is set as either the manager or timesheet approver of an employee with timesheets left to be validated - OR if the said employee has no manager or timesheet approver set Task-3624610 Forward-Port-Of: odoo/enterprise#102860 Forward-Port-Of: odoo/enterprise#52355
This update resolves a technical issue where the UrbanPiper POS system was incorrectly reporting an 'undefined street' error during order completion. The fix ensures that the system properly checks if a customer is assigned before finalizing an order, preventing this error and allowing customers to successfully complete their deliveries.
Original PR description
Steps to produce: ==== - Place an online delivery order through urbanpiper - Edit the order and remove customer - Complete the order as Marks as Ready - Print Reciept Issue: ==== - TB occurs stating undefined street Fix: ==== - Check whether partner is assigned or not task-5407001 Forward-Port-Of: odoo/enterprise#103633 Forward-Port-Of: odoo/enterprise#102100
This update resolves a technical issue that caused a traceback when users accessed the bank reconciliation popover in debug mode, specifically when reconciling statements with invoices in different currencies. The fix ensures the popover component functions correctly, preventing errors and improving the user experience for this common banking task.
Original PR description
In Bank reconciliation widget, when reconciling a statement with a move in different currency, users may display a popover to access some reconciliation info. Currently, accessing this component in debug mode may raise a traceback. Steps to reproduce: - Have a Bank statement in company currency - Reconcile with an invoice in foreign currency - Go in debug mode - From the reconciliation widget, locate the reconciled bank statement - Click on the reconciled bank statement popover button Issue: Traceback is shown `OwlError: Invalid props for component 'BankRecLineInfoPopOver': 'exchangeMove' is not a object` It occurs because props validation of the Owl component will fail BankRecLineInfoPopOver opw-5355964 Forward-Port-Of: odoo/enterprise#103731
This update resolves an issue where accepting UrbanPiper online orders in multiple POS locations would trigger duplicate preparation ticket prints. The fix ensures that preparation tickets are printed only once, regardless of the number of active POS sessions, improving order accuracy and reducing unnecessary printing. This change impacts the UrbanPiper integration.
Original PR description
When a POS session is open in multiple tabs/locations, accepting an UrbanPiper online order triggers multiple preparation ticket prints. Steps to reproduce: - Configure POS with UrbanPiper and a preparation printer. - Open the same POS session in multiple tabs/locations. - Receive an online food delivery order via UrbanPiper. - Accept the order in the POS terminal (TicketScreen). (Note: Order may also be auto-accepted by UrbanPiper.) Issue: - The same order printed multiple preparation tickets due to multiple active session instances. Fix: - Ensure preparation ticket prints only once when accepting (or auto-accepting) UrbanPiper orders. - Remove local order records when rejecting an online order. Task-5353283 Forward-Port-Of: odoo/enterprise#103894 Forward-Port-Of: odoo/enterprise#100280
This update fixes an issue where the 'Out of Contract' duration was incorrectly calculated, leading to inaccurate reporting. The change ensures that contract overlap dates are limited to the payslip period, providing more reliable payroll data. This improves the accuracy of employee time and cost tracking.
Original PR description
Steps to Reproduce: 1. Create a contract ending early in the year (e.g., February). 2. Compute a payslip for a much later period (e.g., November). 3. The "Out of Contract" line shows an excessive number of days (counting from Feb to Nov). Reason: - If a contract ends before the payslip period, it adds all days from the end of the contract until the end of the payslip period as "Out of Contract", ignoring the payslip start date. - If a contract starts after the payslip period, it adds all days from the payslip start date until the contract start date, ignoring the payslip end date. Solution: Constrain the calculated "Out of Contract" dates using `max()` and `min()` to ensure they never exceed the payslip's `date_from` and `date_to`. Task: 5350519 Forward-Port-Of: odoo/enterprise#103739 Forward-Port-Of: odoo/enterprise#100700
This update fixes a potential issue where the POS system incorrectly flagged refunds as exceeding order amounts due to rounding differences. The change ensures accurate comparisons between refund amounts and order totals, preventing false alerts and improving the reliability of the refund process. This resolves a technical problem related to financial reporting accuracy.
Original PR description
Before this commit, if the total amount of the order had rounding differences compared to the sum of its lines, the system could incorrectly trigger an alert stating that the refund amount exceeds the original order amount. This was due to a direct comparison between the two amounts without considering potential rounding issues. opw-5402240 Forward-Port-Of: odoo/enterprise#103551 Forward-Port-Of: odoo/enterprise#102224