Daily updates from Odoo
Monday, March 10, 2025
5 changes
Resolved issues and error corrections
Tasks created from sales orders that use quotation templates will now show the product name as the task title instead of the line description. This makes project tasks easier to identify and keeps the quotation description available in the task details.
Original PR description
### Steps to reproduce: - create a new quotation with configured quotation template - the descriptions are added by default (thanks to the template) - confirm the SO - the task is created, but it shows the description in the title (instead of the name of the product) and the description tab is empty ### Cause: In 'Quotation Templates' the description of each line is being stored under the name of 'name' so when using this quotation template in an SO the SO line name will be the template line name not the product name + the description and so when creating the task we use the name of the SO line which in that case will be the description. ### Fix: We are checking if we have a quotation template or not and if we don't we use the name of the SO line to get the name and the description of the task if we have a quotation template we use the product name for the name of the task and the name of the template line as a description. opw-4482867
Public shoppers could encounter an access error when viewing product pages that include published combo items with tax-included prices. This fix allows the page to load correctly by safely reading the needed combo product tax information.
Original PR description
Versions -------- - 18.0+ Steps ----- 1. Set website to display prices tax included; 2. have a combo item published; 3. open product's eCommerce page as public user. Issue ----- Access Error. Cause ----- Commit 4ec8d2198a1a0 added a disclaimer for combo items products tax calculations. It checks the `taxes_id` fields of the `combo_item_ids`. Issue is that the `product.combo` model isn't accessible for public users (unlike `product.product` and `product.template`. Solution -------- Use `sudo` on the combo product. opw-4608719
Accounting email aliases now mark bounce messages so the system can recognize and stop repeated rerouting. This prevents potential email loops when messages without attachments are rejected, reducing unnecessary email traffic and operational noise.
Original PR description
Sending emails with no attachments now bounce when sending to account.move aliases. This can cause loops if the bounce email is then rerouted because are not using any loop detection. Added the loop detection message id to the bounce email in order to prevent any loops. opw-4576526
This fixes a problem where indenting a bullet list item while multiple people edit the same document could trigger an error for other collaborators. The editor now handles the list structure safely, reducing interruptions and improving reliability during shared editing.
Original PR description
**Problem**: When collaborating, indenting a list item (`LI`) using "Tab" causes a structural issue in the DOM. **Scenario**: 1. User C1 and C2 both edit a list item in collaboration mode. - Common…
**Problem**:
When collaborating, indenting a list item (`LI`) using "Tab"
causes a structural issue in the DOM.
**Scenario**:
1. User C1 and C2 both edit a list item in collaboration mode.
- Common structure at the beginning:
`<ul><li>[]</li></ul>`
- When C1 presses "Tab", the DOM updates to:
`<ul (new)><li (new)><ul><li>[]</li></ul></li (new)></ul (new)>`
2. At this point C2 still has:
`<ul><li>[]</li></ul>`
3. When C2 receives a mutation update, it tries to insert:
`<ul (new)><li (new)><ul><li>[]</li></ul></li (new)></ul (new)>`
before:
`<li>[]</li>`
- **Issue**: `li` is already inside `li (new)`, causing a DOM error.
**Solution**:
- Before inserting, remove `li2`, then reinsert it at the
correct position.
- This ensures the `.before()` operation does not conflict
with `li1`.
**PS**: I adapted `createPeers` and `Wysiwygs` to make it work with
custom content and by default it will use `initialValue`, because in
this test i needed to test collaboration with `ul`, `li`.
**Steps to Reproduce**:
1. Open two tabs with the editor.
2. Create a bullet list in the first tab.
3. Press "Tab" to indent a list item.
4. Observe a traceback error in the second tab.
opw-4538671
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prDraft invoices in the Peru electronic invoicing module can now be printed correctly. The fix prevents a printing error caused by draft invoices having no invoice number yet in Odoo 18.0.
Original PR description
Since 18.0, the name field of draft invoice is false instead of "/", this causes an issue in the name replace as we try to use the replace() method on a False boolean.