Wednesday, December 23, 2020
12 changes · master
Enhancements to existing features
Course tags in eLearning are now separated between internal backend tags and public-facing website tags. This keeps internal classification hidden from visitors while ensuring only relevant tags appear in website filters and menus.
Original PR description
colorless tags are not showing in frontend and dynamic menu, course group have tags in tree view now, public and portal users have no access to colorless tag, slide officer have complete access. Task-id: 2357942
Resolved issues and error corrections
When deleting records, the confirmation window now closes if the deletion fails with a user-facing error. This prevents users from seeing repeated error messages and makes the deletion flow clearer.
Original PR description
PURPOSE Close cofirm dialog on UserError. SPEC Deleting records from listview show confirm dialog and if unlink method throws UserError then it will display UserError dialog above confirm dialog and closing UserError dialog and clicking on OK button in confirn dialig will again open UserError dialog, so to avoid this situation close confirm dialog when error occurs. TASK 2221075 Fixes https://github.com/odoo/odoo/issues/59688 Closes https://github.com/odoo/odoo/issues/59688 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Steps: - Go to "Website" > "Go to Website" - Click Edit - Add an image gallery - Add an image to the gallery - Add the same image to the gallery - Click the first image - Click "Image Cover" in the side panel - Click on the Link button in the bottom-right of the side panel - Add a link and save Bug: The first image is not displayed in the same way as the second one. Explanation: The layout is not carried over to `img` when it's nested into an `a` tag. Redefining the layout on th
Original PR description
Steps: - Go to "Website" > "Go to Website" - Click Edit - Add an image gallery - Add an image to the gallery - Add the same image to the gallery - Click the first image - Click "Image Cover" in the side panel - Click on the Link button in the bottom-right of the side panel - Add a link and save Bug: The first image is not displayed in the same way as the second one. Explanation: The layout is not carried over to `img` when it's nested into an `a` tag. Redefining the layout on the `a` tag fixes the issue. opw:2394953 Forward-Port-Of: odoo/odoo#63675
1) create a storable product with category costing method FIFO and inventory valuation automated 2) Make a subcontracting type bill of material for this product and set the vendor 3) Create the purchase order for this product 4) Receive the product 5) Create a vendor bill with a landed cost product and create the landed costs 6) On the landed cost entry, you are not able to select the receipt transfer for the subcontracted product This occur because during 3) the stock moves for the
Original PR description
1) create a storable product with category costing method FIFO and inventory valuation automated 2) Make a subcontracting type bill of material for this product and set the vendor 3) Create the purchase order for this product 4) Receive the product 5) Create a vendor bill with a landed cost product and create the landed costs 6) On the landed cost entry, you are not able to select the receipt transfer for the subcontracted product This occur because during 3) the stock moves for the product are created, but the picking is not recorded on the finished move (but on the receipt move) At thep 6) the system will look for candidate moves which have an associated picking, so it will not find the entry opw-2380634 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#62633
Forward-Port-Of: odoo/odoo#63716 Forward-Port-Of: odoo/odoo#63676
Original PR description
Forward-Port-Of: odoo/odoo#63716 Forward-Port-Of: odoo/odoo#63676
Steps to reproduce the bug: - Install Accounting, Sales, Project and Timesheet apps - Enable Analytic accounting in Accounting settings - Uninstall Timesheet app - Try to create an analytic account Bug: An error was raised because the field project_id didn't exist on model account.analytic.line opw:2420177 Forward-Port-Of: odoo/odoo#63687
Original PR description
Steps to reproduce the bug: - Install Accounting, Sales, Project and Timesheet apps - Enable Analytic accounting in Accounting settings - Uninstall Timesheet app - Try to create an analytic account Bug: An error was raised because the field project_id didn't exist on model account.analytic.line opw:2420177 Forward-Port-Of: odoo/odoo#63687
Before this commit, some notifications in mail were not following the changes made in odoo/odoo#52826 . task-2278579 Forward-Port-Of: odoo/odoo#63614
Original PR description
Before this commit, some notifications in mail were not following the changes made in odoo/odoo#52826 . task-2278579 Forward-Port-Of: odoo/odoo#63614
PURPOSE All fixes and last improvements are not correctly forward ported in 14.1 and master. Let us clean and forward everything. Channel tests are partially cleaned and improved, notably to add test users and improve code readability. Manual forward port of odoo/odoo@eda542 Manual forward port of odoo/odoo@340f6ba Contain some additional fixes. See sub commits for more details. LINKS Task ID-2421795 COM PR odoo/odoo#63677 Forward-Port-Of: odoo/odoo#63677
Original PR description
PURPOSE All fixes and last improvements are not correctly forward ported in 14.1 and master. Let us clean and forward everything. Channel tests are partially cleaned and improved, notably to add test users and improve code readability. Manual forward port of odoo/odoo@eda542 Manual forward port of odoo/odoo@340f6ba Contain some additional fixes. See sub commits for more details. LINKS Task ID-2421795 COM PR odoo/odoo#63677 Forward-Port-Of: odoo/odoo#63677
Description of the issue/feature this PR addresses: Erroneous next invoice number Current behavior before PR: When calculating the last used invoice number, vendor bills are evaluated Desired behavior after PR is merged: The query where is modified in order to exclude 'in' move_types -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#63611
Original PR description
Description of the issue/feature this PR addresses: Erroneous next invoice number Current behavior before PR: When calculating the last used invoice number, vendor bills are evaluated Desired behavior after PR is merged: The query where is modified in order to exclude 'in' move_types -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#63611
Steps to reproduce the bug: - Go to Accounting > Customers > Batch Payments - Try to create a batch payment Bug: The field journal_id was in readonly opw:2417673 Forward-Port-Of: odoo/enterprise#15401
Original PR description
Steps to reproduce the bug: - Go to Accounting > Customers > Batch Payments - Try to create a batch payment Bug: The field journal_id was in readonly opw:2417673 Forward-Port-Of: odoo/enterprise#15401
What are the steps to reproduce your issue ? 1. Install "helpdesk" 2. Create new ticket with customer name, customer email (valid emal like xyz@xyz.com) and no customer 3. Save What is currently happening ? The system create new contact with customer email in customer name field What are you expecting to happen ? The system create new contact with correct mail and correct name Why is this happening ? because there was a check that verified if "partn
Original PR description
What are the steps to reproduce your issue ?
1. Install "helpdesk"
2. Create new ticket with customer name, customer email (valid emal like xyz@xyz.com) and no customer
3. Save
What is currently happening ?
The system create new contact with customer email in customer name field
What are you expecting to happen ?
The system create new contact with correct mail and correct name
Why is this happening ?
because there was a check that verified if "partner_id" was in the
'vals' to know if a partner was specified or not in the ticket creation,
except that even when the partner_id was not specified in the records,
it was in the 'vals', but had a value of 'False'
How to fix the bug ?
Instead of checking if "partner_id" is in 'vals', check that it is not equal to 'False'
opw-2412224
Forward-Port-Of: odoo/enterprise#15378
Forward-Port-Of: odoo/enterprise#15366What are the steps to reproduce your issue ? 1. Install 'mrp' 2. Set a work instruction on a WO Operation 3. Create a MO with that operation 4. Enter WO 5. Scroll to page bigger than 1 6. Pause the WO What is currently happening ? Once the WO is paused or continued again, the PDF renders back to page 1 What are you expecting to happen ? The pdf should remain on same page opw-2418609 Forward-Port-Of: odoo/enterprise#15399
Original PR description
What are the steps to reproduce your issue ?
1. Install 'mrp'
2. Set a work instruction on a WO Operation
3. Create a MO with that operation
4. Enter WO
5. Scroll to page bigger than 1
6. Pause the WO
What is currently happening ?
Once the WO is paused or continued again, the PDF renders back to page 1
What are you expecting to happen ?
The pdf should remain on same page
opw-2418609
Forward-Port-Of: odoo/enterprise#15399