Daily updates from Odoo
Tuesday, December 31, 2024
10 changes
2 changes
Resolved issues and error corrections
The point of sale checkout now removes unnecessary payment lines with a zero amount before validating an order. This keeps receipts and backend records cleaner by avoiding confusing empty payment entries.
Original PR description
Steps to reproduce : ------------------------- - Install the point_of_sale module. - Order something and go to payment page. - Apply multiple payment lines even with 0 amount. Issue : ------- The payment lines with 0 amount is also shown on receipt as well. Cause : ---------- We never checked for the amount of paymentline. Fix : ---- Updated the condition to remove 0 amount paymentline from the view. task - 4285705
Customers viewing delivery location selection on the website will now see previously untranslated labels in their chosen language. This fixes a mismatch where delivery text was defined outside the website translation area, improving clarity for multilingual shoppers.
Original PR description
There are some terms that are defined in `delivery` module but are not translated when you see them on the website. This happens because these strings are defined in the `delivery` module, which is not a frontend module. This commit redefines those strings in the `website_sale` module, which is a fronend module. Task-4328208 OPW-4403072 OPW-4326840
6 changes
Resolved issues and error corrections
This fix prevents an error when creating a manufacturing order component if the unit of measure is removed and the quantity is changed. Users can now adjust the quantity without the screen crashing, improving reliability during manufacturing order entry.
Original PR description
Currently, a traceback is occurring when the user removes the `uom` and tries to change the `product_uom_qty` in the stock move. While creating the Manufacturing Order. To reproduce this issue: 1) Install MRP and enable UOM from the configuration 2) Create a new mrp order and add a product in components 3) Remove the UOM and change the `To Consume` value Error:- ``` AssertionError: precision_rounding must be positive, got 0.0 ``` This traceback occurs because when the user changes the `product_uom_qty`, an onchange method `_onchange_product_uom_qty` will triggered. In that method, `float_round` is used with precision_rounding getting from `product_uom.rounding`. It leads to the above traceback as `product_uom` has an empty recordset. sentry-6170644216
When creating a recruitment application, key contact fields such as email, phone number, and LinkedIn profile now appear immediately. This makes it easier for recruiters to enter applicant details without first assigning a candidate.
Original PR description
Steps to Reproduce: • Install the Recruitment app. • Open any Job Position. • Click New to create a new application, The Email, Phone Number, and LinkedIn Profile fields are not visible until a candidate is assigned. Cause: The fields were set to be conditionally invisible based on candidate assignment. Fix: Removed the visibility conditions to ensure these fields are always visible. task-4385022 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
POS receipts for GCC countries now show the cashier name only once instead of repeating the "Served by" text. This improves receipt clarity for customers and staff while leaving receipts in other countries unchanged.
Original PR description
Description of the issue/feature this PR addresses: In GCC countries, the POS receipt displays duplicate "Served by" text due to inconsistent handling of the cashier field in the getReceiptHeaderData method. Current behavior before PR: 1. The "Served by" text is duplicated on POS receipts for GCC countries. 2. The issue arises from both the base implementation and the l10n_gcc_pos module adding the "Served by" prefix. Desired behavior after PR is merged: 1. The POS receipt correctly displays the cashier's name without duplication. 2. For GCC countries, the "Served by" prefix is removed, and only the cashier's name is displayed. 3. Non-GCC countries remain unaffected. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue where the live chat bot could fail to restart on embedded external websites after a visitor was redirected. The bot now starts as soon as the active live chat conversation is available, improving continuity for visitors and support teams.
Original PR description
Previously, the chat bot would fail to restart on external websites after a redirection. The issue occurs because the chat bot service waits for the mail store to be ready before verifying if the current live chat thread is linked to a chat bot. However, since [1], the thread is only assigned after the ready event. While the website app assigns the visitor thread earlier, embedded websites do not, causing the chat bot service to incorrectly assume that no bot is linked to the live chat thread and fail to start. This PR resolves the issue by leveraging modelization. The chat bot now starts when the current live chat thread is inserted. [1]: https://github.com/odoo/odoo/pull/173197 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Imported websites can once again accept new content blocks through drag and drop. This restores expected editing behavior, so users can continue building pages after an import without workarounds.
Original PR description
After importing a website, it was not possible to drag and drop new blocks. You could still edit them but not add new ones. Fixed it by changing the way the snippets are added into the view.
Several automated walkthroughs were made more precise and reliable across sales, e-signature, helpdesk forum, and subscription flows. This helps reduce false test failures and supports smoother validation of important customer-facing processes.
Original PR description
In this commit, we fix 4 tours by being more precise on the triggers and/or adding intermediate steps to ensure the proper conduct of the tour. We take advantage of this commit to linter the tour files.
2 changes
Resolved issues and error corrections
This update ensures that customer names are now included in FedEx shipping requests when shipping to companies. FedEx support confirmed this was a requirement, resolving a previous error that occurred when delivery and billing addresses differed. This improves shipping accuracy and reliability.
Original PR description
Before this commit: Only `companyName` is included in shipping requests sent to FedEx. After this commit: `personName` is added to the request, same as `companyName`. According to FedEx documentation, it is not required if the address is `buisness` but we get an error if the `deliveryAddress` and `soldTo` address are different. Checked with FedEx support, and they said it is required to send the `personName` field always. opw-4415536
This update resolves a technical issue preventing users from editing shipping documents reports within the Odoo Studio. The fix corrects a typo in the report's code, preventing an error when searching for a specific element on the report's design. This ensures the Studio editor functions correctly for all shipping label reports.
Original PR description
while opening report in report('shipping Document','Shipping Labels') through studio this traceback is raising because their is no node have with [id = 'wrapwrap'] due to that while checking xpath it…
while opening report in report('shipping Document','Shipping Labels') through studio this traceback is raising because
their is no node have with [id = 'wrapwrap'] due to that while checking xpath it is giving the error because their is no element and returing None so checking before accessing.
Traceback
```
RPC_ERROR
Odoo Server Error
Traceback (most recent call last):
File "/data/build/odoo/odoo/http.py", line 1765, in _serve_db
return service_model.retrying(self._serve_ir_http, self.env)
File "/data/build/odoo/odoo/service/model.py", line 133, in retrying
result = func()
File "/data/build/odoo/odoo/http.py", line 1792, in _serve_ir_http
response = self.dispatcher.dispatch(rule.endpoint, args)
File "/data/build/odoo/odoo/http.py", line 1996, in dispatch
result = self.request.registry['ir.http']._dispatch(endpoint)
File "/data/build/odoo/addons/website/models/ir_http.py", line 235, in _dispatch
response = super()._dispatch(endpoint)
File "/data/build/odoo/odoo/addons/base/models/ir_http.py", line 222, in _dispatch
result = endpoint(**request.params)
File "/data/build/odoo/odoo/http.py", line 722, in route_wrapper
result = endpoint(self, *args, **params_ok)
File "/data/build/enterprise/web_studio/controllers/report.py", line 471, in load_report_editor
report_qweb = self._get_report_qweb(report)
File "/data/build/enterprise/web_studio/controllers/report.py", line 604, in _get_report_qweb
main_qweb.xpath("//*[@id='wrapwrap']")[0]
IndexError: list index out of range
The above server error caused the following client error:
OwlError: An error occured in the owl lifecycle (see this Error's "cause" property)
at handleError (https://61184473-17-0-all.runbot103.odoo.com/web/assets/ffa43fc/web.assets_web.min.js:916:101)
at App.handleError (https://61184473-17-0-all.runbot103.odoo.com/web/assets/ffa43fc/web.assets_web.min.js:1542:29)
at ComponentNode.initiateRender (https://61184473-17-0-all.runbot103.odoo.com/web/assets/ffa43fc/web.assets_web.min.js:1006:19)
Caused by: RPC_ERROR: Odoo Server Error
```
on clicking on this error is raising :-
