Saturday, August 22, 2020
11 changes · master
Enhancements to existing features
The core Odoo release version has been updated for the master branch to 14.1 alpha. This helps align internal versioning and release identification as development moves toward the next release cycle.
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
This fixes small issues that caused upgrade validation tests to show warnings or fail unnecessarily. The changes help ensure module upgrades complete more reliably without affecting day-to-day business workflows.
Original PR description
Multiple fix to make upgrade test green
Miscellaneous changes
Steps to reproduce: - Install MRP and Inventory - In Settings > Decimal accuracy, change the number of digits of Product Price to 6 - Go to a product template PT Bug: The field standard_price was displayed with two digits instead of 6 opw:2241369 Forward-Port-Of: odoo/odoo#56203
Original PR description
Steps to reproduce: - Install MRP and Inventory - In Settings > Decimal accuracy, change the number of digits of Product Price to 6 - Go to a product template PT Bug: The field standard_price was displayed with two digits instead of 6 opw:2241369 Forward-Port-Of: odoo/odoo#56203
This fixes small visual gaps that could appear between decorative website shapes and the surrounding page area. The change helps website sections look more polished and consistent across browsers.
Original PR description
Because of the way browsers render SVGs as background images, background SVGs will sometimes not perfectly hug the top or bottom of their containers because of rounding in the calculation of the width from the height, or height from the width. This commit fixes a number of the shapes displaying this behaviour, by making their viewbox a perfect square, this means that whenever the width or height of the SVG is determined by the brower, it will use the same number for the height or width respectively because the aspect ratio is exactly one, rather than using the closest integer approximation of the aspect ratio, which causes those artifacts.
From now, you need to explicitely add sitemap=True if you want your controller into the sitemap. It's the default value, but if you forgot it, it will raise a Warning on runbot. It will avoid wrong controller in sitemap and duplicate (empty) content. From now, if your model contains a field website_id, the modelConverter for sitemap will automatically add the domain: "[('website_id', 'in', (False, current_website_id))]" It avoid redundant declaration and ugly url in redirect/rewrite vi
Original PR description
From now, you need to explicitely add sitemap=True if you want your controller
into the sitemap. It's the default value, but if you forgot it, it will raise
a Warning on runbot. It will avoid wrong controller in sitemap and duplicate
(empty) content. From now, if your model contains a field website_id, the
modelConverter for sitemap will automatically add the domain:
"[('website_id', 'in', (False, current_website_id))]"
It avoid redundant declaration and ugly url in redirect/rewrite view.
Task ID: 2318597
Forward-Port-Of: odoo/odoo#56054PURPOSE Same error message in Firefox and Chrome in crash_manager SPEC Add somewhere in the code throw new Error('hello world'); -> in chrome, the error message and traceback are properly displayed -> in firefox, the error message isn't displayed TASK 2191727 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#56274
Original PR description
PURPOSE
Same error message in Firefox and Chrome in crash_manager
SPEC
Add somewhere in the code
throw new Error('hello world');
-> in chrome, the error message and traceback are properly displayed
-> in firefox, the error message isn't displayed
TASK 2191727
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#56274- Create 2 customers A & B - On A, set a Payment Term for Sales and Purchases - Create a customer invoice - Add a line - Set Partner A => the payment term is selected - Set Partner B => the payment term is kept Moreover, the term account is set onmy if the customer has a payment term set, which is not logical. Since the partner is not mandatory, we keep an intermediate behavior: we set the info of the partner only if there is a partner defined. opw-2304436 Description of
Original PR description
- Create 2 customers A & B - On A, set a Payment Term for Sales and Purchases - Create a customer invoice - Add a line - Set Partner A => the payment term is selected - Set Partner B => the payment term is kept Moreover, the term account is set onmy if the customer has a payment term set, which is not logical. Since the partner is not mandatory, we keep an intermediate behavior: we set the info of the partner only if there is a partner defined. opw-2304436 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#55627
Phone validation of crm_leads was using crm.lead country instead of partner country code. This was leading to phone number of crm_case_16 coming from an us partner validated as a uk phone number. (same applies for crm_case_14) The problem was discovered in pre/post upgrade crawler test. Failure example: https://runbot.odoo.com/runbot/build/3938632 Forward-Port-Of: odoo/odoo#56336
Original PR description
Phone validation of crm_leads was using crm.lead country instead of partner country code. This was leading to phone number of crm_case_16 coming from an us partner validated as a uk phone number. (same applies for crm_case_14) The problem was discovered in pre/post upgrade crawler test. Failure example: https://runbot.odoo.com/runbot/build/3938632 Forward-Port-Of: odoo/odoo#56336
Now any set of widgets and rows can be placed in a we-collapse element so that those elements can be foldable. The first element inside (or the mentioned "string" on the we-collapse element itself) is used as the always shown element (with a toggler on its left to toggle the visibility of the other items). we-collapse inside other we-collapse is supported as well. Limitations / Other infos: - The use of '⌙' and   characters is not automatic (yet?). Sometimes it actually ma
Original PR description
Now any set of widgets and rows can be placed in a we-collapse element
so that those elements can be foldable. The first element inside (or
the mentioned "string" on the we-collapse element itself) is used as the
always shown element (with a toggler on its left to toggle the
visibility of the other items).
we-collapse inside other we-collapse is supported as well.
Limitations / Other infos:
- The use of '⌙' and   characters is not automatic (yet?).
Sometimes it actually make sense to use them without a we-collapse or
to not use them in a we-collapse.
- The use of we-collapse is limited to widgets inside the same option.
So unfortunately, there is no current way to add all bg image options
in a folable section as those contain many different options. Maybe
in the future.
Forward-Port-Of: odoo/odoo#56350Description 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#55988
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#55988
According to this document: http://legilux.public.lu/eli/etat/leg/rgd/2019/09/12/a631/jo The account 44113 should be in assets and so it should be added in the liabilities opw:2313939 Forward-Port-Of: odoo/enterprise#12484
Original PR description
According to this document: http://legilux.public.lu/eli/etat/leg/rgd/2019/09/12/a631/jo The account 44113 should be in assets and so it should be added in the liabilities opw:2313939 Forward-Port-Of: odoo/enterprise#12484