Daily updates from Odoo
Tuesday, May 27, 2025
18 changes
4 changes
Resolved issues and error corrections
This update corrects a formatting problem in the VoIP contact information display. It helps prevent incorrect or confusing text from appearing when users view call contact details.
This change fixes an unreliable automated test in Web Studio navigation. It helps reduce false failures in the release process, making validation more dependable without changing the user experience.
Original PR description
runbot-error-224154
The VoIP softphone now shows a pause icon when an active call is placed on hold. This gives users clearer visual feedback in both the softphone top bar and systray, reducing confusion during calls.
Original PR description
This commit modifies the icons displayed in the softphone interface to provide clearer feedback on call status. Now, when the ongoing call is on hold, the user will see a pause icon in the top bar and the systray item.
This update corrects how Mexican e-commerce checkout handles tax ID validation after a related platform change. It helps prevent validation errors during website sales for customers entering VAT or tax details.
Original PR description
In PR https://github.com/odoo/enterprise/pull/75974, it was forgotten that the return value for _run_vat_checks had changed.
14 changes
Resolved issues and error corrections
Point of Sale session reports now correctly show counted amounts when bank payments include refunds or other negative transactions. This prevents mismatched payment totals and gives businesses more reliable end-of-session reporting.
Original PR description
Before this commit, if a session included negative bank payments resulting in a negative total, the session report displayed incorrect counted amounts and mismatched values for the bank payment method. opw-4714251 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents pivot report exports from crashing when a numeric field is used in the row grouping. Business users can now download CSV or Excel exports from affected reports reliably, including reports such as Sales Analysis.
Original PR description
Steps to reproduce: - Go to any Report (Ex: Sale Analysis) - Switch to the pivot view - Add on y-column any **int** field - Download as csv Tracebrack is thrown, because the controller tries to concat int to str in the csv generated file. opw-4762807 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
Invoice PDFs now handle unusually long tax group names without pushing the total amount off the page. This keeps invoice totals readable and avoids layout problems when printing or sharing invoices.
Original PR description
**Issue** When the tax group name is too long, it pushes the total amount off the page in the invoice PDF, making the amount unreadable. **Steps to Reproduce** 1. Install the Accounting module. 2. Go to Taxes. 3. Select a tax and open Advanced Options. 4. Set a very long name for the tax group. 5. Go to Accounting > Customers > Invoices. 6. Create and confirm an invoice using the tax with the long group name. 7. Print the invoice PDF and observe the layout issue. **Root Cause** The text-nowrap CSS class prevents the tax group name from wrapping, causing it to expand the table cell width and push the amount outside the page boundary. **Fix** Remove the text-nowrap class and apply a maximum width to the <td> element, allowing the tax group name to wrap or truncate properly without overlapping or pushing the total amount off the page. Opw-4795941 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Calendar popovers now display each task property with its own label instead of reusing the general container label. This makes custom property information clearer and consistent with how standard fields are shown.
Original PR description
Backport of 18affd81cbdd321e428b729602f91dc06988929f Steps: ------ * Add properties (displayed on card) to a task of a project * Open the card view of the task in the calendar view of the project Previously, the calendar popover displayed property field values using the label of the container field. This commit updates the behavior to display each property field with its respective label, ensuring consistency with the appearance of standard fields. opw-4767059 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an issue in the homeworking calendar where changing the time format could trigger an error when moving between calendar views in debug mode. This makes calendar navigation more reliable for users who adjust time display settings.
Original PR description
**Issue**:
an error is thrown in debug mode when switching between calendar views ("year", "week", etc.) after changing the time format.
**Steps to reproduce:**
- ensure hr_homeworking_calendar is installed
- activate debug mode
- Calendar > change the time format
opw-4684831The Point of Sale mobile screen now keeps the search dropdown visible above the orders list. This fixes an issue that made searching orders difficult or unusable on smaller screens.
Original PR description
The search field dropdown was being rendered behind the orders list in mobile view, making it unusable. This commit adds a higher z-index to the search field dropdown to ensure it's rendered above the orders list. opw-4654710 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Users can now add a Pricer Sales Pricelist while creating a product variant before it has been saved. This prevents an error that interrupted product setup and improves the reliability of the product form workflow.
Original PR description
An error occurs when a user attempts to set the **Pricer Sales Pricelist** on a product variant that has not yet been saved. **Steps to reproduce:** - Install the `pos_pricer` module. - Open the form view of **Product Variants**. - Without saving the record, try to add a **Pricer Sales Pricelist**. - Observe the error. **Error:** `KeyError: False` **Cause:** When the product variant is unsaved, `product.id` is `False`, leading to a `KeyError` at [1], because `False` is not a valid key in the result of method `_compute_price_rule()`. [1] - https://github.com/odoo/odoo/blob/d352cfcfe0fe8c161392f3c39ea3e64b7c98bd69/addons/product/models/product_pricelist.py#L140 This commit ensures that users can add a 'Pricer Sales Pricelist' to a product variant, even before saving it. Sentry - 6598605111
Website editors can now delete all text from a button, save the page, and still edit that button later. This prevents buttons such as “Apply Now!” on job pages from becoming inaccessible after content cleanup.
Original PR description
Problem: When the "Apply Now!" button text is deleted (e.g., on `/jobs/experienced-developer-4`), it becomes uneditable after saving. Cause: When all text is deleted, a zero-width space (ZWS) is…
Problem: When the "Apply Now!" button text is deleted (e.g., on `/jobs/experienced-developer-4`), it becomes uneditable after saving. Cause: When all text is deleted, a zero-width space (ZWS) is inserted with the `data-oe-zws-empty-inline` attribute. This is removed during the save process. Since the button has `data-oe-field="arch"` and becomes empty, it is excluded from editable areas in `_getContentEditableAreas`, making it uneditable after reload. This worked in 17.0 due to inherited `display: block` from a floated parent, which added a `<br>` in empty blocks. Solution: Preserve the ZWS for inline empty elements with `data-oe-field="arch"`, ensuring the element remains editable after save. Steps to reproduce: 1. Navigate to `/jobs/experienced-developer-4`. 2. Open the web editor. 3. Delete the text inside the "Apply Now!" button. 4. Save the page. 5. Reopen the web editor. → The button is no longer editable. opw-4737255 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue in the HTML editor where pressing Tab inside a table header cell could cause an error. Users can now navigate tables with header cells more reliably without interrupting their editing work.
Original PR description
Problem: `shiftCursorToTableCell` is not considering being inside `th` which causes traceback as `currentTd` will be null. Solution: Include `th` in the selector alongside `td` to ensure proper detection and navigation. Steps to reproduce: - Copy and paste in the editor any table that has `th`. - Put selection inside a `th` element. - Press "TAB". → Traceback occurs. opw-4808751 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Document tags can now display the custom tooltip text set by users instead of always showing the tag name. This makes tag details clearer when hovering over tags in document views and avoids misleading or incomplete hover text.
Original PR description
Before this commit --- The tooltip shown on hover over document tags was always the tag name. This ignored the "Tooltip" field available on document tags. (The tooltip was not fetched.) After this commit --- We fetch and display the custom tooltip defined in the "Tooltip" field of the tag. Reproduce --- - install documents - add "Tooltip" string to a TAG in Documents/Configuration/Tags - open documents kanban view and over onto the TAG - BUG: tag name is apearing on hover (instead of tooltip string) opw-4567814 A sibling https://github.com/odoo/enterprise/pull/79496 updating xml and utilizing this change
This fix makes list column width handling more reliable, especially for right-to-left layouts and custom integrations that may not pass newer options. It helps prevent display issues or errors in list views while preserving compatibility for existing custom code.
Original PR description
This commit is a followup of [1]. It does two things: 1) it fixes the "rtl" check that was forwardported from 16.0, where the callback was defined in the renderer and for which `this` was…
This commit is a followup of [1]. It does two things: 1) it fixes the "rtl" check that was forwardported from 16.0, where the callback was defined in the renderer and for which `this` was unambiguously the renderer. As of 18.0, the code was moved to an hook, so using `this.isRTL` worked, but kind of by chance. This commit removes the ambiguity and makes the code a bit more robust. 2) using the newly added parameters `options` in `listViewWidths` callbacks looked harmless. Indeed, it causes no issue in standard odoo. However, as reported in [2], there is a world where `options` is undefined. I couldn't really find how, as it works fine even with the suggested culprit [3]. So this commit simply adds a fallback, which makes sense in stable in case there would be custom code calling those `listViewWidths` functions without options. In master though, we expect from people to adapt their code with respect to this change. [1] https://github.com/odoo/odoo/pull/210584 [2] https://github.com/odoo/odoo/issues/211243 [3] https://github.com/OCA/web/tree/18.0/web_remember_tree_column_width closes #211243 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
Updates internal test data so tax group receivable and payable accounts follow the latest accounting validation rules. This helps ensure accounting, tax report, localization, and subscription tests continue to reflect compliant account setup without changing customer-facing functionality.
Original PR description
In the related community commit, we added a constraint that requires the Tax Receivable and Tax Payable accounts on tax groups to be a Receivable or Payable account, be reconcilable and set to Non Trade. In this commit we adapt the current tests that use accounts on tax groups to have their accounts comply to the new constraint. [task-3763030](https://www.odoo.com/odoo/project.task/3763030) Related to https://github.com/odoo/odoo/pull/201249
This fix prevents an error in Mexican electronic invoicing for Point of Sale when a cashier selects a company contact on the payment screen. Orders are now only marked for invoicing once the required customer information is complete, reducing checkout interruptions.
Original PR description
Before this commit, selecting a contact of type "company" on the payment screen would result in the following error: `TypeError: Cannot read properties of undefined (reading 'name')` This occurred because selecting a company contact automatically set the order to be invoiced, even if the required fields were not filled in. To prevent this error, the process now checks that all necessary fields are completed before setting the order to invoice. opw-4773831
Document tags now display the custom tooltip text configured for them when users hover over a tag, instead of always showing the tag name. This makes tag guidance clearer for users and ensures the existing Tooltip field works as intended across document-related views.
Original PR description
[FIX] documents: display tag tooltip on hover when possible Before this commit, the tooltip shown on hover over document tags was always the tag name. This ignored the "Tooltip" field available on document tags. After this commit, the system correctly fetches and displays the custom tooltip defined in the "Tooltip" field of the tag. Reproduce --- - install documents - add "Tooltip" string to a TAG in Documents/Configuration/Tags - open documents kanban view and over onto the TAG - BUG: tag name is apearing on hover (instead of tooltip string) opw-4567814 # (older) sibling PR: https://github.com/odoo/odoo/pull/210147