Odoo Changelog — 2026-04-19

Sunday, April 19, 2026

4 changes · saas-19.1

Bug Fixes(4)

Resolved issues and error corrections

[FIX] survey: use recipient lang for invitations in mixed-lang batches

Coresaas-19.1surveyMEDIUM

Survey invitation emails are now sent in the correct language for each person, even when a batch includes recipients with different language preferences. This avoids confusion and helps ensure a better experience for international audiences.

Original PR description

When sending survey invitations to a group of recipients with different language preferences, some recipients would receive the invitation in the incorrect language.

### Steps to reproduce

1. Install the "Surveys" module and activate a second language (e.g., Dutch).
2. Create a survey and ensure its invitation template has translations for both languages.
3. Create two contacts: one with English as their language and another with Dutch.
4. On the survey, click "Share" and add both contacts as recipients.
5. Send the invitations.
6. The contact with Dutch preferred language receives the email in English.

### Cause

By default, the wizard uses a single language for every email in a batch. While it can switch this language if everyone in the group speaks the same tongue, it fails to do so for mixed-language groups. Adding compute_lang=True fixes this by telling the system to look up and use the correct language for each recipient one by one.

opw-5868581

Forward-Port-Of: odoo/odoo#255677
Forward-Port-Of: odoo/odoo#246778

#survey#email#translations#language#invitations

[FIX] website_crm_partner_assign: use child_of for chatter access check

PR #259958

Coresaas-19.1website_crm_partner_assignMEDIUM

This change fixes an error that could prevent portal users from posting messages on opportunities when the opportunity was assigned to their company contact instead of their exact person record. It aligns the access check with existing portal rules, so related contacts can now use chatter messaging without hitting a 404 error.

Original PR description

Steps to reproduce:
1) Create a partner contact form
2) Create a child contact for this partner, and grant it portal access
3) Create a customer contact form
4) Create an opportunity for the customer, with the previously created partner as "assigned partner"
5) Connect on the portal account of the partner
6) Send a message from an opportunity

When a company partner is assigned to an opportunity (instead of a specific contact person), posting a message in the chatter raised a 404 NotFound error.

_mail_get_operation_for_mail_message_operation was using a strict equality check (partner_assigned_id == user.partner_id), which fails when the assigned partner is the company and the user is a child contact under it.

Replace the equality check with a child_of domain filter on commercial_partner_id, consistent with the logic already used in _assert_portal_write_access.

Forward-Port-Of: odoo/odoo#252854

#portal#chatter#access#crm#opportunity

[FIX] payment_stripe: avoid refund payment for uncaptured transactions

PR #260019

Coresaas-19.1payment_stripeMEDIUM

This fix prevents Odoo from creating a refund entry when a Stripe payment is voided before it has actually been captured. It ensures the accounting records match the real payment status, avoiding confusing or incorrect refund entries.

Original PR description

When an uncaptured Stripe payment is voided, the system will still
generate the refund payment entry.

Steps to reproduce:
- Configure the Stripe payment provider
  - enable "Capture Manually"
  - generate webhook
- Create a sales order
- Generate a payment link and pay with Card
- Back to the SO, click 'Void Transaction'

Issue:
Refund payment entry will be created even if no payment has been
collected for the transaction.

opw-5866924

Forward-Port-Of: odoo/odoo#259945
Forward-Port-Of: odoo/odoo#259230

#stripe#refund#payment#void#capture manually

[FIX] sale_subscription: invoice not automatically reconciled

PR #114223

Enterprisesaas-19.1sale_subscriptionMEDIUM

Fixed an issue where subscription payments could be recorded successfully but the related invoice still showed as unpaid. This ensures invoices are automatically reconciled after payment, so users no longer need to manually fix the payment status.

Original PR description

Currently, when a subscription payment is processed through a provider configured to use as outstanding account the bank default account, the resulting invoice may remain in an 'open' state even…

Currently, when a subscription payment is processed through a provider
configured to use as outstanding account the bank default account,
the resulting invoice may remain in an 'open' state even though
the payment transaction is 'done'.
This type of configuration is usually done when users want to skip
the bank reconciliation process, and just create payments without
the need to reconcile the payments with transactions.

Steps to reproduce:
- In Settings, under Sales > Invoicing, disable Automatic Invoice
- Activate demo payment method
- In the main Bank account add the default account as outstanding
  account for demo payment method.
- Create a sales order with a subscription product
- Open Preview
- Pay
- Go back to the sales order and open the created invoice

Issue:
The invoice is created and the payment is registered, but
the invoice remains 'Not Paid'.

Analysis:
The invoice and the payment move lines are not automatically reconciled
during the post-processing of the transaction, leaving the invoice
unbalanced.

opw-5869303

Forward-Port-Of: odoo/enterprise#110656

#subscription#invoice#payment#reconciliation

When sending survey invitations to a group of recipients with different language preferences, some recipients would receive the invitation in the incorrect language. ### Steps to reproduce 1. Install the "Surveys" module and activate a second language (e.g., Dutch). 2. Create a survey and ensure its invitation template has translations for both languages. 3. Create two contacts: one with English as their language and another with Dutch. 4. On the survey, click "Share" and add both contacts as recipients. 5. Send the invitations. 6. The contact with Dutch preferred language receives the email in English. ### Cause By default, the wizard uses a single language for every email in a batch. While it can switch this language if everyone in the group speaks the same tongue, it fails to do so for mixed-language groups. Adding compute_lang=True fixes this by telling the system to look up and use the correct language for each recipient one by one. opw-5868581 Forward-Port-Of: odoo/odoo#255677 Forward-Port-Of: odoo/odoo#246778

Steps to reproduce: 1) Create a partner contact form 2) Create a child contact for this partner, and grant it portal access 3) Create a customer contact form 4) Create an opportunity for the customer, with the previously created partner as "assigned partner" 5) Connect on the portal account of the partner 6) Send a message from an opportunity When a company partner is assigned to an opportunity (instead of a specific contact person), posting a message in the chatter raised a 404 NotFound error. _mail_get_operation_for_mail_message_operation was using a strict equality check (partner_assigned_id == user.partner_id), which fails when the assigned partner is the company and the user is a child contact under it. Replace the equality check with a child_of domain filter on commercial_partner_id, consistent with the logic already used in _assert_portal_write_access. Forward-Port-Of: odoo/odoo#252854

When an uncaptured Stripe payment is voided, the system will still generate the refund payment entry. Steps to reproduce: - Configure the Stripe payment provider - enable "Capture Manually" - generate webhook - Create a sales order - Generate a payment link and pay with Card - Back to the SO, click 'Void Transaction' Issue: Refund payment entry will be created even if no payment has been collected for the transaction. opw-5866924 Forward-Port-Of: odoo/odoo#259945 Forward-Port-Of: odoo/odoo#259230

Currently, when a subscription payment is processed through a provider configured to use as outstanding account the bank default account, the resulting invoice may remain in an 'open' state even though the payment transaction is 'done'. This type of configuration is usually done when users want to skip the bank reconciliation process, and just create payments without the need to reconcile the payments with transactions. Steps to reproduce: - In Settings, under Sales > Invoicing, disable Automatic Invoice - Activate demo payment method - In the main Bank account add the default account as outstanding account for demo payment method. - Create a sales order with a subscription product - Open Preview - Pay - Go back to the sales order and open the created invoice Issue: The invoice is created and the payment is registered, but the invoice remains 'Not Paid'. Analysis: The invoice and the payment move lines are not automatically reconciled during the post-processing of the transaction, leaving the invoice unbalanced. opw-5869303 Forward-Port-Of: odoo/enterprise#110656