Monday, March 28, 2022
12 changes · master
Enhancements to existing features
The settings page now aligns the displayed version number more consistently with surrounding elements. This small visual polish improves readability and keeps the settings layout looking cleaner without changing functionality.
Original PR description
Technical note: We didn't change ".app_settings_block h3" because it is used all over the place. Instead, we've overridden the margin and padding using bootstrap classes on that specific element. Task-2792977
Features or functions removed from Odoo
The spreadsheet document bundle has been simplified by removing an old headless loading mode that is no longer needed. This reduces internal complexity while keeping normal spreadsheet behavior and update notifications intact for users and integrations.
Original PR description
Modes (normal, headless and readonly) have been introduced in order to be able to load different plugins depending on the mode in which the model is created. "readonly" has been removed because readonly is not as simple as loading or not some plugins. readonly impacts the dispatching of commands. Now, headless can be removed as it was introduced to disable the evaluation at the time where async evaluation was present. As it has been removed, we do not need it anymore. Also, the other difference with normal mode is the triggering of "update" which can be listened from outside. It's not necessary to bypass this trigger. Task-id 2791206
Miscellaneous changes
Purpose ======= Pictures from the digest emails are currently stored on the database itself, meaning that if the database expires (e.g. after trial expires) all pictures from previously sent emails won't be visible. This is an issue since digest tips are meant as a marketing tool to bring people to Odoo after trying a database. Digest pictures are now taken from Odoo's server (https://download.odoocdn.com/digests) so that the pictures will still be visible after the database has exp
Original PR description
Purpose ======= Pictures from the digest emails are currently stored on the database itself, meaning that if the database expires (e.g. after trial expires) all pictures from previously sent emails…
Purpose ======= Pictures from the digest emails are currently stored on the database itself, meaning that if the database expires (e.g. after trial expires) all pictures from previously sent emails won't be visible. This is an issue since digest tips are meant as a marketing tool to bring people to Odoo after trying a database. Digest pictures are now taken from Odoo's server (https://download.odoocdn.com/digests) so that the pictures will still be visible after the database has expired. From this commit onwards, it should not be allowed to change a digest picture with the same name (to display a gif of a newer version), since all databases with previous versions would receive pictures of a version that does not correspond to theirs. This also means that everyone client's Odoo server will contain pictures that are never used. This could be fixed if Odoo stored them somewhere else and didn't make them dependent from the git repository. Task-2372195 Forward-Port-Of: odoo/enterprise#25544
Move linked to an expenses created by the hr expenses module should appear in the reconciliation report, which is not the case at the moment. opw-2790337 Forward-Port-Of: odoo/enterprise#25537 Forward-Port-Of: odoo/enterprise#25428
Original PR description
Move linked to an expenses created by the hr expenses module should appear in the reconciliation report, which is not the case at the moment. opw-2790337 Forward-Port-Of: odoo/enterprise#25537 Forward-Port-Of: odoo/enterprise#25428
Forward-Port-Of: odoo/enterprise#25613
Original PR description
Forward-Port-Of: odoo/enterprise#25613
This commit is the counterpart of a community fix in the web module. The click handler is only triggered once and a phone call will no longer raise an error. A test has been added in the voip module to check that the handler is only called once. PR community: odoo/odoo#86928 Forward-Port-Of: odoo/enterprise#25506
Original PR description
This commit is the counterpart of a community fix in the web module. The click handler is only triggered once and a phone call will no longer raise an error. A test has been added in the voip module to check that the handler is only called once. PR community: odoo/odoo#86928 Forward-Port-Of: odoo/enterprise#25506
Steps to reproduce: - Install accounting - Create more than 6 analytical tags - Create an invoice - Create a payment - Go in Accounting>Actions>Reconciliation, tab Manal Operations - In the field Analytical Tag, click on 'Search More' and selected 1 or multiple tags Issue: Void tags are displayed Solution: Fetch the field `display_name` ref commit: 53d62efbe4647ac01d9a747aaeffabf08b485a54 opw-2734029 Forward-Port-Of: odoo/enterprise#25451 Forward-Port-Of: odoo/enterprise#25247
Original PR description
Steps to reproduce: - Install accounting - Create more than 6 analytical tags - Create an invoice - Create a payment - Go in Accounting>Actions>Reconciliation, tab Manal Operations - In the field Analytical Tag, click on 'Search More' and selected 1 or multiple tags Issue: Void tags are displayed Solution: Fetch the field `display_name` ref commit: 53d62efbe4647ac01d9a747aaeffabf08b485a54 opw-2734029 Forward-Port-Of: odoo/enterprise#25451 Forward-Port-Of: odoo/enterprise#25247
To reproduce ============ - Create two companies - Create tax in each comany with same value (21% for example) - Make invoices in each comany with this tax In tax report with these two companies selected, we notice that the tax 21% has just the value for the displayed company, but when we go in the audit of this tax, we notice that the two records of each company is present. Wanted behavior =============== We want to see the records of all selected companies both on the report
Original PR description
To reproduce ============ - Create two companies - Create tax in each comany with same value (21% for example) - Make invoices in each comany with this tax In tax report with these two companies…
To reproduce ============ - Create two companies - Create tax in each comany with same value (21% for example) - Make invoices in each comany with this tax In tax report with these two companies selected, we notice that the tax 21% has just the value for the displayed company, but when we go in the audit of this tax, we notice that the two records of each company is present. Wanted behavior =============== We want to see the records of all selected companies both on the report and the audit if the system parameter `account_tax_report_multi_company` is set. Otherwise we want to see only the displayed company records on the report and the audit even if multiple companies are selected. Purpose ======= The issue is that while going to the audit the domain doesn't contain a condition on `company_id`. Specification ============= To solve the issue, the condition on `company_id` was added to the domain depending on the system parameter `account_tax_report_multi_company`. opw-2769251 Forward-Port-Of: odoo/enterprise#25617 Forward-Port-Of: odoo/enterprise#25234
Step to reproduce: - Go to website_sale reporting - Use the filter 'Abandoned Cart' Current Behaviour: - To be abandoned, a cart has to be in state draft : https://github.com/odoo/odoo/blob/13.0/addons/website_sale/models/sale_order.py#L48 - To be available in the view, cart has to be confirmed : https://github.com/odoo/enterprise/blob/13.0/website_sale_dashboard/views/dashboard_view.xml#L77 - No possible overlap Behaviour after PR: - Filter is removed opw-2754927 Forward-Por
Original PR description
Step to reproduce: - Go to website_sale reporting - Use the filter 'Abandoned Cart' Current Behaviour: - To be abandoned, a cart has to be in state draft : https://github.com/odoo/odoo/blob/13.0/addons/website_sale/models/sale_order.py#L48 - To be available in the view, cart has to be confirmed : https://github.com/odoo/enterprise/blob/13.0/website_sale_dashboard/views/dashboard_view.xml#L77 - No possible overlap Behaviour after PR: - Filter is removed opw-2754927 Forward-Port-Of: odoo/enterprise#24943
As of now, when getting the partner to assign to bank statement line we look at the online_partner_information but not the company. This means that we could assign a partner from the wrong company to the bank statement line. Forward-Port-Of: odoo/enterprise#25534
Original PR description
As of now, when getting the partner to assign to bank statement line we look at the online_partner_information but not the company. This means that we could assign a partner from the wrong company to the bank statement line. Forward-Port-Of: odoo/enterprise#25534
If applied, this commit will fix the following bug by sending the email to the pool after rollback Steps to reproduce: 1- get amazon synchronization to fail 2- the email informing of the failure is never sent Bug: cursor rollback is happening right after the email is added to pool it never gets the chance to be sent Fix: reverse the order so that the rollback happens first OPW-2790513 Forward-Port-Of: odoo/enterprise#25490
Original PR description
If applied, this commit will fix the following bug by sending the email to the pool after rollback Steps to reproduce: 1- get amazon synchronization to fail 2- the email informing of the failure is never sent Bug: cursor rollback is happening right after the email is added to pool it never gets the chance to be sent Fix: reverse the order so that the rollback happens first OPW-2790513 Forward-Port-Of: odoo/enterprise#25490
Forward-Port-Of: odoo/enterprise#25367
Original PR description
Forward-Port-Of: odoo/enterprise#25367