Saturday, September 18, 2021
12 changes · master
Miscellaneous changes
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#76642
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#76642
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#76680
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#76680
Bug introduced by this commit: https://github.com/odoo/odoo/commit/f05db8b122140a9d0f124484ab22eb094b4e36e9 Steps to reproduce the bug: - create a journal entry with 4 ”account.move.line”: - two `”account.move.line”` with accounts of type ('receivable' or 'payable') > with the amount of both in debit or both in credit - two `”account.move.line”` with accounts other than the type ('receivable' or 'payable') - save - duplicate the `“account.move”` - validation error will be trigge
Original PR description
Bug introduced by this commit: https://github.com/odoo/odoo/commit/f05db8b122140a9d0f124484ab22eb094b4e36e9
Steps to reproduce the bug:
- create a journal entry with 4 ”account.move.line”:
- two `”account.move.line”` with accounts of type ('receivable' or 'payable') > with the amount of both in debit or both in credit
- two `”account.move.line”` with accounts other than the type ('receivable' or 'payable')
- save
- duplicate the `“account.move”`
- validation error will be triggered: https:github.com/odoo/odoo/blob/14.0/addons/account/models/account_move.py#L3209-L3211
Problem:
The payment terms must be recomputed only if the `”account.move”` is an invoice
OPW-2642826
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#76728
Forward-Port-Of: odoo/odoo#76655Bug introduced here: #74842 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76674
Original PR description
Bug introduced here: #74842 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76674
When making a payment intent from Adyen terminal with the POS, the payment intent was validated by Adyen but Odoo stopped polling because a connection failure happened. With this fix we use the remaining_polls already implemented to get the adyen status with a interval of 3 secondes. If after 3 tries of 3 seconds each it still fails we can retry manually. Related to dcb1e2b4823c917f4c547d2cad604187f893948d and f83d1b13a96f8df559918b5905b949009d2ece88 opw:2587625 Description of the is
Original PR description
When making a payment intent from Adyen terminal with the POS, the payment intent was validated by Adyen but Odoo stopped polling because a connection failure happened. With this fix we use the remaining_polls already implemented to get the adyen status with a interval of 3 secondes. If after 3 tries of 3 seconds each it still fails we can retry manually. Related to dcb1e2b4823c917f4c547d2cad604187f893948d and f83d1b13a96f8df559918b5905b949009d2ece88 opw:2587625 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#76705 Forward-Port-Of: odoo/odoo#76481
*website, website_form_project In master, there was an error when adding a form to a website and selecting "Create a Task" with no active projects. This issue was solved in PR #73269, by allowing tasks without a project associated. This introduces a new problem: if a user wants to create a project (e.g. if there is no active project), they will have to save their changes, close the editor, navigate to Project, and only then will they be able to do it. This issue could happen for other m
Original PR description
*website, website_form_project In master, there was an error when adding a form to a website and selecting "Create a Task" with no active projects. This issue was solved in PR #73269, by allowing…
*website, website_form_project In master, there was an error when adding a form to a website and selecting "Create a Task" with no active projects. This issue was solved in PR #73269, by allowing tasks without a project associated. This introduces a new problem: if a user wants to create a project (e.g. if there is no active project), they will have to save their changes, close the editor, navigate to Project, and only then will they be able to do it. This issue could happen for other modules, so the solution has to be generic. In this commit, we add the possibility to add a button to the form editor, next to a we-select item, which will redirect the user to a specified action after prompting them to save their work. This button can be added by specifying an action window in the corresponding registry. We also add the action window to the website form project editor, so that the user can be redirected towards the Project app if they want to create a project to select in their form. task-2580436 Forward-Port-Of: odoo/odoo#73241
- Configure payment stripe to be available on the web shop - Let's consider a product with P (sales price = 100€) invoice policy based on delivered qty - Set in the config parameter sale.automatic_invoice to True - Create a SO with P and generate a payment link PL for 50€ - Go to PL and pay it Bug: An error was raised because there was no invoicable line when computing the invoice of SO opw:2635175 Forward-Port-Of: odoo/odoo#76635 Forward-Port-Of: odoo/odoo#75892
Original PR description
- Configure payment stripe to be available on the web shop - Let's consider a product with P (sales price = 100€) invoice policy based on delivered qty - Set in the config parameter sale.automatic_invoice to True - Create a SO with P and generate a payment link PL for 50€ - Go to PL and pay it Bug: An error was raised because there was no invoicable line when computing the invoice of SO opw:2635175 Forward-Port-Of: odoo/odoo#76635 Forward-Port-Of: odoo/odoo#75892
Description of the issue/feature this PR addresses: Fix a singleton error when passing a list of value dictionaries to forum.forum's create method that occurs because `_set_default_faq` is called on the result of the model's create-multi: https://github.com/odoo/odoo/blob/master/addons/website_forum/models/forum.py#L197. Current behavior before PR: Singleton error occurs when passing a list of value dictionaries to forum.forum's create method Desired behavior after PR is merged: No sing
Original PR description
Description of the issue/feature this PR addresses: Fix a singleton error when passing a list of value dictionaries to forum.forum's create method that occurs because `_set_default_faq` is called on the result of the model's create-multi: https://github.com/odoo/odoo/blob/master/addons/website_forum/models/forum.py#L197. Current behavior before PR: Singleton error occurs when passing a list of value dictionaries to forum.forum's create method Desired behavior after PR is merged: No singleton error occurs when passing a list of value dictionaries to forum.forum's create method -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#76463
PR #75856 introduced a default implementation of group_expand for Selection fields that set the value of group_expand to True. However the PR lacked the necessary bits that allow the same behavior for fields created on the fly instead of through code. This commit allows the propagation of the group_expand attribute for fields of type Selection, this commit also exposes the checkbox in the UI to enable/disable the setting. Forward-Port-Of: odoo/odoo#76592
Original PR description
PR #75856 introduced a default implementation of group_expand for Selection fields that set the value of group_expand to True. However the PR lacked the necessary bits that allow the same behavior for fields created on the fly instead of through code. This commit allows the propagation of the group_expand attribute for fields of type Selection, this commit also exposes the checkbox in the UI to enable/disable the setting. Forward-Port-Of: odoo/odoo#76592
Until now easypost treated all messages as errors even when it wasn't This fix adds a whitelisted messages field which will not raises error. opw-2563571 Forward-Port-Of: odoo/enterprise#20918
Original PR description
Until now easypost treated all messages as errors even when it wasn't This fix adds a whitelisted messages field which will not raises error. opw-2563571 Forward-Port-Of: odoo/enterprise#20918
Forward-Port-Of: odoo/enterprise#20947
Original PR description
Forward-Port-Of: odoo/enterprise#20947
Forward-Port-Of: odoo/enterprise#20982
Original PR description
Forward-Port-Of: odoo/enterprise#20982