Thursday, September 21, 2023
9 changes · master
Resolved issues and error corrections
Demo point-of-sale self-order sessions now receive the missing sequence setup they need during installation. This prevents demo self-order flows from failing because required numbering information cannot be found.
Original PR description
The demo data sessions were not having the self needed sequence, so when the user tried to use the demo sessions in the self, the sequence was not found and the normal flows were not successful. This commit adds a new post_init_hook to the pos_self_order module to add the sequence to the demo data sessions. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes CRM search performance so searches using mobile phone numbers can properly benefit from the intended database index. The change corrects an internal setup mistake and helps keep contact and lead lookup reliable without changing user workflows.
Original PR description
PR #105873 added computed indexes on the `mobile` and `phone` fields for the benefit of `phone_mobile_search`, however it created both indexes to work on the `phone` field as source, rather than whichever field they were named after and partial for. As a result, the index has no effect when searching on `mobile`. Thankfully (?) the "mobile" field is mostly unused (4000 to 120000 "phone" set)
Creating a new Field Service task will now leave the assignee blank instead of automatically assigning it to the current user. This makes task creation behavior consistent across Field Service menus and avoids unintended ownership assignments.
Original PR description
Before this commit, When the user creates a new task, the assignee gets automatically set to the current user. This behavior, however, was inconsistent with how other menus in the Field Service module operated. After this commit, The assignee won't be set when creating a task. it will remain empty. task:3475473
This fix ensures restaurant demo and onboarding sessions show the correct order preparation status after a page reload. Staff using the restaurant point of sale will see the expected red indicator for orders not yet sent to the kitchen, avoiding confusion during demos or initial setup.
Original PR description
This PR resolves a bug in the self linked to the demo data. Steps to reproduce: - Create a new Restaurant session - Open mobile menu for Restaurant - Make an order in the mobile menu for a table - Reload the page where the open restaurant session is. - [BUG] The ball telling if an order is sent to the kitchen or notbecame black. - [EXPECTATION] The ball telling if an order is sent to the kitchen or not is red. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Knowledge topbar now includes the “Add to favorites” and “Remove from favorites” labels in the translation process. This helps users working in other languages see consistent, localized wording for favorite actions.
Original PR description
This commit ensures that the "Add to favorites" and "Remove from favorites" labels in the topbar component are properly added to the translations.
This update fixes how manufacturing work order documents are displayed in the document viewer. It avoids an unnecessary data reload and helps ensure images and embedded documents continue to open reliably for users.
This update fixes an internal payroll accounting test related to Belgian leave allocations. It helps keep payroll validation reliable after changes to how allocation names are automatically handled.
Original PR description
Previously, allocation name was not computed on create. Now, it's not a case anylonger. With this change, create_allocation test was failing as first the name field was assigned, then holiday_status_id; Which caused for the name field to be recomputed and assigned to False. As the field is required, leave_form.save() was raising an error. task-3389144
This fix aligns several localized point of sale modules with the updated order date handling used elsewhere. It helps ensure receipts, certifications, and local compliance records use the correct order date instead of the creation date.
Original PR description
In this previous commit: [0735ec422cdb0f3af3fb573ff78f06f0f75cfd38 ](https://github.com/odoo/odoo/pull/133293/commits/0735ec422cdb0f3af3fb573ff78f06f0f75cfd38) We changed the flow of validation_date and creation_date to date_order. But this wasn't checked in the l10n pos modules.
Fixed an issue where subscription sales log reports could appear empty when currency exchange rate data was missing. This helps users keep visibility into subscription activity even when some currency rate information is unavailable.
Original PR description
task-id: 3452269