Daily updates from Odoo
Thursday, August 8, 2024
12 changes · master
Resolved issues and error corrections
The Planning calendar popover now hides its footer when a user does not have permission to edit or delete a planning slot. This removes a confusing empty area and makes the interface cleaner for users with limited access rights.
Original PR description
**Current behaviour before PR:** In planning app calendar view, when user has no rights to edit or delete a record then clicking on a planning slot opens a calendar popover with empty footer. Steps to reproduce: - Set no editing rights for demo user for planning app. - Log in as demo user, open planning app. - Switch to calendar view, click on a planning slot. - Notice that calendar popover gets opened with empty footer. **Desired behaviour after PR:** Popover footer shouldn't be displayed at all if user has no rights. task-3823315
The Data Cleaning module now limits a click action to the intended view instead of applying it more broadly. This prevents unintended behavior in base model views and keeps navigation/actions consistent for users.
Original PR description
Since #64854 view_model_tree inherited an action on click that was meant only for a specific view this action has been moved to a primary inherited view. Related to task-id: 3861100
Code cleanup and technical improvements
The editor toolbar configuration was updated to follow the same structure as the command menu, making it easier to organize and extend. This helps teams add toolbar actions within existing categories more consistently across areas such as appointments, knowledge articles, and report editing.
Original PR description
The purpose of this commit is to modify the api used to define toolbar elements so that it is like the powerbox api. We're therefore going to replace toolbarGroup by toolbarCategory/toolbarCommands. These are the equivalents of powerboxCategory and powerboxCommands. Thanks to this new API, a plugin can add a command to an existing category.
Miscellaneous changes
Before this commit: When the user chooses a pickup point, the res.partner of the sale order is replaced with data from the pickup point, while the previously set customer's data is set as the partner's parent. And Sendcloud relies on a service_point_id field in its API rather than a raw address. Which causes double printing of the service point address on the label. Moreover, Sendcloud explicitly requires the customer's (and not the pickup point) address in its API. After this commit:
Original PR description
Before this commit: When the user chooses a pickup point, the res.partner of the sale order is replaced with data from the pickup point, while the previously set customer's data is set as the partner's parent. And Sendcloud relies on a service_point_id field in its API rather than a raw address. Which causes double printing of the service point address on the label. Moreover, Sendcloud explicitly requires the customer's (and not the pickup point) address in its API. After this commit: Both the service_point_id and the customer's delivery address are sent to Sendcloud. Both addresses are printed on the label correctly. opw-3977565 Forward-Port-Of: odoo/enterprise#65354
Sync between Transifex and Github has been broken lately. Some fixes need to be deployed asap. This commit manually sync pt-BR translations. See also - odoo/odoo#175298 - odoo/odoo#176035 Community: https://github.com/odoo/odoo/pull/176134 Forward-Port-Of: odoo/enterprise#68141
Original PR description
Sync between Transifex and Github has been broken lately. Some fixes need to be deployed asap. This commit manually sync pt-BR translations. See also - odoo/odoo#175298 - odoo/odoo#176035 Community: https://github.com/odoo/odoo/pull/176134 Forward-Port-Of: odoo/enterprise#68141
The default _generate_payslip method is using structure type instead of structure. Therefore it generates wrong payslip under BE structure. Forward-Port-Of: odoo/enterprise#67770
Original PR description
The default _generate_payslip method is using structure type instead of structure. Therefore it generates wrong payslip under BE structure. Forward-Port-Of: odoo/enterprise#67770
The Issue: Before this commit, the test always assumed the existence of the 'Deco Addict' partner. However, in the 'no demo' test, we run tests without demo data, so this partner does not exist. The Fix: Create the demo Partner runbot-58765 Forward-Port-Of: odoo/enterprise#67811
Original PR description
The Issue: Before this commit, the test always assumed the existence of the 'Deco Addict' partner. However, in the 'no demo' test, we run tests without demo data, so this partner does not exist. The Fix: Create the demo Partner runbot-58765 Forward-Port-Of: odoo/enterprise#67811
Version: saas-17.2 Before this commit: the warning notification for the auto plan would stay on the screen even when navigating to another page. cause: the warning notification were set to be sticky but did not properly handle removing the notification when navigate to another page. Solution: added a method to remove notifications after navigating to another page. task-4023197 Forward-Port-Of: odoo/enterprise#67870 Forward-Port-Of: odoo/enterprise#66037
Original PR description
Version: saas-17.2 Before this commit: the warning notification for the auto plan would stay on the screen even when navigating to another page. cause: the warning notification were set to be sticky but did not properly handle removing the notification when navigate to another page. Solution: added a method to remove notifications after navigating to another page. task-4023197 Forward-Port-Of: odoo/enterprise#67870 Forward-Port-Of: odoo/enterprise#66037
Version: saas-17.1 Before this commit: the notification for the auto plan would stay on the screen even when navigating to another page. cause: the notification were set to be sticky but did not properly handle removing the notification when navigate to another page. Solution: added a method to remove notifications after navigating to another page. task-4023197 Forward-Port-Of: odoo/enterprise#67852 Forward-Port-Of: odoo/enterprise#66038
Original PR description
Version: saas-17.1 Before this commit: the notification for the auto plan would stay on the screen even when navigating to another page. cause: the notification were set to be sticky but did not properly handle removing the notification when navigate to another page. Solution: added a method to remove notifications after navigating to another page. task-4023197 Forward-Port-Of: odoo/enterprise#67852 Forward-Port-Of: odoo/enterprise#66038
This PR does 2 things: - clean up pot/po files had manually adjustments done to them (see specific commit for cleanup process) - added some missing translations
Original PR description
This PR does 2 things: - clean up pot/po files had manually adjustments done to them (see specific commit for cleanup process) - added some missing translations
Before this PR: - the HSN code on products determined HSN code warnings. After this PR: - This update modifies the computation of HSN warnings based on journal items rather than products. This change enhances the accuracy of HSN code validation by focusing on the financial entries. Task ID: 4085936 Forward-Port-Of: odoo/enterprise#67685
Original PR description
Before this PR: - the HSN code on products determined HSN code warnings. After this PR: - This update modifies the computation of HSN warnings based on journal items rather than products. This change enhances the accuracy of HSN code validation by focusing on the financial entries. Task ID: 4085936 Forward-Port-Of: odoo/enterprise#67685
Steps: - Install `web_studio` - Open Studio report view from any model (e.g: Users) - Double click on any report kanban card - Crash because component is destroyed In this case: - First click create the first `ReportEditorModel` https://github.com/odoo/enterprise/blob/cebfacec4e5c6f24ed7f915da204867e39ba53ca/web_studio/static/src/client_action/report_editor/report_editor_model.js#L401 - This first instance of `ReportEditorModel` make two calls via `this.loadReportDa
Original PR description
Steps: - Install `web_studio` - Open Studio report view from any model (e.g: Users) - Double click on any report kanban card - Crash because component is destroyed In this case: - First click create…
Steps:
- Install `web_studio`
- Open Studio report view from any model (e.g: Users)
- Double click on any report kanban card
- Crash because component is destroyed
In this case:
- First click create the first `ReportEditorModel`
https://github.com/odoo/enterprise/blob/cebfacec4e5c6f24ed7f915da204867e39ba53ca/web_studio/static/src/client_action/report_editor/report_editor_model.js#L401
- This first instance of `ReportEditorModel` make two calls via `this.loadReportData` (rpc) and `this.loadModelEnv` (orm.search)
- Second click create a second instance of `ReportEditorModel` which destroys the first instance to replace it.
- The problem is that the RPC of the first instance has not yet had time to execute, so by the time it arrives the component is already destroyed, which causes the problem
This commit fixes the problem by checking the state of reportEditorModel, if it is destroyed we don't call the loaders
opw-3973038
Forward-Port-Of: odoo/enterprise#68041
Forward-Port-Of: odoo/enterprise#64876