Monday, July 20, 2020
12 changes · master
Enhancements to existing features
Email templates now include the database name when loading the company logo, helping Odoo choose the right company branding. This prevents recipients from seeing the default Odoo logo in cases where the system could not identify the correct database or company automatically.
Original PR description
Task Link: https://www.odoo.com/web#id=1889370&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.d71047d940568b9151eb9511c4f54278 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Email templates now include the database name when loading the company logo. This helps Odoo reliably show the correct company branding instead of falling back to the default Odoo logo in multi-database or ambiguous situations.
Original PR description
Task Link: https://www.odoo.com/web#id=1889370&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad Link: https://pad.odoo.com/p/r.d71047d940568b9151eb9511c4f54278
Resolved issues and error corrections
A small documentation formatting issue was fixed so the online reference displays list items correctly. This helps readers avoid confusion when consulting view documentation, with no impact on product behavior.
Miscellaneous changes
There is no field 'ids' on a gamification.goal, but one called 'id' Fixes odoo/odoo#25913 Forward-Port-Of: odoo/odoo#54363
Original PR description
There is no field 'ids' on a gamification.goal, but one called 'id' Fixes odoo/odoo#25913 Forward-Port-Of: odoo/odoo#54363
When the server execute the job 'Mail: Fetchmail Service' if it's processed an attachment having a Notes field with None values the following traceback will occur AttributeError: 'NoneType' object has no attribute 'split' //IdentificativoSdI','//DataOraRicezione','//Descrizione','//MessageId','//Note'. seems to be not mandatory opw-2277722 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54591
Original PR description
When the server execute the job 'Mail: Fetchmail Service' if it's processed an attachment having a Notes field with None values the following traceback will occur AttributeError: 'NoneType' object has no attribute 'split' //IdentificativoSdI','//DataOraRicezione','//Descrizione','//MessageId','//Note'. seems to be not mandatory opw-2277722 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54591
Issue is specifically in the case of an onchange removing a record in an o2m in an o2m (so a sub-o2m) if loading an *existing* record in the SSF: since the server pretty much only returns a REMOVE_ALL followed by the records to keep or create, conserving the removal information requires diffing the value currently stored in the form and the result fo the onchange. Diff which was properly done for top-level o2ms, but not for the ones below that (apparently forgot this bit when improving
Original PR description
Issue is specifically in the case of an onchange removing a record in an o2m in an o2m (so a sub-o2m) if loading an *existing* record in the SSF: since the server pretty much only returns a REMOVE_ALL followed by the records to keep or create, conserving the removal information requires diffing the value currently stored in the form and the result fo the onchange. Diff which was properly done for top-level o2ms, but not for the ones below that (apparently forgot this bit when improving support for nested o2ms earlier this year). Forward-Port-Of: odoo/odoo#54655 Forward-Port-Of: odoo/odoo#54642
Description of the issue/feature this PR addresses: Related to the documentation https://www.odoo.com/documentation/13.0/howtos/backend.html#default-values The comment note states "Odoo has built-in rules making fields with an active field set to False invisible." It should be "Odoo has built-in rules making **records** with an active field set to False invisible." Current behavior before PR: Incorrect documentation Desired behavior after PR is merged: Documentation fixed -- I
Original PR description
Description of the issue/feature this PR addresses: Related to the documentation https://www.odoo.com/documentation/13.0/howtos/backend.html#default-values The comment note states "Odoo has built-in rules making fields with an active field set to False invisible." It should be "Odoo has built-in rules making **records** with an active field set to False invisible." Current behavior before PR: Incorrect documentation Desired behavior after PR is merged: Documentation fixed -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#54701
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#54575
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#54575
Bank reconciliation widget allows creating a writeoff with tax lines, in order to simulate both the invoice and the payment into a single entry, from one statement line. Before this fix, the tax repartition used by this feature was always the one defined for invoices. Also, in some cases, the amounts reported in the tax report had the wrong sign, because of the way the tax report applies the sign multiplicator on lines' balances. This multiplicator cannot be computed properly from a payment or m
Original PR description
Bank reconciliation widget allows creating a writeoff with tax lines, in order to simulate both the invoice and the payment into a single entry, from one statement line. Before this fix, the tax…
Bank reconciliation widget allows creating a writeoff with tax lines, in order to simulate both the invoice and the payment into a single entry, from one statement line. Before this fix, the tax repartition used by this feature was always the one defined for invoices. Also, in some cases, the amounts reported in the tax report had the wrong sign, because of the way the tax report applies the sign multiplicator on lines' balances. This multiplicator cannot be computed properly from a payment or miscellaneous operation, so we need to rather impact the sign of the tags directly. With this fix, we guess whether or not we are refunding something from the data entered by the user, and modify the signs of the tags accordingly so that the tax has the same impact on the report as it would have had with an invoice doing the same operation. 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#54639 Forward-Port-Of: odoo/odoo#54070
The tags are not copied on the bank reconciliation widget when making a manual line with tax. Forward-Port-Of: odoo/enterprise#11943
Original PR description
The tags are not copied on the bank reconciliation widget when making a manual line with tax. Forward-Port-Of: odoo/enterprise#11943
When the OCR try to applies the values to an invoice, it searches for an existing tax. This search must take the company into account, otherwise an AccessError is raised. Bad fw-port, see : #11578 Forward-Port-Of: odoo/enterprise#11932 Forward-Port-Of: odoo/enterprise#11916
Original PR description
When the OCR try to applies the values to an invoice, it searches for an existing tax. This search must take the company into account, otherwise an AccessError is raised. Bad fw-port, see : #11578 Forward-Port-Of: odoo/enterprise#11932 Forward-Port-Of: odoo/enterprise#11916
Forward-Port-Of: odoo/enterprise#11895
Original PR description
Forward-Port-Of: odoo/enterprise#11895