Wednesday, December 18, 2024
8 changes · 18.0
Resolved issues and error corrections
This fixes issues in Point of Sale where scale readings on the customer-facing display could fail, show outdated net weight, or remain visible after a weighing was cancelled. It helps restaurant and retail staff avoid confusing customers and prevents errors when switching views without an active order.
Original PR description
Since #176062, the customer display is able to mirror the scale measurements. This commit fixes some bugs with this feature: - A traceback when no order is selected (this can happen when returning to the plan view in a restaurant) - The net weight not updating correctly on the customer display - The scale values remaining on the customer display indefinitely if weighing is cancelled opw-4343571, opw-4343559 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Orders placed at a self-order kiosk and paid at the counter are now sent to the preparation display as soon as they are created. This helps staff see and prepare kiosk orders promptly, reducing missed orders or delays.
Original PR description
*: pos_online_payment_self_order When creating an order from the kiosk and pay it at the counter, it should be sent to PDIS when creating it. opw-4364309
Partner records now use country-specific labels when warning about duplicate tax IDs or company registry numbers, making messages easier to understand. Morocco also gets stricter ICE number validation and duplicate warnings, while Australia and New Zealand receive clearer company registry labels.
Original PR description
* Add custom tax ID and company registry labels for warning messages to partners with the same tax ID/company registry. * Add custom company registry label for AU and NZ * Make sure the ICE number has 15 digits otherwise show an error message. * Move ICE to be below the Tax ID field. task-4226448 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Customers using a website tied to a company branch could hit an access error when adding branch-specific products to their cart. The fix ensures tax filtering can correctly handle company branch relationships, preventing failed cart actions for public or restricted users.
Original PR description
Scenario: - create a company branch, with a website and a product for that branch - add that product to a cart from that website branch with a user that only has that branch in its allowed companies…
Scenario: - create a company branch, with a website and a product for that branch - add that product to a cart from that website branch with a user that only has that branch in its allowed companies (eg. public user) => an AccessError is raised because we can't read "parent_id" of parent company when passing in method account.tax()._filter_taxes_by_company Note: The error doesn't happen if the product is not in the company, because then we will check access rules which will set the parent res.company record in the cache, so no access error happen. Fix: Add sudo in account.tax()._filter_taxes_by_company method. The sudo could be put on company_id argument by the calling method (eg. 4 calls in website_sale) but it's hard to know that sudo is necessary since it works in a lot of case by chance because the res.company records are already in cache. Note: added test fails with odoo.exceptions.AccessError because we try to read "parent_id" of the branch company. opw-4282334
This fixes two issues in the HTML editor: Ctrl-clicking a link now opens it in a new tab, and internal Odoo links now show the correct preview instead of a warning. This makes editing linked content smoother and reduces confusing error messages for users.
Original PR description
**Problem**: 1. `Ctrl+click` on a link in the editor does not open the link in a new tab. 2. Internal links with the format `odoo/<model>/<record_id>` do not display a proper preview. Instead, a…
**Problem**: 1. `Ctrl+click` on a link in the editor does not open the link in a new tab. 2. Internal links with the format `odoo/<model>/<record_id>` do not display a proper preview. Instead, a warning toaster appears: _"Action `<model>` not found, link preview is not available. Please check your URL is correct."_ **Solution**: 1. Implement the same code as version 17.0 to handle `ctrl+click` for opening links in a new tab: https://github.com/odoo/odoo/commit/981290ee9c88ea00440268d2a7b829d3a601a2d2 2. For internal links (`odoo/<model>/<record_id>`), validate the `action_name` as a model name. If valid, treat `action_name` as the model name for the link preview. **Steps to reproduce**: 1. Open the editor. 2. Add a link with the path `odoo/project.task/59`. 3. Try `Ctrl+click`: - **Issue**: The link does not open in a new tab. 4. Observe the warning toaster: _"Action project.task not found, link preview is not available. Please check your URL is correct."_ opw-4353235 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Orders created at a self-order kiosk and paid at the counter are now sent to the preparation display as soon as they are created. This helps kitchen or preparation staff see these orders promptly and reduces the risk of missed or delayed preparation.
Original PR description
When creating an order from the kiosk and pay it at the counter, it should be sent to PDIS when creating it. opw-4364309
The Moroccan reporting export now makes it possible to identify partners that are missing required ICE or Tax ID details when preparing XML reports. This helps users correct partner records more easily and reduces export issues caused by incomplete tax information.
Original PR description
* From OXP feedback, there was no way to view partners with missing ICE/Tax ID when exporting reports as XML. * Fix ICE numbers in tests. task-4226448
Fixes an error that could stop Australian ABA batch payments from being validated. The payment process now uses the correct payment description field, allowing vendor batch payments to proceed normally.
Original PR description
**Steps to reproduce:** - Install l10n_au_aba - Switch to an Australian company (e.g. AU Company) - Configure batch payments according to fiscal localization docs in Odoo (https://www.odoo.com/documentation/18.0/applications/finance/fiscal_localizations/australia.html#aba-files-for-batch-payments) - Configure a bank account for a vendor - Create a bill for that vendor - Confirm the bill - Register a payment with "ABA Credit Transfer" as payment method - Go to the payments list - Select the created payment and create a batch payment - Validate the batch payment **Issue:** A traceback is raised while trying to access "ref" field of "account.payment" model. **Cause:** "ref" field has been replaced by "memo" field in "account.payment" model. opw-4346794 opw-4355394