Tuesday, July 20, 2021
15 changes · master
Enhancements to existing features
Renames confusing menu labels in Fleet and Website so users can more easily distinguish business menus from technical menus. Fleet's "Models" becomes "Vehicle Models", and Website's "Views" becomes "Page Views", including the related action name for consistency.
Original PR description
PURPOSE Right now, some menus having frequently accessed the same name, so it is mixed with technical/../menu while searching with name of the menu. this may cause user confuse. SPECIFICATION in this PR, change the frequent menu name 'Models' to 'Vehicle Models' and 'Views' to 'Page Views'. TaskId: 2595993 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update corrects internal developer documentation for web components so automated documentation tools can read it properly. It also clarifies default notification settings, helping future maintenance without changing how users experience the product.
Original PR description
jsdoc apparently doesn't understand arrow functions to indicate function-valued attributes. Also add some default values in the notifications typedefs.
Miscellaneous changes
**Description of the issue/feature this PR addresses:** Before this commit UserError, ValidationError are not correctly show. **Current behavior before PR:**  **Desired behavior after PR is merged:**  @pimodoo @rhe-odoo -- I confirm I have signed the CLA an
Original PR description
**Description of the issue/feature this PR addresses:** Before this commit UserError, ValidationError are not correctly show. **Current behavior before PR:**  **Desired behavior after PR is merged:**  @pimodoo @rhe-odoo -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#73649
Fixed an issue where clicking display-only buttons on the website visitor form could trigger an error. These visitor status and visit-count buttons are now correctly treated as non-clickable, preventing confusing interruptions for users.
Original PR description
PURPOSE Fix Traceback which occurs when clicking on buttons. SPECIFICATIONS In Visitors form if Connected/Offline or Visits button are clicked traceback occurs. LINKS PR #73813 Task 2593552
Before this commit, for a subcontracted product with reserved available tracked components, if at least one component is recorded but not all, the "Record components" button isn't available anymore. How to reproduce: - Create a product and create a subcontracting BOM for this product; - Add a tracked component for this product; - Add some qty. for the tracked component in the subcontracting loc.; - Create a receipt for the subcontracted product (for demand qty. more than 1) with t
Original PR description
Before this commit, for a subcontracted product with reserved available tracked components, if at least one component is recorded but not all, the "Record components" button isn't available anymore.
How to reproduce:
- Create a product and create a subcontracting BOM for this product;
- Add a tracked component for this product;
- Add some qty. for the tracked component in the subcontracting loc.;
- Create a receipt for the subcontracted product (for demand qty. more than 1) with the subcontractor as partner and confirm it:
=> The "Record components" button should be visible.
- Record a part of the demand qty. then click on "Continue", then on "Discard":
=> The "Record components" button is now hidden.
It's because the button is hidden if all the MO are done or to close (they are) and if all the tracked move lines have a SN/LN (they have as they are reserved).
task-2604728
Forward-Port-Of: odoo/odoo#73780Description of the issue/feature this PR addresses: Currently, the quantity delivered of a sales order line for a dropship product with a kit BoM will never be updated if there is any related move that has been cancelled, for example there are several pickings and one of them has been cancelled. Current behavior before PR: The quantity delivered is not updated in the scenario described above. Desired behavior after PR is merged: The quantity delivered is computed considering the stock move
Original PR description
Description of the issue/feature this PR addresses: Currently, the quantity delivered of a sales order line for a dropship product with a kit BoM will never be updated if there is any related move that has been cancelled, for example there are several pickings and one of them has been cancelled. Current behavior before PR: The quantity delivered is not updated in the scenario described above. Desired behavior after PR is merged: The quantity delivered is computed considering the stock moves that are not cancelled. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#73532 Forward-Port-Of: odoo/odoo#73372
Before this commit, overrided images was not visible if not logged in. How to reproduce ---------------- Install a theme with configurator to have custom image of industries. Log out You have original image instead of industries 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#73863
Original PR description
Before this commit, overrided images was not visible if not logged in. How to reproduce ---------------- Install a theme with configurator to have custom image of industries. Log out You have original image instead of industries 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#73863
In 2018 geoip2 support was added to allow the new database format that are freely available. But for these, only a subset of properties are available. Since Odoo 13 (August 2019), the sign module is using geoip latitude and longitude for logging access to sign module signatures, but this was only working for database using the first version of GeoIP databases. In other use case there would never be any geolocalization recorded. With this change, latitude and longitude are available in the ses
Original PR description
In 2018 geoip2 support was added to allow the new database format that are freely available. But for these, only a subset of properties are available. Since Odoo 13 (August 2019), the sign module is using geoip latitude and longitude for logging access to sign module signatures, but this was only working for database using the first version of GeoIP databases. In other use case there would never be any geolocalization recorded. With this change, latitude and longitude are available in the session if the right module/database is installed. opw-2426323 Forward-Port-Of: odoo/odoo#73973
- Define a [DEMO] prod with tracking by SN and add some SNs - Activate "use existing lot/serial number" on the receipt picking type - Create a purchase order for [DEMO] - Process the receipt in the barcode app: * Scan the product * Scan the SN barcode * Validate User will get an error. It seems that Odoo is trying to create this SN instead of matching the existing one opw-2474347 Description of the issue/feature this PR addresses: Current behavior before PR: Desired
Original PR description
- Define a [DEMO] prod with tracking by SN and add some SNs - Activate "use existing lot/serial number" on the receipt picking type - Create a purchase order for [DEMO] - Process the receipt in the barcode app: * Scan the product * Scan the SN barcode * Validate User will get an error. It seems that Odoo is trying to create this SN instead of matching the existing one opw-2474347 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#70097
After FW-port https://github.com/odoo/odoo/pull/64721 Section for down payment were added multiple times because of a typo 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#73834
Original PR description
After FW-port https://github.com/odoo/odoo/pull/64721 Section for down payment were added multiple times because of a typo 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#73834
Since 14.3, Taxes have a country field. Newly created taxes don't always have the correct country set, thereby making the tax unusable. Issue identified in task 2591541 Forward-Port-Of: odoo/odoo#74038
Original PR description
Since 14.3, Taxes have a country field. Newly created taxes don't always have the correct country set, thereby making the tax unusable. Issue identified in task 2591541 Forward-Port-Of: odoo/odoo#74038
Adding tests for the follwing barcode flow - Define a [DEMO] prod with tracking by SN and add some SNs - Activate "use existing lot/serial number" on the receipt picking type - Create a purchase order for [DEMO] - Process the receipt in the barcode app: * Scan the product * Scan the SN barcode * Validate opw-2474347 Forward-Port-Of: odoo/enterprise#18277
Original PR description
Adding tests for the follwing barcode flow - Define a [DEMO] prod with tracking by SN and add some SNs - Activate "use existing lot/serial number" on the receipt picking type - Create a purchase order for [DEMO] - Process the receipt in the barcode app: * Scan the product * Scan the SN barcode * Validate opw-2474347 Forward-Port-Of: odoo/enterprise#18277
Since a2669c1 sale_amazon single module build was broken in test when validating a picking A first attempt to fix this was made in #19672. Unfortunattely this was not enough since this error was also triggered in other tests and helped to discover that this error wasn't leggit in some case: it should only be triggered if sale_id is linked to an amazon_order_ref but the check was triggered for all picking. The first part of this commit checks that we have an amazon_picking before chec
Original PR description
Since a2669c1 sale_amazon single module build was broken in test when validating a picking A first attempt to fix this was made in #19672. Unfortunattely this was not enough since this error was also triggered in other tests and helped to discover that this error wasn't leggit in some case: it should only be triggered if sale_id is linked to an amazon_order_ref but the check was triggered for all picking. The first part of this commit checks that we have an amazon_picking before checking if the module is installed. The second part checks if we are in a test to avoid to trigger this error on existing tests. This fix is crapy but easier to forwardport. It looks like more of the logic could be put under the `if amazon_pickings:` condition for performance reason but this will target master. Forward-Port-Of: odoo/enterprise#19748 Forward-Port-Of: odoo/enterprise#19735
- Create a Loyalty Program with at least 1 Points Rules applicable to all products - Delete the Loyalty Program just created - Open a POS Session - Set the customer and add a product on the list. Points will be awarded. This occur because: - rules are loaded in POS without taking into account POS settings - rules are not deleted along with the program opw-2560038 Forward-Port-Of: odoo/enterprise#19289 Forward-Port-Of: odoo/enterprise#19265
Original PR description
- Create a Loyalty Program with at least 1 Points Rules applicable to all products - Delete the Loyalty Program just created - Open a POS Session - Set the customer and add a product on the list. Points will be awarded. This occur because: - rules are loaded in POS without taking into account POS settings - rules are not deleted along with the program opw-2560038 Forward-Port-Of: odoo/enterprise#19289 Forward-Port-Of: odoo/enterprise#19265
Before this commit, the tests weren't run. Also, this commit changes the trigger in the test tour because it seems they are outdated. The test `test_receipt_tracked_subcontracted_product` can't pass without the community fix ba2f3cad2c67dd4385b78d3dcadd16c32c641d76 task-2604728 Forward-Port-Of: odoo/enterprise#19686
Original PR description
Before this commit, the tests weren't run. Also, this commit changes the trigger in the test tour because it seems they are outdated. The test `test_receipt_tracked_subcontracted_product` can't pass without the community fix ba2f3cad2c67dd4385b78d3dcadd16c32c641d76 task-2604728 Forward-Port-Of: odoo/enterprise#19686