Odoo Changelog — 2026-07-13

Monday, July 13, 2026

303 changes

Bug Fixes(3)

Resolved issues and error corrections

[FIX] website: duplicate t-key error when opening Optimize SEO menu

Coresaas-19.3website

This update resolves an error that occurred when multiple product images with the same content were used on the website's 'Optimize SEO' feature. The fix ensures that image IDs are uniquely identified, preventing the 'duplicate key' error and improving the stability of the SEO optimization process. This ensures the website's SEO tools function correctly for all users.

Original PR description

## Problem: when snippets with identical images are added in the e-commerce website product page, the "Optimize SEO" option in debug mode causes an error to occur with a traceback. The traceback…

## Problem:
when snippets with identical images are added in the e-commerce website product page, the "Optimize SEO" option in debug mode causes an error to occur with a traceback. The traceback calls out a duplicate key in the `t-foreach` of a loop over `state.altAttributes`. the `t-key` for this loop is `img.id` which is generated by the `/website/get_alt_images` controller endpoint.

## Steps to reproduce:
1. Go to a product page and click on "go to website" smart nav btn.
2. Add a snippet with an image in the `description_ecommerce` field
3. Add a snippet with the same image in the `website_description` field.
4. In debug mode, open `site > Optimize SEO`
5. An error `Got duplicate key in t-foreach` is thrown.

## Solution:
The solution was simple to add a qualifier in the compound key generated by the controller action for the `id` field. The chosen qualifier in this case was `model['field']`. `field` is the position in the template where the image came from.

So now the keys for the two identical images go 

FROM
 
> `${model}-${id}-${index}`
>
> 1st image of `website_description`:
>    `product.template-6-0`
> 
> 1st image of `description_ecommerce`:
>    `product.template-6-0`

TO

> `${model}-${id}-${field}-${index}`
>
> 1st image of `website_description`:
>    `product.template-6-website_description-0`
>
> 1st image of `description_ecommerce`:
>    `product.template-6-description_ecommerce-0`

task-6325786

Forward-Port-Of: odoo/odoo#275789
Forward-Port-Of: odoo/odoo#272846

#seo#website#images#optimization

[FIX] project[_todo]: IS TRUE index

PR #275914

Coresaas-19.3project_todoproject

This update fixes an issue where a database index wasn't being utilized by Odoo's internal queries. The change ensures the index works correctly for all queries, including those generated by Odoo, improving data retrieval performance. This enhances the efficiency of project and to-do related operations.

Original PR description

The index added by 778c09f4ffb4 works for the specific query it was meant to improve.

Unfortunately, it cannot be used by ORM-generated queries, which is unfortunate. The reason is that the ORM generates queries with `IS TRUE` or `IS NOT TRUE` for boolean fields.

Because `=` and `IS` do not have the same semantics, postgresql cannot use the index for ORM-generated queries.

= -> eval(NULL = True) -> NULL
IS -> eval(NULL IS TRUE) -> FALSE

By changing both the index and the query to use `IS TRUE`, the index is now used by both the specific query and the ORM.



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

Forward-Port-Of: odoo/odoo#275681

#performance#database#index

[FIX] l10n_rs_edi: default tax date obligation to 'By Delivery Date'

PR #275990

Coresaas-19.3l10n_rs_ediMEDIUM

This update fixes a discrepancy in how the VAT tax date is calculated for Serbian invoices. Previously, the default date was set to 'By Issuance Date,' which wasn't compliant with Serbian law. Now, the default is 'By Delivery Date,' aligning with Article 16 of the Serbian VAT Law and ensuring accurate tax reporting.

Original PR description

According to[ Article 16 of Serbia's VAT Law](https://www.paragraf.rs/propisi/law-on-value-added-tax.html#:~:text=of%20Tax%20Obligation-,Article%2016,-A%20tax%20obligation),
the tax obligation arises at the time of delivery of goods/services by default. 'By Issuance Date' only applies to a narrow set of services under Article 16(2a)

Before: l10n_rs_tax_date_obligations_code defaulted to '3' (By Issuance Date)
After: defaults to '35' (By Delivery Date)

Upgrade: odoo/upgrade#10657
task-6348377

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

Forward-Port-Of: odoo/odoo#273608

#VAT#Serbia#Tax Compliance

Rows:Rows per page:

10 25 50 100

4 / 4Page 4 of 4 · 303 days total

## Problem: when snippets with identical images are added in the e-commerce website product page, the "Optimize SEO" option in debug mode causes an error to occur with a traceback. The traceback calls out a duplicate key in the `t-foreach` of a loop over `state.altAttributes`. the `t-key` for this loop is `img.id` which is generated by the `/website/get_alt_images` controller endpoint. ## Steps to reproduce: 1. Go to a product page and click on "go to website" smart nav btn. 2. Add a snippet with an image in the `description_ecommerce` field 3. Add a snippet with the same image in the `website_description` field. 4. In debug mode, open `site > Optimize SEO` 5. An error `Got duplicate key in t-foreach` is thrown. ## Solution: The solution was simple to add a qualifier in the compound key generated by the controller action for the `id` field. The chosen qualifier in this case was `model['field']`. `field` is the position in the template where the image came from. So now the keys for the two identical images go FROM > `${model}-${id}-${index}` > > 1st image of `website_description`: > `product.template-6-0` > > 1st image of `description_ecommerce`: > `product.template-6-0` TO > `${model}-${id}-${field}-${index}` > > 1st image of `website_description`: > `product.template-6-website_description-0` > > 1st image of `description_ecommerce`: > `product.template-6-description_ecommerce-0` task-6325786 Forward-Port-Of: odoo/odoo#275789 Forward-Port-Of: odoo/odoo#272846

The index added by 778c09f4ffb4 works for the specific query it was meant to improve. Unfortunately, it cannot be used by ORM-generated queries, which is unfortunate. The reason is that the ORM generates queries with `IS TRUE` or `IS NOT TRUE` for boolean fields. Because `=` and `IS` do not have the same semantics, postgresql cannot use the index for ORM-generated queries. = -> eval(NULL = True) -> NULL IS -> eval(NULL IS TRUE) -> FALSE By changing both the index and the query to use `IS TRUE`, the index is now used by both the specific query and the ORM. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#275681

According to[ Article 16 of Serbia's VAT Law](https://www.paragraf.rs/propisi/law-on-value-added-tax.html#:~:text=of%20Tax%20Obligation-,Article%2016,-A%20tax%20obligation), the tax obligation arises at the time of delivery of goods/services by default. 'By Issuance Date' only applies to a narrow set of services under Article 16(2a) Before: l10n_rs_tax_date_obligations_code defaulted to '3' (By Issuance Date) After: defaults to '35' (By Delivery Date) Upgrade: odoo/upgrade#10657 task-6348377 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#273608