Tuesday, November 19, 2024
8 changes · 17.0
Enhancements to existing features
This update adds logging for websocket statistics, giving teams better visibility into real-time connection activity. It helps administrators monitor usage and investigate operational issues more easily without changing the user experience.
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
Resolved issues and error corrections
Pager navigation buttons now keep their rounded corners in the correct places when using right-to-left languages. This improves the visual consistency of the interface for users working in languages such as Arabic or Hebrew.
Original PR description
This PR fixes an issue about the pager buttons having a wrong `border-radius` in RTL languages. Prior to this PR, the icons were defined at the button level. On top of being unusual, this had a…
This PR fixes an issue about the pager buttons having a wrong `border-radius` in RTL languages. Prior to this PR, the icons were defined at the button level. On top of being unusual, this had a side-effect. In RTL languages, we use a CSS `transform: rotate(180deg);` on our directional icons,in order to flip their direction and match the RTL or LTR. While this works totally fine, having the icon sets on the button directly means the whole button will be flipped, meaning the border-radius will be inverted. To prevent this behaviour, we simply need to use a `<i/>` tag for both icons, which will allow them to be flipped without affecting the button design. | 17.0 | This PR | |--------|--------| | <img width="159" alt="image" src="https://github.com/user-attachments/assets/2afc13b3-0b4b-4baf-a306-2196a3c83867"> | <img width="159" alt="image" src="https://github.com/user-attachments/assets/a405e167-6a0f-4a49-a15d-4e36735d95f5"> | task-4345233 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
The function _validate_accounting_entries is notorious for not using proper batching which results in a lot of SQL queries. Originally, it had to iterate individual svls and invoke functions in an unbatched way, even when all svls belonged to the same product. The changes here are to use as much batching as possible and enforcing the use of prefetch_ids to lower the total number of queries. Benchmarks: |no. queries before| no. queries after | total time before | total time after| |-----|-
Original PR description
The function _validate_accounting_entries is notorious for not using proper batching which results in a lot of SQL queries. Originally, it had to iterate individual svls and invoke functions in an unbatched way, even when all svls belonged to the same product. The changes here are to use as much batching as possible and enforcing the use of prefetch_ids to lower the total number of queries. Benchmarks: |no. queries before| no. queries after | total time before | total time after| |-----|-----|------|-----| |95991|83352|1.59 min|1.48 min| opw-4283347 opw-4096108 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186434
This fix stops project analytic information from being applied to bill payment term lines created through Project Updates. It helps keep accounting reports accurate by ensuring only the appropriate purchase lines carry project tracking details.
Original PR description
When confirming a BILL via Project's Updates, the generated payment terms line will have the analytic account of the project assigned Version: 17.0+ Steps to reproduce: - Have a project (i.e. Renovations) - Create a Purchase Order - Add on the line the analytic account of the project - Go to Projects Kanban view - Open Project 3 dots menu > Reporting > Project Updates - Open the created PO, Create Bill Issue: Analytic account will be assigned to the payment term line opw-4193509
This update corrects a technical issue where a specific view was incorrectly prioritized, leading to unexpected display behavior and a traceback error. The fix ensures the correct `stock.move.line` form view is consistently displayed, improving the stability and reliability of the stock barcode picking process. This resolves a minor bug impacting user experience.
Original PR description
The view `stock_move_line_product_selector_inherit` had no priority set and so had the default one, which means when we want to display the `stock.move.line` form view, it could happen this one is displayed instead, which is not wanted and causes traceback. task-4329041 Forward-Port-Of: odoo/enterprise#73893
This update fixes a technical issue where certain strings within the Odoo Enterprise modules (mrp_workorder, quality_iot) were not properly prepared for translation. The changes ensure all strings are translatable, improving localization support and allowing for broader language options. This resolves a potential barrier to internationalization and enhances the user experience for global customers.
Original PR description
Some strings weren't translatable/were missing from the pot files to be translated. Since these strings weren't translatable (i.e. no lost work), they have been updated to be more grammatically correct + understandable where useful. opw-4321317
This update makes it easier for users to view Google Slides directly within Odoo's work order module. Previously, a flawed feature was used for maintenance, and this change expands its availability to all users. This improves workflow efficiency by allowing for seamless integration of presentation materials.
Original PR description
As the previous 'embed_viewer' was also (wrongly) used in maintenance, make it available globally.
## Problem: When generating sorting URLs, the `post` dictionary only contains a single selected attribute. This is due to `request.params` only passing the first `attrib` parameter during dispatch, even though there can be multiple. ## Solution: Modify the `post` dictionary to store attributes as a list before passing it to the `_shop_get_query_url_kwargs` method. This ensures that all selected attributes are preserved and properly passed to the `keep` query parameters. ## Steps to repro
Original PR description
## Problem: When generating sorting URLs, the `post` dictionary only contains a single selected attribute. This is due to `request.params` only passing the first `attrib` parameter during dispatch, even though there can be multiple. ## Solution: Modify the `post` dictionary to store attributes as a list before passing it to the `_shop_get_query_url_kwargs` method. This ensures that all selected attributes are preserved and properly passed to the `keep` query parameters. ## Steps to reproduce: - Go to `/shop`. - Apply multiple attribute filters (ensure more than one attribute is selected). - Change the sorting option. - Only the first selected attribute is applied in the filter. opw-4244895 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#183927