Wednesday, November 4, 2020
25 changes · master
Enhancements to existing features
Notification popups have been redesigned to look simpler and easier to scan. The update removes the icon and separate header, places the title within the message body, and moves action buttons to the bottom for a clearer layout.
Original PR description
Remove the icon of the toaster. Remove the header and move the title in the body. Move buttons at the bottom instead of at the right side. task-2311554 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
Resolved issues and error corrections
Long names and text labels are now shortened with an ellipsis when they do not fit in their display area. This keeps screens across sales, marketing, events, projects, products, contacts, and coupons readable and prevents layout issues caused by unusually long text.
Original PR description
Miscellaneous changes
As the POS doesn't manage CABA entries, don't use the temporary CABA account. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61164 Forward-Port-Of: odoo/odoo#61147
Original PR description
As the POS doesn't manage CABA entries, don't use the temporary CABA account. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61164 Forward-Port-Of: odoo/odoo#61147
[FIX] {base, crm, event, mass_mailing, project, sales_team, utm}: Prevents long texts from overflowing
Previously, in multiple modules, long names would result in an overflow of text.
If applied, this issue should not occur anymore.
The long text should appear like this: [aaaaa...], instead of being like this: [aaaaaa]aaaa.
Task ID: 2325219
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update fixes an issue in the website editor that could affect selecting or positioning content in Safari, especially around shadow styling. It also updates the underlying editor library to improve stability and reduce disruptive automatic recovery behavior when some internal errors occur.
This fixes cases where report styling assets were created incorrectly, such as when a required tool was missing during the first setup. Administrators can now regenerate those report assets from the debug menu, helping restore correct report layouts without deeper technical intervention.
Original PR description
WHY: you may have wrongly compiled assets for reports (e.g. if you didn't have rtlcss installed on first run) 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
Background images in website building blocks now appear centered by default, making pages look better across screen sizes. This especially improves the mobile experience where images could previously appear awkwardly cropped or misaligned.
Original PR description
Before this commit, background images were not centered by default. It was especially annoying on mobile device. We created a new class to center background image and we added it on all the snippets with a background image except those with a parallax effect because they already have a background-position in inline style. task-2318526 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
Contact smart buttons now include records linked to child contacts, including archived child contacts, and open the same complete set when clicked. This makes point of sale and project information shown on a contact more accurate and consistent for users managing company or family contact hierarchies.
Original PR description
Unify the behavior for smart buttons on res.partner view form Let's consider generic records R on a specific model M - All the R of the children and archived children of a contact C must be counted in smart button of M in the form of C - Clicking on the smart button of a contact C must display all R of the children and archived children of C
Long names in Marketing Automation and Social screens are now shortened with an ellipsis so they stay within their display area. This prevents messy layouts and makes records easier to read without text spilling outside boxes.
Original PR description
[FIX] {maketing_automation, social}: Prevents long texts from overflowing
Previously, in multiple modules, long names would result in an overflow of text.
If applied, this issue should not occur anymore.
The long text should appear like this: [aaaaa...], instead of being like this: [aaaaaa]aaaa.
Task ID: 2325219# Purpose When we clear the config parameter crm.pls_fields, it calls the unlink method. So to have a correct dynamic compute based on this parameter we need to re-evaluate the depends. task-2196200 Forward-Port-Of: odoo/odoo#58312
Original PR description
# Purpose When we clear the config parameter crm.pls_fields, it calls the unlink method. So to have a correct dynamic compute based on this parameter we need to re-evaluate the depends. task-2196200 Forward-Port-Of: odoo/odoo#58312
Steps to reproduce the bug: - Go to Fleet > Reporting > Cost - Select the pivot/graph view Bug: The elements in the table/graph were clickable opw:2360528 Forward-Port-Of: odoo/odoo#61279
Original PR description
Steps to reproduce the bug: - Go to Fleet > Reporting > Cost - Select the pivot/graph view Bug: The elements in the table/graph were clickable opw:2360528 Forward-Port-Of: odoo/odoo#61279
Before this commit, when the user dropped the "Quotes" snippet, the editor was not allowing to drop any more snippet (see [1]). This was because the editors initialization related to the drop of the "Quotes" snippet was not able to be fully performed. Indeed, it is composed of carousel items, themself containing images. As some of those carousel items are hidden, the images they contains are too... and some options actually wait to access their `naturalWidth`. As the images are lazy loade
Original PR description
Before this commit, when the user dropped the "Quotes" snippet, the editor was not allowing to drop any more snippet (see [1]). This was because the editors initialization related to the drop of the "Quotes" snippet was not able to be fully performed. Indeed, it is composed of carousel items, themself containing images. As some of those carousel items are hidden, the images they contains are too... and some options actually wait to access their `naturalWidth`. As the images are lazy loaded since [2], we were thus waiting infinitely. [1]: https://github.com/odoo/odoo/commit/277f39904e7218bef2dd23b1c5b719ce8660008f [2]: https://github.com/odoo/odoo/commit/617c716aeafd7bbc776d81da134a9b25329f08c9 Forward-Port-Of: odoo/odoo#61123
Before this commit, once you install website_* module, the ir.actions.todo from the installed module was overidded by the 'choose a theme' action. Now, when we consume this ir_act_todo, we re-open the open_menu that contains most of the time the expected next action from new module installed. Since we can also install module from the '+ new' button, in frontend, we considere that it first step of tour is to click on it, it is already done and we skip it. Install website_event Befor
Original PR description
Before this commit, once you install website_* module, the ir.actions.todo from the installed module was overidded by the 'choose a theme' action. Now, when we consume this ir_act_todo, we re-open…
Before this commit, once you install website_* module, the ir.actions.todo from
the installed module was overidded by the 'choose a theme' action.
Now, when we consume this ir_act_todo, we re-open the open_menu that contains
most of the time the expected next action from new module installed.
Since we can also install module from the '+ new' button, in frontend, we
considere that it first step of tour is to click on it, it is already done and
we skip it.
Install website_event
Before:
-> not redirected to /event (the ir.action.todo)
-> no tour, if you don't click manually on '+ new'
After:
-> you are redirected to /event
-> you can launch tour from '+ new' if you are alrady on the new panel,
start direclty to the second step 'create event'
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#60759Commit [1] made a stupid mistake forgetting nodes with the t-field instruction can also have the position attribute in case of inheritance without xpath node. ... It did not crash because there actually is no case of it in the current codebase, but this is used by some custo on our prod however. The test introduced by mentioned commit has been extended to crash, should this specific case be broken again. [1]: https://github.com/odoo/odoo/commit/92ef3b2dd4655913198d10d06598b799fdcae6d0
Original PR description
Commit [1] made a stupid mistake forgetting nodes with the t-field instruction can also have the position attribute in case of inheritance without xpath node. ... It did not crash because there actually is no case of it in the current codebase, but this is used by some custo on our prod however. The test introduced by mentioned commit has been extended to crash, should this specific case be broken again. [1]: https://github.com/odoo/odoo/commit/92ef3b2dd4655913198d10d06598b799fdcae6d0 Forward-Port-Of: odoo/odoo#61263 Forward-Port-Of: odoo/odoo#61248
In the shop when the product page is loaded, the variants are now selected from search attributes if filter is applied. Since we have a hash containing variants unique id in product url, we can simply apply variants from search filter attributes in url instead of default ones. ISSUE 47117 ISSUE 22982 task-2369420 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 a
Original PR description
In the shop when the product page is loaded, the variants are now selected from search attributes if filter is applied. Since we have a hash containing variants unique id in product url, we can simply apply variants from search filter attributes in url instead of default ones. ISSUE 47117 ISSUE 22982 task-2369420 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#60929
https://github.com/odoo/enterprise/pull/13883 task-2323665 Forward-Port-Of: odoo/odoo#60948
Original PR description
https://github.com/odoo/enterprise/pull/13883 task-2323665 Forward-Port-Of: odoo/odoo#60948
opw-2374318 Forward-Port-Of: odoo/odoo#61309
Original PR description
opw-2374318 Forward-Port-Of: odoo/odoo#61309
A classic payment uses the outstanding account to create the line that needs to be matched later with a statement line. Otherwise, some ppl doesn't want that (e.g. to manage cash transactions) and prefers creating a payment impacting directly the bank account even this payment will never be matched to any statement line. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61059
Original PR description
A classic payment uses the outstanding account to create the line that needs to be matched later with a statement line. Otherwise, some ppl doesn't want that (e.g. to manage cash transactions) and prefers creating a payment impacting directly the bank account even this payment will never be matched to any statement line. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#61059
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#60487
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#60487
Issue - Install "Website" and "website_event" - Try to add Event block The title is editable Cause The contentEditable attribut is enabled Solution Disable the contentEditable attribut opw-2367538 Forward-Port-Of: odoo/odoo#61267
Original PR description
Issue
- Install "Website" and "website_event"
- Try to add Event block
The title is editable
Cause
The contentEditable attribut is enabled
Solution
Disable the contentEditable attribut
opw-2367538
Forward-Port-Of: odoo/odoo#61267When you enable the cash rounding in POS, all your payment methods are rounded in the POS. In some countries, only the cash methods must be rounded, so we enable here the possibility to activate the rounding only on the cash methods. OPW-2373516 and OPW-2366101 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 Forwa
Original PR description
When you enable the cash rounding in POS, all your payment methods are rounded in the POS. In some countries, only the cash methods must be rounded, so we enable here the possibility to activate the rounding only on the cash methods. OPW-2373516 and OPW-2366101 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#61304 Forward-Port-Of: odoo/odoo#61274
Fix the wrong name of start number Forward-Port-Of: odoo/enterprise#14592
Original PR description
Fix the wrong name of start number Forward-Port-Of: odoo/enterprise#14592
A classic payment uses the outstanding account to create the line that needs to be matched later with a statement line. Otherwise, some ppl doesn't want that (e.g. to manage cash transactions) and prefers creating a payment impacting directly the bank account even this payment will never be matched to any statement line. Forward-Port-Of: odoo/enterprise#14502
Original PR description
A classic payment uses the outstanding account to create the line that needs to be matched later with a statement line. Otherwise, some ppl doesn't want that (e.g. to manage cash transactions) and prefers creating a payment impacting directly the bank account even this payment will never be matched to any statement line. Forward-Port-Of: odoo/enterprise#14502
Steps to reproduce the bug: - Export an asset in xls file F - Import F Bug: Impossible to import F because the required field name was impossible to import opw:2374351 Forward-Port-Of: odoo/enterprise#14574
Original PR description
Steps to reproduce the bug: - Export an asset in xls file F - Import F Bug: Impossible to import F because the required field name was impossible to import opw:2374351 Forward-Port-Of: odoo/enterprise#14574
https://github.com/odoo/enterprise/pull/13883 task-2323665 ---- # Forward-Port-Of: odoo/enterprise#14468
Original PR description
https://github.com/odoo/enterprise/pull/13883 task-2323665 ---- # Forward-Port-Of: odoo/enterprise#14468
Issue - Install `Accounting` and `l10n_mx_edi` - Set you company with mexican COA - Go to "Accounting -> Customers -> Payment" - Try to print a payment receipt Traceback raised. Cause - Missing `namespaces` keyword argument in the XPath - `invoice_ids` field does not exist anymore. Solution - Add `namespaces` keyword argument that maps the namespace prefixes used in the XPath. ref: https://lxml.de/xpathxslt.html#namespaces-and-prefixes - Replace `invoice
Original PR description
Issue - Install `Accounting` and `l10n_mx_edi` - Set you company with mexican COA - Go to "Accounting -> Customers -> Payment" - Try to print a payment receipt Traceback raised. Cause - Missing `namespaces` keyword argument in the XPath - `invoice_ids` field does not exist anymore. Solution - Add `namespaces` keyword argument that maps the namespace prefixes used in the XPath. ref: https://lxml.de/xpathxslt.html#namespaces-and-prefixes - Replace `invoice_ids` by `reconciled_invoice_ids` in `report_payment_document_mx` template opw-2369144 Forward-Port-Of: odoo/enterprise#14556