Saturday, September 5, 2026
6 changes · master
Enhancements to existing features
This update makes mobile form fields easier to scan by simplifying field styling and making required fields stand out through their labels. Phone actions such as calling, SMS, and WhatsApp are now visible as direct icon buttons instead of being hidden in a menu, reducing taps for users on smaller screens.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Dominican Republic localization now uses the updated partner identification approach while keeping existing validation rules intact. Business identifiers are stored more consistently: RNC remains on the VAT field, while Cedula is handled as an additional identifier, improving data reliability for local compliance.
Original PR description
Purpose: Adapt the current latam partner identification type to follow the additional identifiers approach introduced in PR: https://github.com/odoo/odoo/pull/259051. The validation logic involving identification types are preserved after the re-implementation. RNC now lives in the VAT and Cedula is an additional identifier. task-6129832 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Dominican Republic electronic invoicing now uses the updated partner identification approach while keeping existing validation rules intact. Business tax IDs (RNC) are handled through VAT, and personal IDs (Cedula) are managed as additional identifiers, improving consistency with the broader Odoo platform.
Original PR description
Purpose: Adapt the current latam partner identification type to follow the additional identifiers approach introduced in PR: https://github.com/odoo/odoo/pull/259051. The validation logic involving identification types are preserved after the re-implementation. RNC now lives in the VAT and Cedula is an additional identifier. task-6129832
The mail composer now better supports grouped actions in the add-action menu and chatter composer, so users see more complete and consistently ordered options. It also allows richer inline content and more flexible menu-closing behavior, improving usability for future composer actions.
Original PR description
Extend composer actions to support grouped actions, optional inline OWL components, and configurable action-list closing behavior. Grouped composer actions were previously not supported, causing actions with a `sequenceGroup` to be omitted from the "+" button. This commit adds support for grouped actions in both the "+" button and the chatter composer, ordered according to their `sequenceGroup`. Actions can also render an optional OWL component at the end of their content, aligned to the right, and `closingMode` controls whether the action list closes after an action is selected. Implementation notes: * Added `extraContentComponent` and `extraContentComponentProps`. * Added grouped action support to the "+" button and chatter composer. * Added `closingModeAsDropdown` to control action-list closing behavior. Co-authored-by: Alexandre Kühn <aku@odoo.com> task-6310817
This update aligns invoicing and payment tools with a new standalone direct debit mandate foundation. It also makes Canadian direct debit support easier to discover in settings and improves demo data for faster testing.
Original PR description
On Enterprise side, we extracted base direct debit mandate models, wizards, reports, and views from SEPA direct debit into a standalone module. This commits reflects this change on Community. task-6269131
The website forum sitemap now uses much less memory by avoiding unnecessary loading of large forum post content. This reduces the risk of sitemap failures on high-volume sites and helps search engines access the site map more reliably.
Original PR description
On odoo.com, /sitemap.xml fails dozens of times a day with a 500 `MemoryError` before finally succeeding and being cached. The primary cause is the loading of all forum posts. With this commit, we…
On odoo.com, /sitemap.xml fails dozens of times a day with a 500 `MemoryError` before finally succeeding and being cached. The primary cause is the loading of all forum posts. With this commit, we avoid fetching all fields and specifically the `content` field which is html which can contain embeded images in base64. | | Peak memory | |--------|--------| | Before | 1.7GB | | After | 610MB | ### Before <img width="2505" height="400" alt="sitemap-forum-posts-before" src="https://github.com/user-attachments/assets/0ce3aca9-52ed-46a6-ac9b-245c754a08a7" /> ### After <img width="1864" height="291" alt="image" src="https://github.com/user-attachments/assets/6686b0fc-d0ce-4dc2-b2ff-d34e37695104" /> Another approach could be to load posts in batch and free the memory between each batch. It has been measured and yield very similar results in practice. I chose this approach because it matches the future behavior in version 20.0 (see https://github.com/odoo-dev/odoo/commit/fe186b07475cf15a50558d9bdacd0599c17c39be) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#286154