Daily updates from Odoo
Friday, July 28, 2023
13 changes · master
Enhancements to existing features
This update simplifies how automated tests are set up across several Odoo Enterprise apps by removing custom setup workarounds. It helps keep test maintenance simpler and more reliable, with no expected change for end users.
Original PR description
community: https://github.com/odoo/odoo/pull/129705
Resolved issues and error corrections
This update prevents an error when viewing online bank account selection options before balance data has finished loading. Balances are now loaded at the right time and checked before display, improving reliability for users managing online bank synchronization.
Original PR description
Since [8723f020](https://github.com/odoo/odoo/commit/8723f020), a new way to define items in `radio_field.js` is used. The problem is that `items` are now defined asynchronous and it causes that our widget tries to load `balances` data using these `items` when we still don't have. It causes a traceback. This fix load the balances data when the component is mounted and there is 2 helpers functions that verifies if we have the data or not before displaying it. A test has been added to avoid this problem next time.
Code cleanup and technical improvements
This update refreshes several Point of Sale screens by replacing custom styling with standard Bootstrap layout tools. This should make the interface easier to maintain and more consistent, with limited direct impact on day-to-day workflows.
Original PR description
pos*: l10n_cl_edi_pos,l10n_mx_edi_pos,pos_settle_due Prior to this commit, the point_of_sale module relied on custom CSS. To enhance user experience, increase flexibility, and simplify maintenance, most of the custom css was replaced in this PR with Bootstrap utility classes. Task: 3354582 Co-authored-by: Xavier Luyckx (xlu) <xlu@odoo.com> Co-authored-by: vlst <vlst@odoo.com> Task: 3354582
Miscellaneous changes
Make the unfoldable line cursor pointer on hover. Forward-Port-Of: odoo/enterprise#44744
Original PR description
Make the unfoldable line cursor pointer on hover. Forward-Port-Of: odoo/enterprise#44744
Change the color of some elements to better adapt the dark mode. Forward-Port-Of: odoo/enterprise#44736
Original PR description
Change the color of some elements to better adapt the dark mode. Forward-Port-Of: odoo/enterprise#44736
Make the styling of journal report name into a link. Forward-Port-Of: odoo/enterprise#44729
Original PR description
Make the styling of journal report name into a link. Forward-Port-Of: odoo/enterprise#44729
[IMP] Account_deferred_reports: Text styling Make the column name 'TOTALS' sentence case 'Totals' Forward-Port-Of: odoo/enterprise#44728
Original PR description
[IMP] Account_deferred_reports: Text styling Make the column name 'TOTALS' sentence case 'Totals' Forward-Port-Of: odoo/enterprise#44728
Steps to reproduce: Go to general ledger report in the accounting module. Unfold just one of the lines and print the report. Current Behaviour: The pdf printed will have all the lines unfolded. Expected Behaviour: The pdf should have unfolded only those lines which were unfolded in the report screen. We only want the report to automatically unfold all of its lines in the export when no line was manually unfolded in the UI. OPW-3355960 Forward-Port-Of: odoo/enterprise#44721 Forw
Original PR description
Steps to reproduce: Go to general ledger report in the accounting module. Unfold just one of the lines and print the report. Current Behaviour: The pdf printed will have all the lines unfolded. Expected Behaviour: The pdf should have unfolded only those lines which were unfolded in the report screen. We only want the report to automatically unfold all of its lines in the export when no line was manually unfolded in the UI. OPW-3355960 Forward-Port-Of: odoo/enterprise#44721 Forward-Port-Of: odoo/enterprise#42624
Steps to reproduce: - Go to /shop on a day where a pickup is allowed by the company; - Select a rental product; - Select the minimum available date (now, now + preparation time or today, depending on the product setting); - Add to cart; Current behaviour: The product is not added to the cart and a warning says that you cannot rent in the past. Same check would prevent to pay for it. Expected behaviour: The product should be available to cart and payment should not be blocked.
Original PR description
Steps to reproduce: - Go to /shop on a day where a pickup is allowed by the company; - Select a rental product; - Select the minimum available date (now, now + preparation time or today, depending on the product setting); - Add to cart; Current behaviour: The product is not added to the cart and a warning says that you cannot rent in the past. Same check would prevent to pay for it. Expected behaviour: The product should be available to cart and payment should not be blocked. Note: we now add a buffer of 15 minutes between the moment the customer adds a product and the check to fail, so that the customer can rent as soon as possible. OPW-3436743 Forward-Port-Of: odoo/enterprise#44643
Have a Bill with line count exceeding the Journal report 'load more limit' setting Open the journal report Under 'Vendor Bill' section hit load more Issue: The move will not show up. If the move should be the first one to show up, a traceback will appear once user click 'load more' A solution is to detect when we are loading a large move, and avoid creating a second 'first line' opw-3422815 Forward-Port-Of: odoo/enterprise#44350
Original PR description
Have a Bill with line count exceeding the Journal report 'load more limit' setting Open the journal report Under 'Vendor Bill' section hit load more Issue: The move will not show up. If the move should be the first one to show up, a traceback will appear once user click 'load more' A solution is to detect when we are loading a large move, and avoid creating a second 'first line' opw-3422815 Forward-Port-Of: odoo/enterprise#44350
Before this commit ================== If any of the work-order has an operation with undone quality checks the user error won't show up when triggering 'Done' inside WO list view. Steps to produce ================ - Create a bom product having work-order that includes an operation having quality control with the type 'Print Label'. - Create a MO and confirm it. - Inside the WO list view select the WO and trigger 'Done'. The user error will not show up even though the quality check is un
Original PR description
Before this commit ================== If any of the work-order has an operation with undone quality checks the user error won't show up when triggering 'Done' inside WO list view. Steps to produce ================ - Create a bom product having work-order that includes an operation having quality control with the type 'Print Label'. - Create a MO and confirm it. - Inside the WO list view select the WO and trigger 'Done'. The user error will not show up even though the quality check is unfinished. Issue ===== The error only shows up if the quality_mrp_workorder module gets installed. With this commit ================ User error will occur if the WO with an operation having unfinished quality check when triggering 'Done'. Task: 3374990 Forward-Port-Of: odoo/enterprise#44631 Forward-Port-Of: odoo/enterprise#44535
This commit removes the non-standard green box shadow and makes the section stand out thanks to an alert primary style that is more visually appealing and matches more the new MILK style Before:  After:  Community PR: https://github.com/
Original PR description
This commit removes the non-standard green box shadow and makes the section stand out thanks to an alert primary style that is more visually appealing and matches more the new MILK style Before:  After:  Community PR: https://github.com/odoo/odoo/pull/128459 task-3424358 part of task-3326263 Forward-Port-Of: odoo/enterprise#44079
Ensure that the `WysiwygHelper` is correctly displayed even after applying a bunch of steps coming from the collaboration (`historyExternalSteps`). Ensure that the backend does not write on the body of an existing article, since this will either be non-effective if a collaborator is editing the article currently and succeeds to save after the write, or it risks breaking the collaboration in case the user which initiated the write was in the collaboration, and succeeds in reloading the vi
Original PR description
Ensure that the `WysiwygHelper` is correctly displayed even after applying a bunch of steps coming from the collaboration (`historyExternalSteps`). Ensure that the backend does not write on the body…
Ensure that the `WysiwygHelper` is correctly displayed even after applying a bunch of steps coming from the collaboration (`historyExternalSteps`). Ensure that the backend does not write on the body of an existing article, since this will either be non-effective if a collaborator is editing the article currently and succeeds to save after the write, or it risks breaking the collaboration in case the user which initiated the write was in the collaboration, and succeeds in reloading the view with the new body value after the write, since in that case the editor does not have the time to write collaborative steps id in the first node resulting in a `stale` situation where the editor thinks the new body is a stale version of the document that is still being edited with its old value by the other collaborators. The solution is to allow `apply_template_on_article` to do all non-collaborative write, and return the body value without writing it. The client which applied the template will then create a collaborative step with that new value to share it with collaborators, using `wysiwyg.setValue`. ICE servers are a mail feature, and the `editor` uses a hack to check if it is installed by checking `getSession().notification_type`. The issue is that this value is not present for portal users that should be able to use the collaborative feature for Knowledge. Since `mail` is a dependency of Knowledge, we can override the hack to let the editor know that the ICE servers are available as long as Knowledge is installed. Allow useAsDescription macro to attempt pasting again after joining a collaboration session in an external record, quite like the embedded view insertion in Knowledge. task-3378266 Forward-Port-Of: odoo/enterprise#43881