Wednesday, July 1, 2020
9 changes · master
Enhancements to existing features
The web test suite now better detects leftover page elements after automated tests complete. This helps catch test cleanup issues earlier, improving reliability for future development without changing normal user workflows.
Original PR description
Before this commit, unwanted elements left after QUnit tests were unnoticed because of some changes made to the XML test suite. Now, elements still present in the DOM after a test will be properly detected and logged, and an error will be thrown.
The Documents app action rule form now presents conditions before actions, making setup follow a more natural decision flow. Field labels were also clarified so users better understand the action button name and its related workspace.
Original PR description
Currently, 'Actions' is before 'Conditions' on the Actions rules setting. That's not logical, before act something, we have to define the conditions of this action. In this commit, we put 'Conditions' before 'Actions' on the Action rules setting. Also replace the label of 'Rule Name' and 'Workspace' by 'Action Button Name' and 'Related Workspace' respectively. LINKS PR: #11436 Task Id: 2278812
Features or functions removed from Odoo
The documentation no longer points readers to a JavaScript API page that was often unavailable or broken. This reduces confusion and helps users rely on documentation links that are more dependable.
Miscellaneous changes
- Install Accounting, Point of Sales - Go to Accounting > Configuration > Taxes - Create 2 taxes (e.g. Tax 15% and Tax 21%) - Go to Accounting > Configuration > Fiscal Positions - Create a new Fiscal Postion with the following line for Tax Mapping: * Tax on Product: Tax 21% * Tax to Apply: Tax 15% - Go to Point of Sale > Products > Products - Create a new Product (e.g. Test Product) with "Tax 15%" and "Tax 21%" in Customer Taxes - Go to Point of Sales and configure a POS: * Activ
Original PR description
- Install Accounting, Point of Sales - Go to Accounting > Configuration > Taxes - Create 2 taxes (e.g. Tax 15% and Tax 21%) - Go to Accounting > Configuration > Fiscal Positions - Create a new Fiscal…
- Install Accounting, Point of Sales - Go to Accounting > Configuration > Taxes - Create 2 taxes (e.g. Tax 15% and Tax 21%) - Go to Accounting > Configuration > Fiscal Positions - Create a new Fiscal Postion with the following line for Tax Mapping: * Tax on Product: Tax 21% * Tax to Apply: Tax 15% - Go to Point of Sale > Products > Products - Create a new Product (e.g. Test Product) with "Tax 15%" and "Tax 21%" in Customer Taxes - Go to Point of Sales and configure a POS: * Activate "Fiscal Position per Order" and choose the created Fiscal Position * Add Bank as Payment Method - Start a POS session - Search "Test Product" and add it - Click on Tax button and select the created Fiscal Position - Proceed to payment - Choose Bank and validate - Exit the POS session - Click on "CLOSE" and "VALIDATE CLOSING & POST ENTRIES" An error message appeared with the following message: "Cannot create unbalanced journal entry" When closing and posting entries, an account move and account move lines are created from the session orders. For each order lines, taxes are computed from taxes on product and fiscal position of the order. In this case, the product has 2 taxes applied (Tax 15% and Tax 21%). Due to the chosen Fiscal Position, the Tax 15% is applied instead of Tax 21%. For the order line, Tax 15% is applied 2 times. But during the account move lines generation, the original Tax 15% and the converted Tax 15% are merged together, because they represent the same tax (same model id). So the Tax 15% is only applied once, which results on unbalanced amounts during reconciliation. In Sales, for the same case, the tax is only applied once. To stay consistent with Sales behavior, the tax will also be applied once in Point of Sale. opw-2278826 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#53549
odoo/odoo#42015 removed code supporting the sales/CRM dashboards which hadn't been a thing for two years at that point. This is doubly dead code as it's an override for the dead code which has already been removed for a feature which hasn't existed since 2017. Forward-Port-Of: odoo/odoo#53811
Original PR description
odoo/odoo#42015 removed code supporting the sales/CRM dashboards which hadn't been a thing for two years at that point. This is doubly dead code as it's an override for the dead code which has already been removed for a feature which hasn't existed since 2017. Forward-Port-Of: odoo/odoo#53811
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#38301
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 Forward-Port-Of: odoo/odoo#38301
Previously, duplicating a block inside of the newsletter popup would cause the subscribe input and button to disappear. Actually, it disappears when you use most options of the left panel, because selecting an option refreshes the public widgets, which destroys them and starts them again, but for some reason, the subscribe widget's destroy method makes it d-none, but only removes that class if the subscribe input is not inside of a modal. This commit fixes that by not using d-none on th
Original PR description
Previously, duplicating a block inside of the newsletter popup would cause the subscribe input and button to disappear. Actually, it disappears when you use most options of the left panel, because selecting an option refreshes the public widgets, which destroys them and starts them again, but for some reason, the subscribe widget's destroy method makes it d-none, but only removes that class if the subscribe input is not inside of a modal. This commit fixes that by not using d-none on the subscribe input group at all. task-2244780 Forward-Port-Of: odoo/odoo#50286
Small fixup of initial commit abac008c0f4c72b37e7d86cf17cc0ffb8f027953. opw-2287817 Forward-Port-Of: odoo/enterprise#11564
Original PR description
Small fixup of initial commit abac008c0f4c72b37e7d86cf17cc0ffb8f027953. opw-2287817 Forward-Port-Of: odoo/enterprise#11564
Make the `_lot_not_supported_rental` support a recordset to avoid a singleton error. opw-2284157 Forward-Port-Of: odoo/enterprise#11557 Forward-Port-Of: odoo/enterprise#11555
Original PR description
Make the `_lot_not_supported_rental` support a recordset to avoid a singleton error. opw-2284157 Forward-Port-Of: odoo/enterprise#11557 Forward-Port-Of: odoo/enterprise#11555