Tuesday, October 8, 2024
15 changes
3 changes
Resolved issues and error corrections
Reloading an import records page now keeps the selected business object, so users are returned to the correct import screen instead of seeing an error or being redirected. This makes record imports more reliable when users refresh the browser or change interface settings during the process.
Original PR description
- In any APP (We would use CRM for the example); - On a multi-record view (Kanban, List, or other); - Click the action menu; - Click on “Import records” dropdown; - Reload the view (either reload the browser, or activate the debug, or change to dark mode on the user menu). Before this commit, an exception was raised, and the default multi-record view was loaded. This occurs because, the client action base import required a model (found in the context) that was lost when reloading. Now, the model is put in the query string of the URL (as active_model), in that way, when reloading, the client action base import will have the needed model. Note that, this is also the behavior of the stock TraceabilityReport client action [1]. opw-3959254 [1] : https://github.com/odoo/odoo/commit/8b3deab679bfee844ccd84c7f4f6f831921365d3
Reloading an import screen now keeps users on the same import page instead of briefly showing an error and sending them back to the list or kanban view. This preserves the user's workflow and prevents confusion during record imports.
Original PR description
- Go to CRM app - Click on the action menu --> Import records --> Import screen will appear - Reload the page a traceback will occur which will disappear quickly (you can see it in console) - It redirects you back to the kanban view which is not correct Before this commit, on reloading the import screen page a traceback was occuring which redirects back to the kanban/list view. This occurs because the ImportAction lost the current model at reload (resModel). Now, the ImportAction will update the state of action using updateActionState prop, to add the resModel to the url (as a query param), and be able to restore the full state at reload. Task-3959254 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Pivot table header menus now close again after choosing a grouping option. This prevents users from adding multiple groupings from a stale menu state, which could lead to incorrect pivot table results.
Original PR description
Before https://github.com/odoo/odoo/pull/137691, select a groupby in the dropdown of a pivot header would close the dropdown. Now the dropdown stays open and it is possible to add several row/col groupbys at the same time but the pivot model is not updated correctly because the update of the model is based on the groupId of the header for which the dropdown was opened. The simpler/best solution to that problem is to restore the previous behavior. Task ID: 3985217
1 change
Resolved issues and error corrections
Odoo Studio and related apps now avoid creating outdated view rules when customizing screens. This helps keep customizations compatible with current platform standards and reduces the risk of future display or upgrade issues.
10 changes
Resolved issues and error corrections
A spelling mistake in the invoice PDF report was corrected. This improves the professionalism and clarity of customer-facing invoice documents without changing how invoicing works.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
1 change
Resolved issues and error corrections
This fix resolves a user experience issue where the vendor dropdown menu would not close immediately when selecting an option to create a new vendor. Previously, users had to click twice to close the dropdown. Now it closes automatically on the first interaction, making the invoice extraction process smoother and more intuitive.
Original PR description
The vendor dropdown does not close when a extract box is clicked and a creation dialog opens. It would only close after the first click. In this commit the dropdown is closed straight away. Forward-Port-Of: odoo/enterprise#71039
Original PR description
*= account_asset, account_consolidation, account_disallowed_expenses_fleet, account_reports_cash_basis, appointment, documents, helpdesk, l10n_ph_reports, planning, whatsapp This PR consist of two commits: 32c4dc22980c2b723e68a68e417afe3efaebe6a6 - This commit will prevent using deprecated xpath. f01b2e58841fe247d44102055413bbbcea2586e2 - This commit will change studio xpath api such that it no longer generates custom views using deprecated xpath. Specifications: `contains(@class...` => `hasclass(...` Community PR: https://github.com/odoo/odoo/pull/174139 Task - 3820162
This fixes a visual issue in the Discuss sidebar where the selected conversation could lose its background color and show only an outline. The change restores the expected highlight, making it clearer which item is currently active without affecting the previous hover-status fix.
Original PR description
Follow-up of https://github.com/odoo/odoo/pull/182394 PR above fixed an issue where mouse-hovering IM status lead to buggy background color. This happens because the IM status requires `bg-inherit`…
Follow-up of https://github.com/odoo/odoo/pull/182394 PR above fixed an issue where mouse-hovering IM status lead to buggy background color. This happens because the IM status requires `bg-inherit` in order to determine the right background color to crop the avatar. Buttons have specific bg-color that cannot simply be overidden with `bg-inherit`, so this was defined in SCSS with higher specificity. A consequence of increasing the specificity of this rule was that it became more specific than the one for active item, so the active item in discuss sidebar had no background color but only the outline. This commit fixes the issue by increasing the stylerule specificity of active item background color, so that this is higher than the `bg-inherit`. The specific bg-inherit is still important to fix the issue in PR above. Before / After  
This fixes an issue in Point of Sale that prevented custom extensions from saving additional related sales records. Businesses using customized POS workflows can now add and store extra order details more reliably.
Original PR description
At the moment it is not possible to add new X2many relations to a model inside the `SERIALIZABLE_MODELS` list. I would like to add an One2many relation to the `pos.order` model: ```python class…
At the moment it is not possible to add new X2many relations to a model inside the `SERIALIZABLE_MODELS` list.
I would like to add an One2many relation to the `pos.order` model:
```python
class PosOrder(models.Model):
_inherit = "pos.order"
example_items = fields.One2many("example.item", "order_id")
```
```javascript
import { Base } from "@point_of_sale/app/models/related_models";
import { registry } from "@web/core/registry";
export class ExampleItem extends Base {
static pythonModel = "example.item";
setup(vals) {
super.setup(vals);
}
// ...
}
registry.category("pos_available_models").add(ExampleItem.pythonModel, ExampleItem);
```
A call to [`order.serialize`](https://github.com/abichinger/odoo/blob/f9de1eef6dd403157c0222dc75de85c8b7b59e3c/addons/point_of_sale/static/src/app/models/related_models.js#L191) throws the following error:
```
Trying to create a non serializable record example.item
```
After this PR is merged it is possible to add new models to the list of serializable models:
```javascript
import { SERIALIZABLE_MODELS } from "@point_of_sale/app/models/related_models"
SERIALIZABLE_MODELS.push("example.item")
```
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update prevents an error when importing records that use a custom property field linked to another record type but missing its target setup. It also makes import errors for numeric property fields clearer, helping users understand and correct import files faster.
Original PR description
## [FIX] core: fix traceback when importing many2one Property without comodel It is possible to create a Property field as many2one but without choosing a model. But it generates a Traceback in the import. ## [IMP] core: improve error message for import of Properties int/float.
This fix adds a standard identification header when Odoo hardware drivers open websocket connections. It helps prevent legitimate hardware-related connections from being blocked by proxy firewalls, improving reliability in protected network environments.
Original PR description
**This is a forward-port of a fix that was manually committed to saas-17.4 during the OXP:** `websocket.WebSocketApp` doesn't set any fingerprint header, like no user-agent or origin, ... It can lead to issues when using a proxy firewall, such as HAProxy, as it could lead to the fingerpint to be 00000000-00000000-00000000-00000000, which can be seen as not legitimate, and the requests to be rejected for that reason. By setting a user-agent, we overcome this limitation 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
Users who end a call while camera or screen sharing permission is still pending will no longer see an error after responding to the permission prompt. This improves reliability in Odoo Discuss calls by safely handling cases where the call is no longer active.
Original PR description
Fixed an issue where an error is thrown if the call is ended before accepting/rejecting the camera or screen access. After ending the call, accepting or rejecting access would trigger an error due to the absence of a check for whether the call is still active. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update fixes visual issues in website product carousels so product images and text display correctly. It also removes an unwanted mobile scrollbar caused by carousel arrows, improving the shopping experience on smaller screens.
Original PR description
This commit fixes two layout issues: 1. In the dynamic products snippet: using the layout "centered", the image was overlapping the text of the card due to having no height set for the image. 2. On…
This commit fixes two layout issues: 1. In the dynamic products snippet: using the layout "centered", the image was overlapping the text of the card due to having no height set for the image. 2. On the dynamic carousel snippet: on mobile, a scrollbar was appearing because of the arrow buttons. task-4215589 | | Before | After | |--------|--------|--------| | Image issue |  | <img width="1394" alt="Capture d’écran 2024-10-08 à 09 01 46" src="https://github.com/user-attachments/assets/ba710372-dd08-4854-8cfd-c8c999197dca"> | | Scroll issue |  | <img width="447" alt="Capture d’écran 2024-10-08 à 09 02 25" src="https://github.com/user-attachments/assets/415aa9f3-94fd-45e1-9743-ad1ac0a3a205"> | --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change makes an automated live chat test more consistent by ensuring the page is focused before a keyboard shortcut is used. It reduces random test failures, helping maintain confidence in the live chat functionality without changing the user experience.
Original PR description
In this commit, we click on element to set the focus on window before press ctrl+k. This fix an undeterministic error. 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
This change fixes the setup for web development tooling so it works correctly with Odoo 18 and future versions. It helps teams maintain code quality checks consistently before changes are submitted, reducing avoidable issues in development.
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
Fixed a display issue where section headers were hidden when customers grouped helpdesk tickets by sales order in the portal. This makes grouped ticket lists easier to read and navigate for portal users.
Original PR description
…ing by SO in portal When grouping by SO in the helpdesk ticket portal list view, the group headers were invisible. That was cause by changing the groupby options from ``sale_line_id`` to ``sale_order_id`` without changing the condition in the template that would draw the group headers. In this commit we change the condition to ``groupby == 'sale_order_id``. task-4213896