Odoo Changelog — 2026-07-22

Wednesday, July 22, 2026

4 changes · saas-18.4

Bug Fixes(4)

Resolved issues and error corrections

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

Enterprisesaas-18.4whatsapp_eventMEDIUM

This fix prevents users from creating or editing WhatsApp message templates from the event communication flow in a way that could link the wrong record type. It avoids confusing access errors after saving and reloading an event, while respecting the separate approval process required for WhatsApp templates.

Original PR description

Issue:

User goes to Event.event Form -> communication tab -> add line
Select whatsapp -> type something -> create and edit -> create new template with any model event.registration -> save ( all the way including the event form)
reload page -> whatsapp event.mail displays "User does not have access to this record".
Fix: add a patch to the js get m2oProps to deactivate edit, and create on the prop.

WA Templates need more limitations for creation and edits due to the approval process from META's external API.
We cannot block the full creation and edit in the xml becuase other event.mail types rely on that flow to create their types like social posts.
This was a fix implemented due to needing to revert the oginal fix odoo/odoo@f58e9f97192ac0ff8d159377494d6c68f871d20b

opw-6334168

Forward-Port-Of: odoo/enterprise#124156
Forward-Port-Of: odoo/enterprise#121852

#whatsapp#events#templates#access-error

[FIX] l10n_cl_edi_stock: kit component guide price

PR #124821

Enterprisesaas-18.4l10n_cl_edi_stockMEDIUM

Delivery guides for kit products in Chile now avoid pricing errors when kit components use different units of measure than the sold kit. This prevents failures when users print delivery guides priced from the sale order, keeping deliveries and documentation flowing correctly.

Original PR description

When a kit is delivered, each component move is linked to the kit's sale order line. Pricing the delivery guide in "sale order" mode converted the component quantity into the kit's sale UoM. For a component sold in a different UoM category than the kit, this cross-category conversion raises a UserError.

Steps to reproduce:
- Create a BoM for a kit product with a component in a different UoM category
- Create a customer with Delivery Guide Price = "From Sale Order"
- Sold the kit in a sale order and deliver it
- On the delivery, print the delivery guide -> error

This fix makes the guide price for a component move to be "product" if the component's product is different from the related sale line product, avoiding the cross-category UoM conversion.

opw-6327895

Forward-Port-Of: odoo/enterprise#124747
Forward-Port-Of: odoo/enterprise#122776

#Chile#delivery guide#kits#pricing

[FIX] whatsapp_identifiers: add .weblate.json entry

PR #124340

Enterprisesaas-18.4whatsapp_identifiers

The WhatsApp identifiers module is now properly registered for translation file handling. This helps ensure its text can be included in the standard translation workflow, reducing the risk of missing translated labels for users.

Original PR description

pot files must be registered there.

See 9966b160972a053e051f2213846acc64d133f2a3

Forward-Port-Of: odoo/enterprise#124076
Forward-Port-Of: odoo/enterprise#124026

#translations#whatsapp

[FIX] website_sale_renting_planning: fix traceback

PR #125109

Enterprisesaas-18.4website_sale_renting_planningMEDIUM

Opening a rentable service product on the website no longer fails when the assigned employee resource has no working calendar. The system now uses the company calendar as a fallback only for leave calculations, keeping customer-facing availability behavior unchanged.

Original PR description

Steps to reproduce:
------------
  - Install website_sale_renting_planning.
  - Create an employee without a working calendar.
  - Create a service product and enable the planning service.
  - Configure the product:
     - type -> service
     - plan services
         - assign the resource created above.
         - enable sync shifts and rental orders.
  - open the product on the website.

Issue:
------------
   when the resource does not have a working calendar, opening the product on the website raises a singleton traceback.

Cause:
--------
   The _leave_intervals_batch method uses [ensure_one](https://github.com/odoo/odoo/blob/3364b3b38f7d3891d8c69b87fb8234eb9ac8e52b/addons/resource/models/resource_calendar.py#L531-L542),  so a calendar record is needed.

Fix:
----
   - when the resource does not have a working calendar, fall back to the resource's company working calendar
   before calling _leave_intervals_batch. 
   - I used the company calendar only when computing the resource's leave intervals. It is not used to display the company's
    non-working days.

 I found this issue while working on this task-5411076

#website#rentals#planning#calendar#stability

Issue: User goes to Event.event Form -> communication tab -> add line Select whatsapp -> type something -> create and edit -> create new template with any model event.registration -> save ( all the way including the event form) reload page -> whatsapp event.mail displays "User does not have access to this record". Fix: add a patch to the js get m2oProps to deactivate edit, and create on the prop. WA Templates need more limitations for creation and edits due to the approval process from META's external API. We cannot block the full creation and edit in the xml becuase other event.mail types rely on that flow to create their types like social posts. This was a fix implemented due to needing to revert the oginal fix odoo/odoo@f58e9f97192ac0ff8d159377494d6c68f871d20b opw-6334168 Forward-Port-Of: odoo/enterprise#124156 Forward-Port-Of: odoo/enterprise#121852

When a kit is delivered, each component move is linked to the kit's sale order line. Pricing the delivery guide in "sale order" mode converted the component quantity into the kit's sale UoM. For a component sold in a different UoM category than the kit, this cross-category conversion raises a UserError. Steps to reproduce: - Create a BoM for a kit product with a component in a different UoM category - Create a customer with Delivery Guide Price = "From Sale Order" - Sold the kit in a sale order and deliver it - On the delivery, print the delivery guide -> error This fix makes the guide price for a component move to be "product" if the component's product is different from the related sale line product, avoiding the cross-category UoM conversion. opw-6327895 Forward-Port-Of: odoo/enterprise#124747 Forward-Port-Of: odoo/enterprise#122776

Steps to reproduce: ------------ - Install website_sale_renting_planning. - Create an employee without a working calendar. - Create a service product and enable the planning service. - Configure the product: - type -> service - plan services - assign the resource created above. - enable sync shifts and rental orders. - open the product on the website. Issue: ------------ when the resource does not have a working calendar, opening the product on the website raises a singleton traceback. Cause: -------- The _leave_intervals_batch method uses [ensure_one](https://github.com/odoo/odoo/blob/3364b3b38f7d3891d8c69b87fb8234eb9ac8e52b/addons/resource/models/resource_calendar.py#L531-L542), so a calendar record is needed. Fix: ---- - when the resource does not have a working calendar, fall back to the resource's company working calendar before calling _leave_intervals_batch. - I used the company calendar only when computing the resource's leave intervals. It is not used to display the company's non-working days. I found this issue while working on this task-5411076