Friday, October 31, 2025
3 changes · 19.0
Enhancements to existing features
VoIP browser tabs now try to unregister when closed and registrations expire sooner if cleanup does not happen. This helps customers avoid hitting provider limits on active phone registrations, especially when users open multiple Odoo tabs.
Original PR description
Some providers like OnSIP allow for a limited number of registrations per user. This is a problem in Odoo because each tab opened creates a new registration for one hour. This commit mitigates the problems in two ways: - Sends an "unregister" request onbeforeunload to try to invalidate the registration upon closing the tab. - Reduces the TTL of registrations so that they get invalidated quicker in case the unregistration failed. Forward-Port-Of: odoo/enterprise#98413 Forward-Port-Of: odoo/enterprise#97963
Purchase catalog suggestions now show all recommended products on the first page when suggestions are enabled, instead of hiding some behind pagination. The change also improves performance and makes bulk adding suggestions respect the selected purchase order section.
Original PR description
Description of the issue/feature this PR addresses: Improves purchase catalog suggestions, adding a filter on products with `suggested_qty > 0` on suggestion toggle. This ensure all suggested products will be shown on the first catalog page Perf improvements on both front end (reducing number of RPCs) and backend (filtering domain as much as possible on search method). Current behavior before PR: Before, if there were more products than the paging limit, not all suggested product would be pulled to the front (couldn't order a view by a computed field.) Desired behavior after PR is merged: All suggested products are shown on first page. task#5114649 previous PR: odoo/odoo#218343 And separated all the refacto on a beanch on master: https://github.com/odoo/odoo/pull/232456 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Mass mailing now better supports older email templates during the move to Odoo 19. Users can still view legacy email content, receive clearer warnings when parts are outdated, and avoid several editing crashes.
Original PR description
This work's purpose is to prepare `mass_mailing` for the upcoming migration to Odoo 19.0. Existing mail content produced with the old editor is not upgraded, and users who end up editing such content must be informed if a snippet is not up to date. contents: - ensure that existing mail content with an obsolete mail HTML structure is properly displayed, even if the editor will not work at all, instead of showing the Theme Selector if no authorized theme is detected. - ensure that a user editing an obsolete snippet is informed and can change it to the new version - various crash fixes See commits messages for further detail. task-5134263