Odoo Changelog — 2026-06-12

Friday, June 12, 2026

5 changes · saas-18.3

Bug Fixes(5)

Resolved issues and error corrections

[FIX] sign: PDF links unclickable in viewer

PR #120103

Enterprisesaas-18.3sign

This update fixes an issue where PDF links within the Odoo viewer were not working correctly. The problem stemmed from a layer interfering with click events. By adjusting the layer order, the links are now reliably clickable, ensuring users can access content within the PDF documents.

Original PR description

Version
- 18.0

Steps to reproduce:
1. Upload a PDF document containing bookmarks and internal/external links
2. Open the document
3. Click on the links, some work and some do not

Issue:
`canvas_layer_0` is positioned over the PDF viewer with `z-index: 1`, intercepting clicks intended for PDF link annotations and making internal/external links unresponsive. The `.textLayer` already has `z-index: 2 !important` in iframe.css to prevent the same problem for text selection

Fix:
Added `z-index: 2 !important` to `.annotationLayer section` in `iframe.css` raising it above `canvas_layer_0`.

Taskid = 6237688

Forward-Port-Of: odoo/enterprise#118040

#PDF#links#viewer

[FIX] whatsapp_event: event.mail Wrong Whatsapp template model

PR #268641

Coresaas-18.3event

This update resolves a problem where users were incorrectly denied access to WhatsApp templates when creating event communications. The fix prevents users from creating new WhatsApp templates, ensuring proper access control and preventing the 'User does not have access' error. This improves the event communication workflow.

Original PR description

Issue: 
1) User goes to Event.event Form -> communication tab -> add line
2) Select whatsapp -> type something -> create and edit -> create new template with any model event.registration -> save ( all the way including the event form)
3) reload page -> whatsapp event.mail displays "User does not have access to this record".


Fix: add "'no_create_edit': True" to the associated field in the xml to block creation of new mail.templates
opw-6037488

Forward-Port-Of: odoo/odoo#259683

#whatsapp#event#template#access

[FIX] mass_mailing{,_themes}: stop stretching media list images

PR #268638

Coresaas-18.3mass_mailing

This update fixes an issue where images in email marketing templates were stretched and distorted when paired with long text. By removing specific styling, images now maintain their natural aspect ratio and fit neatly alongside the text, ensuring a professional and consistent email design. This improves the overall visual quality of marketing campaigns.

Original PR description

The media list snippet forces the image to fill the height of its row. The
image column carries align-self-stretch and the image carries h-100, so when
the text next to the image is longer than the image is tall, the row grows to
fit the text and the image is stretched to that height (and cropped through
object-fit: cover). The longer the text, the more the image is distorted.

Drop h-100 from the image and align-self-stretch from its column in the
s_media_list snippet and in the mass_mailing_themes templates that reuse it.
With no forced height the image keeps its natural aspect ratio and the row
height follows its content, so the image is laid out next to the text instead
of being stretched to match it.

Steps to reproduce:
1. Open Email Marketing and create a new mailing.
2. Select the Blogging template for the mail body.
3. In a media item, replace the text next to an image with a very long paragraph.

=> The image is stretched and cropped to match the height of the text.

