Wednesday, June 4, 2025
15 changes
1 change
Resolved issues and error corrections
Fixed a display issue in Knowledge where article content could shrink to fit its contents on narrower screens instead of using the available space. This improves readability and layout consistency for users working on tablets or smaller browser windows.
Original PR description
Prior to this commit, passing below the medium bootstrap threshold (992px) in the Knowledge form view would make it so the body width would fit its content instead of taking all the available space. The issue was introduced by the removal of some media queries in [this commit]. [this commit]: https://github.com/odoo/enterprise/commit/3f58d0e6f8f9958a3fd6fbba47d11c3d376cd51f task-4836314
3 changes
Resolved issues and error corrections
After a user signs a document, closing the confirmation popup now sends them back to the correct signed-document page instead of the general portal page. This avoids confusion when viewing completed signature requests, especially in cases where internal request identifiers differ.
Original PR description
### Before this commit: When closing the popup after signing a document, it redirects to the `/my` page instead of `/my/signature/<id>`. It only happens when the request's id is out-of-sync with the request item's id. ### After this commit: Correctly use the `sign.request.item`'s id, as expected from the `/my/signature` route.
11 changes
Resolved issues and error corrections
Fixes an error that occurred when website editors clicked the publish button on a user profile page. This restores the expected ability to publish or unpublish profiles and may also prevent similar publishing errors in related website features.
Original PR description
Currently, an error is encountered when clicking on the publish button in the profile page in the website view. **Steps to Reproduce:** - Install `website_profile` module. - Navigate to the user's…
Opening a report in Studio that has no linked view now shows a controlled user-facing error instead of causing a system traceback. This prevents confusing crashes for users managing reports and improves reliability in the report editor.
Original PR description
Here, when we try to open a report that is not linked to view, a traceback appears. **Steps to reproduce:** - Install the `stock` and `web_studio` modules. - Navigate to `Settings > Technical >…
Here, when we try to open a report that is not linked to view, a traceback appears. **Steps to reproduce:** - Install the `stock` and `web_studio` modules. - Navigate to `Settings > Technical > Actions > Reports`. - Create a new report (e.g; **Model Name** = product.template, **Template Name** = product.report_test). - Open the report in the web editor. **Error:** `ValueError: External ID not found in the system: studio_customization.studio_report_docume_product_label` In this case, if no view is defined for the report, the system attempts to retrieve the related view from [1]. However, since the view does not exist, it raises a **ValueError**. [1] - https://github.com/odoo/odoo/blob/924aa8aa2abe7765d2d605dc7643d1102e056fd6/odoo/addons/base/models/ir_ui_view.py#L2151 This behavior is already handled in **version 16.0** by [2] with a controlled exception. This commit adopts the same approach by raising **UserError** when no view is defined for a report, preventing an unhandled exception. [2] - https://github.com/odoo/enterprise/blob/511781a6bfb52c88892a54e43133b90ddfddbe22/web_studio/controllers/report.py#L137-L143 Related Community PR: https://github.com/odoo/odoo/pull/208806 Sentry - 5715762959, 6303192517, 6577830303, 6577830303, 6577830303, 6303950186
This update fixes several small Shop Floor issues so manufacturing and work order cards show the right names, work centers, product details, and company-related information. It also removes an unused employee popup component, reducing clutter without changing current workflows.
Original PR description
This PR fixes small issues regarding changes done here: odoo/enterprise#83203 and removes dead code.
Currently, an error is encountered when clicking on the publish button in the profile page in the website view. **Steps to Reproduce:** - Install `website_profile` module. - Navigate to the user's profile page.`(/profile/user/2)` - Click on the publish button in the editor view. **Note:** - The error is generic and could be generated via different website modules as well (e.g, website_forum). **Error:** AttributeError: The method `res.users.website_publish_button` does not exist. **Root Cause:** - since [1] we are using `website_publish_button` method to publish/unpublish records, however, `res.users` model **inherits** the publishing fields from its `res.partner`, but not its related publishing methods [1]- https://github.com/odoo/odoo/commit/97d00377de0c32e919587a98210679376e27ecc4 **Solution:** - This commit ensures that the `res.users` model can handle publish/unpublish calls by adding the `website_publish_button` method to `res.users`. sentry-6356507720
This fixes a problem where users could not extend a text selection while scrolling through long editable content. The editor now avoids forcing the page back to the current selection when that selection is already visible, making selection smoother and preventing flickering.
Original PR description
**Current behaviour before PR:** Steps to reproduce: - Have a long content so that editable content becomes scrollable. - Scroll to the bottom of content. - Select the last line of text. - Try extending selection by scrolling through mouse. - Selection is not extending and it flickers. The issue happens because `scrollToSelection` function is invoked on selectionchange and forcefully scrolls to the selected content. As result, selection is not extending when scrolling. **Desired behaviour after PR is merged:** Now, `scrollToSelection` doesn't scroll to the selection if selection range is is within visible viewport area. As result, selection can be extended by scrolling. task-4756869 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an editor display issue where restoring a deleted embedded video with undo could leave the command hint and action buttons on different lines. The editor now waits until embedded content is fully mounted before repositioning these controls, keeping the writing experience clean and predictable.
Original PR description
Steps to Reproduce: 1. Insert a video using the /video command. 2. Place the cursor on the new line below the video. 3. Press Backspace to delete the video. 4. Press Ctrl + Z to undo the deletion. 5.…
Steps to Reproduce: 1. Insert a video using the /video command. 2. Place the cursor on the new line below the video. 3. Press Backspace to delete the video. 4. Press Ctrl + Z to undo the deletion. 5. Observe that the `Type / for commands` hint and the magic buttons appear misaligned on different lines. Current behavior before PR: - After undoing video removal, the video block is remounted and at that time powerButtons position updates but iframe loads after that. - PowerButtons update runs too early when video height is zero, causing misalignment. Desired behavior after PR is merged: - Introduce `post_mount_component_handlers` dispatched after each component mount completes. - PowerButtonsPlugin uses this to update positions after the video and iframe are fully ready. - Ensures powerButtons and hint paragraph stay correctly aligned after undo restores video. task-4832484 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoice screens in Spanish now display the outstanding credits section correctly, even when browser zoom or longer translated text is used. This prevents important credit information from being cut off and improves readability for Accounting users.
Original PR description
**Issue** When viewing an invoice in Spanish, the "Outstanding credits" section may overflow or be cut off on the right side. **Steps to Reproduce** 1. Install the Accounting module. 2. Switch the…
**Issue** When viewing an invoice in Spanish, the "Outstanding credits" section may overflow or be cut off on the right side. **Steps to Reproduce** 1. Install the Accounting module. 2. Switch the user language to Spanish. 3. Navigate to Contabilidad > Clientes > Facturas. 4. Open an invoice that has outstanding credits. 5. Set the browser zoom to 125%. 6. Observe that the outstanding credits widget content is truncated or overflows its container. **Root Cause** The field `invoice_outstanding_credits_debits_widget` was placed directly in the form without a layout container, causing it to misalign and overflow in cases where translated text or zoom scaling increased its width. The lack of a proper responsive layout prevented it from adapting gracefully. **Fix** Wrapped the field inside a `<group>` element with class `oe_subtotal_footer px-4` to ensure it inherits consistent padding and alignment with other form elements. This provides a flexible layout that handles longer text and browser zoom correctly, maintaining readability and visual consistency. opw-4716266 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Printing invoices with long Terms & Conditions text no longer creates an unwanted horizontal scrollbar in that section. This keeps invoice documents cleaner and easier to read for customers and internal users.
Original PR description
<b>Steps to reproduce:</b> 1. Go to Invoices > Create new 2. Add a long string in Terms & Conditions > Click "Print" <b>Issue:</b> - In Invoices, a horizontal scrollbar appears in the Terms & Conditions section. <b>Cause:</b> - The class `overflow-auto` was applied to the container, which triggers scrollbar when content overflows. <b>Solution:</b> - Replace `overflow-auto` with `overflow-hidden` to avoid overflow. <b>opw-4776919</b> Image of issue:  
This fix allows businesses to remove a Point of Sale manager from advanced access rights when needed. It helps keep employee permissions accurate and avoids managers retaining elevated POS access after their role changes.
Original PR description
Before this commit, it wasn't possible to remove a POS manager from the advanced access rights. opw-4774770 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The marketing card section added to robots.txt will now stay in the required standard format regardless of the website language. This prevents search engine crawler instructions from being translated into invalid text and cleans up the file formatting.
Original PR description
Versions -------- - 18.0+ Steps ----- 1. Set up a site in Dutch; 2. go to `/nl/robots.txt` Issue ----- File shows "Toestaan: /kaarten/", which is not a valid string for a robots.txt file. This section is also oddly indented. Cause ----- Inserting the additional text in a template override does not inherit the parent view's `t-translation="off"` setting. Solution -------- Add `t-translation="off"` to the template override, and ensure there's no indentation when generating the file. opw-4815818
This fix ensures sales orders that begin with a section or note are handled correctly in Point of Sale. It prevents incorrect or missing lot information, reducing errors when processing linked sale orders.
Original PR description
Before this commit, if the first line in a sale order was a Section or Note, it would not be included in the `read_converted` result. As a result, using the index to access the corresponding data and read `lot_names` could fail, leading to missing or incorrect `lot_names`. opw-4816447 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents imports from crashing when a record contains an empty selection field inherited from a parent record. Businesses can now export and re-import affected records reliably without manual data cleanup.
Original PR description
If the selection property of a parent record is NULL, and the record is exported and then re-imported, a TypeError occurs. This is resolved by returning an empty dictionary during import whenever the selection property's value is NULL in the parent record. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: opw-4670210 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a test issue that could occur when certain accounting apps were installed without the Accountant app. It helps keep automated quality checks reliable across different installation combinations, reducing false failures during development and release validation.
Original PR description
If account and account_accountant are installed but not accountant the test test_change_payment_state_valid will fail This occurs because the valid payment states for batch payments change when accountant is installed runbot-226305
Closing a POS session with customer account payments now ignores cancelled or unposted accounting entries during reconciliation. This prevents session closing failures caused by invalid entries and helps keep payment processing smoother.
Original PR description
Before this commit, closing a session containing a customer account payment would attempt to reconcile all move lines related to the customer with the same account. However, some of these lines could belong to cancelled journal entries, leading to an error. opw-4843923