Monday, December 28, 2020
14 changes · master
Miscellaneous changes
An account with the type "Credit Card" can not be chosen for the creation of a journal with the type "Bank" as the domain for bank account filter only for accounts with the type "Bank and Cash" As the filter on the `user_type_id` is too restrictive we remove it in case the journal is bank or cash opw-2394959 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 t
Original PR description
An account with the type "Credit Card" can not be chosen for the creation of a journal with the type "Bank" as the domain for bank account filter only for accounts with the type "Bank and Cash" As the filter on the `user_type_id` is too restrictive we remove it in case the journal is bank or cash opw-2394959 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#63095
1. Create a shipping address 2. Place a SO through backend, and choose that specific delivery address. 3. Archive that address 4. Place an Order through the website It is defaulting to the previously archived address, and not to the active one. opw-2411438 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-
Original PR description
1. Create a shipping address 2. Place a SO through backend, and choose that specific delivery address. 3. Archive that address 4. Place an Order through the website It is defaulting to the previously archived address, and not to the active one. opw-2411438 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#63576
Steps: - Install eCommerce - Go to Website > Products > Promotion Programs - Create a promotion program with a filter Based on Customers and a promotion code - Save - Edit the new program and clear the filter Based on Customers - Save again - Log out and go to the shop - Add an article to your cart and click "View Cart" - Click "I have a promo code" - Apply the promo code you created earlier Bug: The promo code is not accepted. Explanation: When the filter Based on Customers is
Original PR description
Steps: - Install eCommerce - Go to Website > Products > Promotion Programs - Create a promotion program with a filter Based on Customers and a promotion code - Save - Edit the new program and clear the filter Based on Customers - Save again - Log out and go to the shop - Add an article to your cart and click "View Cart" - Click "I have a promo code" - Apply the promo code you created earlier Bug: The promo code is not accepted. Explanation: When the filter Based on Customers is cleared, `[]` is written on the program rule. This makes the app search for a partner with id = 4 (Public User). Since this user is not active, the search returns no results and, therefore, forbids the user from using the promo code. This works flawlessly when you create a promotion program with no filters as they are initialized with `NULL` and a `NULL` filter always returns `True`. opw:2419796 Forward-Port-Of: odoo/odoo#63811 Forward-Port-Of: odoo/odoo#63751
**Description of the issue/feature this PR addresses:** As the price_unit and the uom rounding can be more detailed than the currency/accounting rounding (2 decimals as a standard) to cut the number before subtotal is wrong. **Current behavior before PR:** Invoice Line Price Unit of 5 digits is cut to 2 digits on change of a product or the UoM. **Desired behavior after PR is merged:** Keep the non-rounded and limited by the field `price_unit` number to calculate the correct subtotal whi
Original PR description
**Description of the issue/feature this PR addresses:** As the price_unit and the uom rounding can be more detailed than the currency/accounting rounding (2 decimals as a standard) to cut the number before subtotal is wrong. **Current behavior before PR:** Invoice Line Price Unit of 5 digits is cut to 2 digits on change of a product or the UoM. **Desired behavior after PR is merged:** Keep the non-rounded and limited by the field `price_unit` number to calculate the correct subtotal which is rounding correctly based on the currency rounding. Info: @wt-io-it -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#63653
Those kind of images use a specific route (/web_editor/shape/...) to be fetched. While waiting for a more complete solution to maybe handle them for model-related images, this commit only allows their use for images in views and HTML fields. Forward-Port-Of: odoo/odoo#63682
Original PR description
Those kind of images use a specific route (/web_editor/shape/...) to be fetched. While waiting for a more complete solution to maybe handle them for model-related images, this commit only allows their use for images in views and HTML fields. Forward-Port-Of: odoo/odoo#63682
The doc for client actions is currently too minimalistic to be of much use. This commit adds a seealso linking to the related tutorial. task-2423824 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#63818
Original PR description
The doc for client actions is currently too minimalistic to be of much use. This commit adds a seealso linking to the related tutorial. task-2423824 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#63818
Before this commit the deletion of custom snippets failed because the button click event got intercepted by the drag'n'drop mechanism. The currentTarget of the event was used in an asynchronous call where it had already been replaced by the jQuery's event bubbling mechanism when invoking the other handler. After this commit the deletion of custom snippets works again and a test tour is introduced to make sure it does not get broken again task-2405854 Description of the issue/feat
Original PR description
Before this commit the deletion of custom snippets failed because the button click event got intercepted by the drag'n'drop mechanism. The currentTarget of the event was used in an asynchronous call where it had already been replaced by the jQuery's event bubbling mechanism when invoking the other handler. After this commit the deletion of custom snippets works again and a test tour is introduced to make sure it does not get broken again task-2405854 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: Closes https://github.com/odoo/odoo/issues/62923 Fixes https://github.com/odoo/odoo/issues/62923 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#62555
What are the steps to reproduce your issue ? 1. Install website_blog 2. Go to website and add a new blog post 3. Remove the block content 4. Save and go to Blog page What is currently happening ? Crash: Template fallback An error occured while rendering the template website_blog.post_teaser opw-241937 Forward-Port-Of: odoo/odoo#63786
Original PR description
What are the steps to reproduce your issue ?
1. Install website_blog
2. Go to website and add a new blog post
3. Remove the block content
4. Save and go to Blog page
What is currently happening ?
Crash:
Template fallback
An error occured while rendering the template website_blog.post_teaser
opw-241937
Forward-Port-Of: odoo/odoo#63786The goal of this PR is to update the default theme tour (steps, changes on snippets...) as in other themes tours. task-2375011 Forward-Port-Of: odoo/odoo#63509 Forward-Port-Of: odoo/odoo#61733
Original PR description
The goal of this PR is to update the default theme tour (steps, changes on snippets...) as in other themes tours. task-2375011 Forward-Port-Of: odoo/odoo#63509 Forward-Port-Of: odoo/odoo#61733
Before this commit, the padding of the top action buttons in the editor (save, discard and undo buttons) was related to the buttons padding options of the theme. After this commit, the padding of those buttons doesnt change with the theme padding value. task-2349723 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
Original PR description
Before this commit, the padding of the top action buttons in the editor (save, discard and undo buttons) was related to the buttons padding options of the theme. After this commit, the padding of those buttons doesnt change with the theme padding value. task-2349723 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#58993
…voices Improvement over 6429b459c75f92af5404dd4630e58adc8f507172 As the followup does not contains only invoices but may also contain unreconciled move lines, it is necessary to move the blocked check on the latter. opw-2415902 Forward-Port-Of: odoo/enterprise#15386
Original PR description
…voices Improvement over 6429b459c75f92af5404dd4630e58adc8f507172 As the followup does not contains only invoices but may also contain unreconciled move lines, it is necessary to move the blocked check on the latter. opw-2415902 Forward-Port-Of: odoo/enterprise#15386
Before this commit, in case the user scans a package for an existing line then scans a location, it will notify an error. How to reproduce (enable package & multilocation): - Adds some qty. on hand for a product with a package; - Creates a transfer for this product, confirms it and reserves the quantity (be sure it reserved a line with this package); - Opens this transfer in the Barcode App; - Scans the package -> The app find the existing line; - Scans the location -> Error.
Original PR description
Before this commit, in case the user scans a package for an existing line then scans a location, it will notify an error. How to reproduce (enable package & multilocation): - Adds some qty. on hand for a product with a package; - Creates a transfer for this product, confirms it and reserves the quantity (be sure it reserved a line with this package); - Opens this transfer in the Barcode App; - Scans the package -> The app find the existing line; - Scans the location -> Error. opw-2417462 Forward-Port-Of: odoo/enterprise#15370
[FIX] industry_fsm_sale_report: - Display discounts on portal Worksheet Report - Display lines with 100% discount on portal Worksheet Report opw-2357912 Forward-Port-Of: odoo/enterprise#15466 Forward-Port-Of: odoo/enterprise#15463
Original PR description
[FIX] industry_fsm_sale_report: - Display discounts on portal Worksheet Report - Display lines with 100% discount on portal Worksheet Report opw-2357912 Forward-Port-Of: odoo/enterprise#15466 Forward-Port-Of: odoo/enterprise#15463
Go to Accounting > Configurations > Chart of Accounts Click on an account (i.e. 400000 - Product Sales) Add a Custom Group for this account Go to Configuration>Financial Reports>Profit and Loss Check 'Enable the hierarchy option' Go to Reporting > Profit and Loss You can see your group for the account 400000 and fold unfold it Fold the group and click "Print preview" The resulted PDF have the group unfolded, this because by default all results are collected and then organized by the v
Original PR description
Go to Accounting > Configurations > Chart of Accounts Click on an account (i.e. 400000 - Product Sales) Add a Custom Group for this account Go to Configuration>Financial Reports>Profit and Loss Check 'Enable the hierarchy option' Go to Reporting > Profit and Loss You can see your group for the account 400000 and fold unfold it Fold the group and click "Print preview" The resulted PDF have the group unfolded, this because by default all results are collected and then organized by the view. That does not occur when printing. opw-2363814 Forward-Port-Of: odoo/enterprise#15100 Forward-Port-Of: odoo/enterprise#15014