Daily updates from Odoo
Navigate
Branch
Tuesday, December 31, 2024
13 changes
5 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
Miscellaneous changes
- Implemented proper validation logic for Uruguayan VAT numbers (RUT). - Now supports VAT numbers starting with '22', addressing previous validation issues. - Corrections in l10n_uy tests due to changes in logic. Task: 1292 adhoc-task-side: 45613 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191958 Forward-Port-Of: odoo/odoo#191066
Original PR description
- Implemented proper validation logic for Uruguayan VAT numbers (RUT). - Now supports VAT numbers starting with '22', addressing previous validation issues. - Corrections in l10n_uy tests due to changes in logic. Task: 1292 adhoc-task-side: 45613 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191958 Forward-Port-Of: odoo/odoo#191066
Issue: ====== We can't insert a link with `/url` in mass mailing Steps to reproduce the issue: ============================= - Install website and email marketing - Create a new mass mailing - Add a button using `/button` - Add a label - Write `/` in url and choose any option make sure to click on it using the mouse - Save - The link isn't inserted Origin of the issue: ==================== When we click to select an item, the event `mousedown` is triggered on the document which
Original PR description
Issue: ====== We can't insert a link with `/url` in mass mailing Steps to reproduce the issue: ============================= - Install website and email marketing - Create a new mass mailing - Add a button using `/button` - Add a label - Write `/` in url and choose any option make sure to click on it using the mouse - Save - The link isn't inserted Origin of the issue: ==================== When we click to select an item, the event `mousedown` is triggered on the document which will force a wysiwyg blur. So the selection is no more in the editable and we can't insert the link. Solution: ========= To avoid the blur, we add the selector of the autocomplete to the selectors that delay the blur. opw-4283325 Forward-Port-Of: odoo/odoo#192041 Forward-Port-Of: odoo/odoo#186638
**Problem**: In saas-17.2, the new URL structure no longer includes `menu_id`, which was previously used to set the current menu upon page refresh: https://github.com/odoo/odoo/blob/1443e5503c7396512a078f9f52fd4cb31b62e202/addons/web/static/src/webclient/webclient.js#L76 This change causes issues for actions like `action_orderpoint_replenish`, which are not directly tied to any `ir.ui.menu` and lack a `menu_id` in the URL: https://github.com/odoo/odoo/blob/535a02565f9e9142f0ef1fe9f44d1935f
Original PR description
**Problem**: In saas-17.2, the new URL structure no longer includes `menu_id`, which was previously used to set the current menu upon page refresh: https://github.com/odoo/odoo/blob/1443e5503c7396512a078f9f52fd4cb31b62e202/addons/web/static/src/webclient/webclient.js#L76 This change causes issues for actions like `action_orderpoint_replenish`, which are not directly tied to any `ir.ui.menu` and lack a `menu_id` in the URL: https://github.com/odoo/odoo/blob/535a02565f9e9142f0ef1fe9f44d1935f7b42075/addons/web/static/src/webclient/webclient.js#L59-L65 As a result, the menuId becomes `undefined`, leading to the top menu not being loaded properly. **Solution**: Add a path to action to ensure that it is properly reloaded. **Steps to reproduce**: 1. Navigate to *Inventory > Replenishment*. 2. Refresh the page. 3. Observe that the top menu disappears. opw-4350871 Forward-Port-Of: odoo/odoo#189402
2 changes
Enhancements to existing features
Indian GST reporting has been separated from the electronic invoicing dependency, so businesses can use GSTR reporting without also enabling EDI features. A new dedicated bridge module keeps EDI-related GSTR functionality available for companies that need it, improving setup flexibility and reducing unnecessary dependencies.
Original PR description
…ts_gstr *= l10n_in_reports_gstr, l10n_in_reports_gstr_pos, [ADD]l10n_in_reports_gstr_edi This commit removes dependency between `l10n_in_reports_gstr` and `l10n_in_edi`. task-3980324 COM PR:- https://github.com/odoo/odoo/pull/182626
Code cleanup and technical improvements
Indian localization is being reorganized so businesses can enable TDS, TCS, GST reporting, and IRN capabilities more independently. The Indian settings screen is also simplified and adds TAN support, making tax configuration clearer for companies operating in India.
Original PR description
This PR introduces the following changes: **1. Module Refactoring:** - Split `l10n_in_withholding` into independent modules: `l10n_in_tds` and `l10n_in_tcs`. This enables the users to activate the TCS and TDS features independently based on their requirement. - As part of separating `l10n_in_withholding` into `l10n_in_tds` and `l10n_in_tcs`, the `l10n_in_reports_tds_tcs` module has been split into `l10n_in_reports_tds` and `l10n_in_reports_tcs`. - Moved IRN functionality from `l10n_in_reports_gstr` to a separate module `l10n_in_gst_api`. **2. Indian Settings UI Simplification:** - Reorganized the Indian settings user interface to improve clarity and introduce a new field(`l10n_in_tan`) for TAN(use for TDS/TCS returns). **3. Dependency Removal:** - Removed the dependency between `l10n_in_reports_gstr` and `l10n_in_edi`. **COM PR:** https://github.com/odoo/odoo/pull/186860
4 changes
Resolved issues and error corrections
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.
Miscellaneous changes
### Issue: Certain carrier's API processes validity checks and parcels generation one picking at a time so that on our end we are forced to send requests one at a time at the end of the the `_action_done`: https://github.com/odoo/odoo/blob/e4f68fc6eb2a666a07b6627b9dc0ec575b79d1e3/addons/stock/models/stock_picking.py#L918 https://github.com/odoo/odoo/blob/e4f68fc6eb2a666a07b6627b9dc0ec575b79d1e3/addons/delivery/models/stock_picking.py#L192-L196 However, since a UserError of any of the picking
Original PR description
### Issue: Certain carrier's API processes validity checks and parcels generation one picking at a time so that on our end we are forced to send requests one at a time at the end of the the…
### Issue: Certain carrier's API processes validity checks and parcels generation one picking at a time so that on our end we are forced to send requests one at a time at the end of the the `_action_done`: https://github.com/odoo/odoo/blob/e4f68fc6eb2a666a07b6627b9dc0ec575b79d1e3/addons/stock/models/stock_picking.py#L918 https://github.com/odoo/odoo/blob/e4f68fc6eb2a666a07b6627b9dc0ec575b79d1e3/addons/delivery/models/stock_picking.py#L192-L196 However, since a UserError of any of the picking will cause a rollback of the entire batch on Odoo's side, pikcings might end up being processed on the carrier side but non validated on Odoo's side during batch validation. ### Steps to reproduce: - Configure sendcloud shipping method + website + payment providers - In your sendcloud configuration select sendcloud shipping product to not be able to handle products with a weight exceeding 10 kg e.g; bpost @home (0-10kg). - Create 2 storable products with respective weigth 1 and 100 kg. - Publish them on the website for sale. - Open a private window, make an order via the website for the 1kg product by filling your cart and use sendcloud as carrier. - Repeat the operation with the other product to generate a seconde SO. - Back to your main window > Inventory Overview > Delivery Orders - Select both deliveries > Action > Validate (in batch) #### > While the first delivery order was processed on carrier side (can be checked on sendcloud's website) #### > the UserError of the second DO rollbacked its validation in Odoo. ### Fix: As such, and since the carrier requests needs to happen after we have validated the pickings in Odoo, we should avoid any rollback of the transaction once any requests has already been successfully treated on the carrier side. ### Note: It is not possible restructure the code to use `senf.env.cr.savepoint` in a loop in order to reset the validation of pickings that are not valid on the carrier side because savepoints can't be used more than 64 times before the server crashes and hence can't be used in record loops. community: https://github.com/odoo/odoo/pull/190320 opw-4357325 Forward-Port-Of: odoo/enterprise#76244 Forward-Port-Of: odoo/enterprise#75502
Issue: After posting content through Social Marketing on Instagram, the generated link redirects to a non-existent post or page. Steps to Reproduce: 1. Install the Social Marketing tool. 3. Set up an Instagram account connection. 3. Create a post and attempt to click on the generated link for redirection to the post on Instagram. Solution: The issue stems from using Instagram's internal post_id, which does not work for direct URL access to the post. To resolve this, we need to requ
Original PR description
Issue: After posting content through Social Marketing on Instagram, the generated link redirects to a non-existent post or page. Steps to Reproduce: 1. Install the Social Marketing tool. 3. Set up an Instagram account connection. 3. Create a post and attempt to click on the generated link for redirection to the post on Instagram. Solution: The issue stems from using Instagram's internal post_id, which does not work for direct URL access to the post. To resolve this, we need to request the permalink associated with the post rather than relying on the internal link. This will ensure accurate redirection. While using the shortcode is an alternative, requesting the permalink directly is a more reliable approach. opw-4243329 Forward-Port-Of: odoo/enterprise#72725
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 :-
