Wednesday, June 24, 2026
5 changes · 17.0
Resolved issues and error corrections
This update fixes a potential issue where WhatsApp messages were being created multiple times due to retry attempts from the WhatsApp Cloud API. The change adds a check to ensure a message isn't created twice, preventing data inconsistencies and improving the reliability of WhatsApp integrations. This ensures accurate message delivery and avoids potential errors.
Original PR description
When Meta's WhatsApp Cloud API does not receive a fast acknowledgment, it retries the webhook delivery with the same msg_uid. The handler was attempting to INSERT a duplicate whatsapp.message record, violating the whatsapp_message_unique_msg_uid constraint. Fix: Add an existence check on msg_uid before creating the record to make the handler idempotent under Meta's retry pattern. opw-6055334
This update fixes a performance issue within the Odoo gevent server by ensuring it properly initializes database registries. Previously, the server wasn't setting registry sizes, leading to slower performance. This change directly addresses a technical optimization for improved server responsiveness.
Original PR description
The code to set the registry size was moved to `preload_registries`. The gevent server does not preload registries and thus does not set the registries size. Instead of moving the code again, we can preload registries in the gevent server. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update ensures that partner bank accounts are usable within all child companies, even if the partner is associated with a parent company. Previously, this functionality was limited, causing potential disruptions for users managing multiple company branches. This change improves efficiency and simplifies bank account management across the Odoo system.
Original PR description
Even when a partner has the 'company_id' filled with the parent company, his bank account should be usable in the child companies. This was done in odoo/odoo#262173 from 19.2 but we need to backport it in stable task-6309694
This change resolves an issue where SVG images uploaded by users without write access to system views were not displayed correctly. The fix ensures that SVG attachments are properly processed, preventing a technical error and ensuring knowledge articles display images as intended. This improves the user experience for adding and managing content.
Original PR description
__Current behavior before commit:__ When an SVG attachment is uploaded by a user that has no `write` access to `ir.ui.view`, its mimetype is set to `text/plain`[1] for security reasons (prevent XSS…
__Current behavior before commit:__ When an SVG attachment is uploaded by a user that has no `write` access to `ir.ui.view`, its mimetype is set to `text/plain`[1] for security reasons (prevent XSS attacks). Now because the mimetype is not in `SUPPORTED_IMAGE_MIMETYPES`, `image_src` will be set to `False`[2]. This results in a traceback when the frontend tries to call `startsWith` on `image_src`[3]. __Description of the fix:__ Add the mimetypes in `attachmentsDomain` so it only fetches the images (like it's done in the [overridden getter][4]). __Steps to reproduce the issue on runbot:__ - Make sure Marc Demo has not write access to `ir.ui.view` (remove him from the group **Website / Editor and Designer**) - Log in with Demo - Go to a knowledge article - Add a cover and upload an SVG image -> the image is not displayed - Click on **Replace cover** - Search for the name of the previous SVG file - `TypeError: attachment.image_src.startsWith is not a function` [1]: https://github.com/odoo/odoo/blob/70e8ac9c48b4e90/odoo/addons/base/models/ir_attachment.py#L378 [2]: https://github.com/odoo/odoo/blob/70e8ac9c48b4e90/addons/web_editor/models/ir_attachment.py#L41 [3]: https://github.com/odoo/odoo/blob/70e8ac9c48b4e90/addons/web_editor/static/src/components/media_dialog/image_selector.js#L222 [4]: https://github.com/odoo/odoo/blob/70e8ac9c48b4e90/addons/web_editor/static/src/components/media_dialog/image_selector.js#L108 opw-4701372
This update resolves an issue where private tasks could be incorrectly designated as parent tasks. This change ensures that private tasks remain truly private and prevents confusion or unintended hierarchical relationships within project management. This improves data integrity and simplifies project organization.
Original PR description
In this commit, we ensure that private tasks can never be selected as parent tasks. task-5119141