Friday, March 7, 2025
6 changes · 18.0
Enhancements to existing features
The Live Chat integration instructions have been revamped to make it easier to enable chat on both Odoo-hosted and custom websites. This should help businesses set up customer chat more confidently and reduce confusion during website integration.
Original PR description
Purpose of this Commit: Revamp the integration to enable Live Chat functionality on custom websites and Odoo websites. task-3751548 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now enter an exact font size directly in the editor toolbar instead of choosing only from preset options. This gives content creators more flexibility and keeps text selection stable while applying the chosen size.
Original PR description
### Description of the issue/feature this PR addresses: - The editor only provided a font size dropdown with predefined options, preventing the selection of a custom font size. ### Desired behavior after PR is merged: - A font size input field is added to toolbar using an _`iframe`_, ensuring the selection remains intact in editable area. - Clicking the font size input selects the text and displays the predefined font size dropdown. - The entered value in the font size input is applied to the selected content after a _`200ms`_ debounce. - The font size can also be selected from the dropdown. - Font size dropdown closes on Enter and Tab key press. - ArrowUp/Down moves focus to font size dropdown. task-4488396 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Website visitors will no longer see technical traceback popups when a browser-side error occurs, reducing confusion and preserving a more professional customer experience. Employees and developers can still see detailed errors in appropriate contexts such as logged-in internal use, debug mode, or testing, while visitor errors remain available in browser logs for troubleshooting.
Original PR description
Before this commit, any client error would lead to a displayed Odoo traceback dialog. While the goal is obviously to have a code without any possible traceback, visitors really should not see those.…
Before this commit, any client error would lead to a displayed Odoo
traceback dialog. While the goal is obviously to have a code without any
possible traceback, visitors really should not see those.
This is especially true in the website: if a website visitor (who has no
idea the visited website uses Odoo) gets a traceback because of a Chrome
extension, it makes no sense to display the traceback at all. It can be
justified for connected users (not portal, but base.group_user) as they
likely are employees of the company using Odoo and should be able to see
issues and report them to us (e.g. even in the Chrome extension case: so
we can make our code support the breaking extension or decide that it
cannot be used alongside Odoo).
The errors for visitors are still logged in the browser console, even
with more detailed logs in that case.
Note that we use `await user.hasGroup('base.group_user')` upon error to
be able to implement this feature. In the frontend, it actually does a
RPC call as that group information is not in the session_info. We could
add it in the session_info, but since the use case is showing an error,
the extra RPC *upon error* is fine for now.
Notice that traceback dialogs (and the related error handling that comes
with them, like preventing an error to be considered as an error and
logged in the console) are also still enabled in debug mode or during
testing tours.
task-4290643Point of Sale product searches now avoid showing a misleading notification when matching products are found. Staff will only see a message when no additional products match the search, reducing confusion during checkout.
Original PR description
Previously, the toaster notification incorrectly displayed the number of product variants instead of actual products found. This commit removes the (useless) notification when products are found and only displays "No more product found" when no results match the search. task-id: 4595775 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The invoice report action label is renamed from "PDF" to "Invoice PDF". This makes the option clearer for users when generating or accessing invoice documents.
Original PR description
Changing the name: PDF -> Invoice PDF. task-4614454
The Documents app now opens its automation rule setup with fewer background calls while keeping the same user experience. This reduces unnecessary system work and can make the transition to automation settings slightly more efficient.
Original PR description
Automation rule trigger field ids can now be deducted from a default filter domain passed in the context of an action. As a result, in the action used to direct a user of the Documents application to the Automation Rules, it is no longer necessary to pass the trigger field id to be displayed in the new rule creation form. Only the filter domain is required to achieve the same result. This makes it possible to delete an orm call without altering the implemented feature. see odoo/odoo#193576 see odoo/enterprise#75719 task-4502214