Wednesday, August 11, 2021
16 changes · master
Enhancements to existing features
This change adds internal checks that measure how long web asset bundles take to generate. It helps the team detect performance slowdowns early so future changes do not make asset preparation unexpectedly slower.
Original PR description
From time to time, the bundle generation duration may be unexpectedly increased by assets modifications. In order to avoid that, this commit adds two tests that generates all the bundles. One of the test is only meant to log the duration in order to monitor it. The other test is ensuring that a bundle generation does not take more than 2 seconds. Pay attention that the purpose is not to test the generation of the bundle, any error during generation is logged as an information. Also, warnings are silently ignored.
Spreadsheet pivot tables with several header levels now use an additional visual style to make their structure easier to read. This helps users understand complex reports more quickly and reduces confusion when reviewing multi-level pivot data.
Original PR description
If an inserted pivot has multiple levels it can be hard to folow the structure as all the header element except the main headers have the same styling. This commit add a third style to help with the readibility of an inserted pivot task-id: 2304328
Resolved issues and error corrections
This fixes an issue where older dropdown menus in the web interface could appear in the wrong position. Users should see menus open where expected, reducing confusion during navigation and data entry.
Original PR description
Before this commit: the legacy dropdown menus are not placed properly Issue introduced with commit odoo/odoo@0bb93b2 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
Miscellaneous changes
PURPOSE The error message should be displayed correctly while sending a survey invitation. The purpose of this commit is to correct the error message. SPECIFICATIONS Currently, while sending an invitation with the 'one page per section' layout survey and if the survey has a question, but not has section, then the popup is displayed "You cannot send an invitation for a survey that has no questions." This improves the error message like below. "You cannot send an invitation to
Original PR description
PURPOSE The error message should be displayed correctly while sending a survey invitation. The purpose of this commit is to correct the error message. SPECIFICATIONS Currently, while sending an invitation with the 'one page per section' layout survey and if the survey has a question, but not has section, then the popup is displayed "You cannot send an invitation for a survey that has no questions." This improves the error message like below. "You cannot send an invitation to a 'One page per section' survey if the survey has no section." This is the goal of this commit. LINKS PR #74430 TaskID-2611996 Forward-Port-Of: odoo/odoo#74510 Forward-Port-Of: odoo/odoo#74430
Popovers now appear closer to the item they point to, instead of being offset too far away. This makes contextual information feel more precise and improves the overall user experience in the web interface.
Original PR description
Before this commit, the popover was a bit far from its target. We use a margin to compensate the arrow size (8px), but we used it the wrong way, meaning that instead of applying, e.g. a margin of -8px, we applied a margin of 8px. As a consequence, popover were always positionned at 16px from their target. 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 update adds missing text encoding settings to report and dashboard templates. It helps prevent display or rendering problems when documents include special characters, improving reliability for users working with financial reports and subscription dashboards.
Original PR description
following the change: https://github.com/odoo/odoo/commit/7df343dd1be1f286493660ed8fd28669ab4a8311
journal_id value would change when grouping payments in wizard if partner_bank_id was set on a move Forward-Port-Of: odoo/odoo#74830
Original PR description
journal_id value would change when grouping payments in wizard if partner_bank_id was set on a move Forward-Port-Of: odoo/odoo#74830
odoo/odoo#74678 fixed the universal traceback which would happen any time an HTML field would be read, however it's incomplete because: * it was tested on a field which wasn't HTML in 14.4 * and no markup was put in the field anyway So the markup being embedded in the XML-RPC document unescaped was missed, leading to: * corrupted (partial) responses when the HTML content is XML-valid, depending on the exact API of the client it might only return the first or last text segment,
Original PR description
odoo/odoo#74678 fixed the universal traceback which would happen any time an HTML field would be read, however it's incomplete because: * it was tested on a field which wasn't HTML in 14.4 * and no…
odoo/odoo#74678 fixed the universal traceback which would happen any time an HTML field would be read, however it's incomplete because: * it was tested on a field which wasn't HTML in 14.4 * and no markup was put in the field anyway So the markup being embedded in the XML-RPC document unescaped was missed, leading to: * corrupted (partial) responses when the HTML content is XML-valid, depending on the exact API of the client it might only return the first or last text segment, or all the text without markup, or something else * outright deserialisation error on XML-invalid content (e.g. void elements like <br>) The cause being that `Markup` overrides all `str` methods to first escape their parameters before actually applying on the object. This means `xmlrpc.client.escape` would basically do nothing, then would concatenate the `Markup` into the document (stringifying it) and send the entire thing on its way. Fixes #74884 Forward-Port-Of: odoo/odoo#74946
…user email differs. This commit allows using different mail on the user and the partner without experiencing weird behaviors. Before this commit, sometimes when user would set a different email on his user_id and his main partner, the sync event would not be visible as long as the event was not accepted in Google. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#74824
Original PR description
…user email differs.
This commit allows using different mail on the user and the partner without experiencing weird behaviors.
Before this commit, sometimes when user would set a different email on his user_id and his main partner, the sync event would not be visible as long as the event was not accepted in Google.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#74824…plate Before commit: The issue is that the product is not in the 'available' filter but its kanban tile says 'on hand' quantity is available. A different issue is a raise because of this commit: https://github.com/odoo/odoo/commit/b08e3d114aa4efe687b4d4cca3de462a3dbe6eea. in this commit set the "active_test=False" for product template that's why it fetches all active and inactive warehouses and it becomes true for product variant as we don't get active_test=False. so
Original PR description
…plate Before commit: The issue is that the product is not in the 'available' filter but its kanban tile says 'on hand' quantity is available. A different issue is a raise because of this commit: https://github.com/odoo/odoo/commit/b08e3d114aa4efe687b4d4cca3de462a3dbe6eea. in this commit set the "active_test=False" for product template that's why it fetches all active and inactive warehouses and it becomes true for product variant as we don't get active_test=False. so condition becomes true and it will fetch only active warehouse and related location and result is displayed the different on_hand qty on variant and template. After commit: we prevent the archive location quantity on the product template and its related quants to make a consistency between product template and product variant. This issue was found while on upgrade issue: opw: M1712276115202. Forward-Port-Of: odoo/odoo#74748 Forward-Port-Of: odoo/odoo#73339
The template to render location and picking barcodes was not optimized to print lots of barcode. This could lead to extremely long documents with a few barcodes to print. Opw: 2564764 X-original-commit: 9b5bc6cbd2cd415580cee12051e882a2a96a69ab 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 Forward-Port-Of: odoo/odo
Original PR description
The template to render location and picking barcodes was not optimized to print lots of barcode. This could lead to extremely long documents with a few barcodes to print. Opw: 2564764 X-original-commit: 9b5bc6cbd2cd415580cee12051e882a2a96a69ab 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 Forward-Port-Of: odoo/odoo#74927
Printing the barcode commands pdf will add all the picking types as well as all the locations having a barcode. This can lead to a memory error from wkhtmltopdf if there is too much data to handle. This commit limits the number of locations and picking type sent to the pdf generation. The barcodes can be printed via the locations/picking types menus anyways if needed. Opw: 2564764 X-original-commit: 85c850f59f6fe46bec0c011b4274a12c598e6698 Forward-Port-Of: odoo/enterprise#20156
Original PR description
Printing the barcode commands pdf will add all the picking types as well as all the locations having a barcode. This can lead to a memory error from wkhtmltopdf if there is too much data to handle. This commit limits the number of locations and picking type sent to the pdf generation. The barcodes can be printed via the locations/picking types menus anyways if needed. Opw: 2564764 X-original-commit: 85c850f59f6fe46bec0c011b4274a12c598e6698 Forward-Port-Of: odoo/enterprise#20156
Before this commit: when clicking on magnifying glass it cannot show data properly because the parent current domain is applied by default. After this commit: Only action domain is applied by default and it thus shows data properly. Task-2550953 Co-authored-by: bit-odoo <bit@odoo.com> Original PR: #19739 Forward-Port-Of: odoo/enterprise#20136 Forward-Port-Of: odoo/enterprise#20130
Original PR description
Before this commit: when clicking on magnifying glass it cannot show data properly because the parent current domain is applied by default. After this commit: Only action domain is applied by default and it thus shows data properly. Task-2550953 Co-authored-by: bit-odoo <bit@odoo.com> Original PR: #19739 Forward-Port-Of: odoo/enterprise#20136 Forward-Port-Of: odoo/enterprise#20130
ABA count of unsent batches never decrements. Code updated in line with SEPA module. Forward-Port-Of: odoo/enterprise#20018
Original PR description
ABA count of unsent batches never decrements. Code updated in line with SEPA module. Forward-Port-Of: odoo/enterprise#20018
We can now have partial match of a purchase order. In the case where the invoice received only corresponds to a subset of lines of the purchase order, it will automatically try to find and set that subset of lines on the invoice. Forward-Port-Of: odoo/enterprise#20015 Forward-Port-Of: odoo/enterprise#18433
Original PR description
We can now have partial match of a purchase order. In the case where the invoice received only corresponds to a subset of lines of the purchase order, it will automatically try to find and set that subset of lines on the invoice. Forward-Port-Of: odoo/enterprise#20015 Forward-Port-Of: odoo/enterprise#18433
Step to follow Go to the documents app Upload a document Cause of the issue When allowed_company_ids is not in the context, request.company returns the default one Solution Pass allow_company_ids to the context opw-2554649 Forward-Port-Of: odoo/enterprise#20142 Forward-Port-Of: odoo/enterprise#19933
Original PR description
Step to follow Go to the documents app Upload a document Cause of the issue When allowed_company_ids is not in the context, request.company returns the default one Solution Pass allow_company_ids to the context opw-2554649 Forward-Port-Of: odoo/enterprise#20142 Forward-Port-Of: odoo/enterprise#19933