Thursday, June 11, 2026
5 changes · 17.0
Resolved issues and error corrections
This update resolves an issue where the documents project module would fail if a previously used XMLID was deleted. The change ensures the system gracefully handles missing XMLIDs, preventing errors and improving overall stability. This enhances the reliability of document management workflows.
Original PR description
Check that the xmlid exists and not raise any error if not found, as this xmlid can be deleted.
This update fixes an issue where the Peppol XML export incorrectly included vendor deferred dates in invoices. These dates were irrelevant for the customer and were causing export problems. The change now prevents the creation of these deferred entries and removes them from the exported invoices.
Original PR description
The current implementation of the Peppol XML export incorrectly populates the <cac:InvoicePeriod> nodes with internal deferred entry dates. These dates are intended for the vendor's revenue recognition process, and the customer has nothing to do with these dates. This commit ensures that: - deferred entries are never created when importing vendor bills. - <cac:InvoicePeriod> is no longer exported in invoices (for now). task-6014315 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes a minor issue where loading email templates in Odoo would incorrectly mark the template as 'dirty'. This change ensures a smoother experience when previewing and discarding email templates without immediately saving them to the database. It prevents potential interruptions during template editing.
Original PR description
Before this commit, when create a new email marketing and load a template, the isDirty() is true. Because we use the same isDirty function from the html field After this commit, when create a new email (not saved to db) and load a template, we consider the html field in the mass_mailing is not dirty. This is to prevent interruption when discarding after this PR: https://github.com/odoo/odoo/pull/145902 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update resolves an issue where users remained suggested recipients after unsubscribing from a mail thread. The fix ensures that the current user is completely removed from the list of suggested recipients when they click 'Unfollow,' improving the user experience and preventing unwanted notifications. This was a minor bug fix.
Original PR description
### Steps to reproduce: - Open any mail thread in chatter - Click the "Send To" button once - Click "Unfollow" - You will be a suggested recipient ### Cause of Issue: The suggested recipient generation did not filter out the current user. After unsubscribing, the current user could still be returned by `_message_get_suggested_recipients` because the user is not on the following list. https://github.com/odoo/odoo/blob/23398d24e108875b2838715d4b366df265d53234/addons/mail/models/mail_thread.py#L1881-L1907 ### Fix: Since followers are excluded from suggested recipient candidates in the mail thread, and the current user should be excluded when they unfollow, the current user is excluded altogether. opw-6122351
This update fixes an issue where invoices generated with very small product prices (e.g., $0.00003) were being incorrectly formatted in the UBL electronic invoice file. The change ensures the PriceAmount field in the UBL file adheres to the required format, preventing potential errors in electronic invoice processing. This ensures accurate and compliant invoice generation for PEPPOL transactions.
Original PR description
**STEP TO REPRODUCE** 1. Go in debug mode to increase product price decimal precision to 5. 2. Create an invoice with a product of price 0.00003 3. Send the invoice using peppol to generate the ubl file. 4. Opening the file, notice the PriceAmount is 3.33333e-05 which is not a valid string for a float in ubl. opw-6188947