Ticket [link](https://www.odoo.com/odoo/project.task/5117571)
opw-5117571

Forward-Port-Of: odoo/odoo#238138

[FIX] account_edi_ubl_cii: handle LineExtensionAmount of 0 on UBL import

PR #269045

Coresaas-18.3account_edi_ubl_cii

This update fixes an issue where imported Peppol/UBL vendor bills with 100% discounts were incorrectly processed. The fix ensures that a line with a zero-value `LineExtensionAmount` (representing a fully discounted line) is correctly interpreted, preventing incorrect quantity and discount calculations. This improves the accuracy of UBL invoice imports.

Original PR description

When importing a Peppol/UBL vendor bill containing a line with a 100% discount, the line was created in Odoo with quantity=1 and discount of 100*original_qty, instead of the expected…

When importing a Peppol/UBL vendor bill containing a line with a 100% discount, the line was created in Odoo with quantity=1 and discount of 100*original_qty, instead of the
expected quantity=qty_original and discount=100%.

This happened because the line-level branching in
`_import_ubl_invoice_line_add_price_unit_quantity_discount` relied on the truthiness of `line_extension_amount` to detect whether the `LineExtensionAmount` node was present in the XML. a line with a genuine `<cbc:LineExtensionAmount>0</...>` was indistinguishable from a line where the node was missing, and fell
through to the fallback branch intended for incomplete XML. That fallback reconstructs the quantity from `<cbc:BaseQuantity>`, ignoring `<cbc:InvoicedQuantity>`, and then computes the discount percentage against the wrong denominator.

a `LineExtensionAmount` of 0 is the only legal way to express a fully discounted line, so this case must be distinguished from the node being absent.

the fix is simply checking if the line exist not if its True

opw-6176349

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#265261

[FIX] l10n_eg_edi_eta: catch json.JSONDecoderError

PR #269459

Coresaas-18.3l10n_eg_edi_eta

This update resolves an issue where errors occurred when downloading ETA invoice PDFs due to problems decoding JSON data. A recent change introduced a workaround, but a new error type wasn't being caught. This fix adds a necessary catch block to ensure all JSON decoding errors are handled correctly, preventing potential download failures.

Original PR description

When we download the ETA invoice PDF, a JSONDecoderError can happen when calling the json() method on the request. This error is properly caught by Odoo :

https://github.com/odoo/odoo/blob/7a9a340e0dbac470c4bea3f8ce8a32e55f3e82e6/addons/l10n_eg_edi_eta/models/account_edi_format.py#L58-L60

However, the following commit introduced a monkeypatch to handle errors when the simplejson library is
installed : 2435fe76eec1fc4320ef71726fc7f16ece653a32

If we meet the conditions, the original error is replaced by a json.JSONDecodeError which is not caught during the previous process.

We propose to add this error to the catch block.

This modification was inspired by the commit
d483dac144a9caf84c44b9d8d394ea327ca87cfe.

opw-6266862

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/odoo#268309

#invoice#eta#edi

Version - 18.0 Steps to reproduce: 1. Upload a PDF document containing bookmarks and internal/external links 2. Open the document 3. Click on the links, some work and some do not Issue: `canvas_layer_0` is positioned over the PDF viewer with `z-index: 1`, intercepting clicks intended for PDF link annotations and making internal/external links unresponsive. The `.textLayer` already has `z-index: 2 !important` in iframe.css to prevent the same problem for text selection Fix: Added `z-index: 2 !important` to `.annotationLayer section` in `iframe.css` raising it above `canvas_layer_0`. Taskid = 6237688 Forward-Port-Of: odoo/enterprise#118040

Issue: 1) User goes to Event.event Form -> communication tab -> add line 2) Select whatsapp -> type something -> create and edit -> create new template with any model event.registration -> save ( all the way including the event form) 3) reload page -> whatsapp event.mail displays "User does not have access to this record". Fix: add "'no_create_edit': True" to the associated field in the xml to block creation of new mail.templates opw-6037488 Forward-Port-Of: odoo/odoo#259683

The media list snippet forces the image to fill the height of its row. The image column carries align-self-stretch and the image carries h-100, so when the text next to the image is longer than the image is tall, the row grows to fit the text and the image is stretched to that height (and cropped through object-fit: cover). The longer the text, the more the image is distorted. Drop h-100 from the image and align-self-stretch from its column in the s_media_list snippet and in the mass_mailing_themes templates that reuse it. With no forced height the image keeps its natural aspect ratio and the row height follows its content, so the image is laid out next to the text instead of being stretched to match it. Steps to reproduce: 1. Open Email Marketing and create a new mailing. 2. Select the Blogging template for the mail body. 3. In a media item, replace the text next to an image with a very long paragraph. => The image is stretched and cropped to match the height of the text. Ticket [link](https://www.odoo.com/odoo/project.task/5117571) opw-5117571 Forward-Port-Of: odoo/odoo#238138

When importing a Peppol/UBL vendor bill containing a line with a 100% discount, the line was created in Odoo with quantity=1 and discount of 100*original_qty, instead of the expected quantity=qty_original and discount=100%. This happened because the line-level branching in `_import_ubl_invoice_line_add_price_unit_quantity_discount` relied on the truthiness of `line_extension_amount` to detect whether the `LineExtensionAmount` node was present in the XML. a line with a genuine `<cbc:LineExtensionAmount>0</...>` was indistinguishable from a line where the node was missing, and fell through to the fallback branch intended for incomplete XML. That fallback reconstructs the quantity from `<cbc:BaseQuantity>`, ignoring `<cbc:InvoicedQuantity>`, and then computes the discount percentage against the wrong denominator. a `LineExtensionAmount` of 0 is the only legal way to express a fully discounted line, so this case must be distinguished from the node being absent. the fix is simply checking if the line exist not if its True opw-6176349 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#265261

When we download the ETA invoice PDF, a JSONDecoderError can happen when calling the json() method on the request. This error is properly caught by Odoo : https://github.com/odoo/odoo/blob/7a9a340e0dbac470c4bea3f8ce8a32e55f3e82e6/addons/l10n_eg_edi_eta/models/account_edi_format.py#L58-L60 However, the following commit introduced a monkeypatch to handle errors when the simplejson library is installed : 2435fe76eec1fc4320ef71726fc7f16ece653a32 If we meet the conditions, the original error is replaced by a json.JSONDecodeError which is not caught during the previous process. We propose to add this error to the catch block. This modification was inspired by the commit d483dac144a9caf84c44b9d8d394ea327ca87cfe. opw-6266862 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#268309