Wednesday, December 16, 2020
20 changes · master
Enhancements to existing features
The testing rules for Odoo’s JavaScript code now align with the browsers currently supported by Odoo 14 and later. This allows teams to use newer browser capabilities already present in Odoo while dropping checks aimed at outdated Edge and older iOS versions.
Original PR description
This reverts commit d431f94c759f9811c640d81a274e90301276d001 and even upgrade the EcmaScript version further to ES10/2019. The original commit mainly targeted the support of MS Edge (pre-Chromium)…
This reverts commit d431f94c759f9811c640d81a274e90301276d001 and even upgrade the EcmaScript version further to ES10/2019. The original commit mainly targeted the support of MS Edge (pre-Chromium) and earlier versions of iOS 11. As with the release of Odoo 14, we don't support either of those (MS Edge only Chromium-based and iOS 12), the original restriction can be lifted and again target EcmaScript 9/2018. But furthermore, some features of ES10/2019 are already in use in Odoo 14+ (e.g. `Object.fromEntries()` used in SpreadSheet, PoS, WebEditor, Website Sale...) and the only browser not supporting them is Safari on iOS versions < 12.2. As there is no drop of supported devices between iOS 11 and 12 and they all have access to - at least - the latest revision of iOS 12 (cf. 12.5), it looks reasonable to target the latest revision only and not the earlier ones. This policy also matches the "ever-green-browsers" policy applied on desktop. Note: please note that the tool (es-check) used for testing the EcmaScript version targeted has for primary goal to catch unsupported syntax and reserved keywords only, but not the actual APIs available for a given EcmaScript version. (e.g. async/await keywords or string literals are tested *but not* Object.fromEntries() or Array.prototype.flatMap()). References: - https://kangax.github.io/compat-table/es2016plus/ - https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/fromEntries - https://en.wikipedia.org/wiki/IOS_12
Miscellaneous changes
1) Extra Items Issue: Adding an extra to one menu item, automatically adds it to the other food items in the same order. Expected Behavior: When adding an extra, it should only be associated to the food item for which it was selected, and NOT applied to the other ordered items. For example, if I select a "Ranch" dressing for the "Chef Salad", the ranch should not appear as an extra for the "Cheeseburger" or "Cookie of the Day". 2) Unable to Submit Certain Orders
Original PR description
1) Extra Items Issue: Adding an extra to one menu item, automatically adds it to the other food items in the same order. Expected Behavior: When adding an extra, it should only be associated to the…
1) Extra Items
Issue: Adding an extra to one menu item, automatically adds it to the other food items in the same order.
Expected Behavior: When adding an extra, it should only be associated to
the food item for which it was selected, and NOT applied to the other ordered items.
For example, if I select a "Ranch" dressing for the "Chef Salad",
the ranch should not appear as an extra for the "Cheeseburger" or "Cookie of the Day".
2) Unable to Submit Certain Orders
Issue: Odoo prevents the user from submitting an order in the following case
(better illustrated through an example). If you select a "Chef Salad", you will be prompted to select a "Dressing Choice",
because the configuration is set to select one and only one extra.
You cannot add the salad to the cart without selecting a dressing,
nor can you proceed if you have more than one dressing selected;
this is functioning as expected. The problem, however, comes when you
select a dressing and add the salad to the cart, and now you try to add a
dressing as its own order item (separate from any salad). Even though the
salad has its own dressing selected, and the separate dressing is its own item,
the error message: "You have to order one and only one Dressing choice" appears and
prevents the order from being submitted. This issue may be a consequence of the behavior observed in the first issue.
Expected Behavior: The user should be able to submit the order in
this case because the salad had only one dressing associated with it,
and the extra dressing is supposed to be its own item.
This should not create a conflict with the "only one" extra logic.
Step to reproduce (video: edv)
Reproducible on runbot.
1) Extra Items
https://drive.google.com/file/d/1yos9coFqd55pq8qNbNs1OqGNMNSdgxDX/view
2) Unable to Submit Certain Orders
https://drive.google.com/file/d/1M0ZEElu-hYwU9bmCwEx_tqEZRAPG_UEt/view
opw-2391070
Forward-Port-Of: odoo/odoo#63228temp Forward-Port-Of: odoo/odoo#63366
Original PR description
temp Forward-Port-Of: odoo/odoo#63366
Steps to reproduce the bug: - Let's consider a company C with l10n_ch installed - Try to create a vendor bill Bug: A traceback was raised. PS: Function _is_qr_iban has an ensure_one and when creating a vendor bill the function _is_qr_iban by _compute_l10n_ch_isr_needs_fixing was called with no partner_bank opw:2416809 Forward-Port-Of: odoo/odoo#63424
Original PR description
Steps to reproduce the bug: - Let's consider a company C with l10n_ch installed - Try to create a vendor bill Bug: A traceback was raised. PS: Function _is_qr_iban has an ensure_one and when creating a vendor bill the function _is_qr_iban by _compute_l10n_ch_isr_needs_fixing was called with no partner_bank opw:2416809 Forward-Port-Of: odoo/odoo#63424
Steps: - Go to "Website" > "Go to Website" - Click Edit - Add an image gallery - Add an image to the gallery - Click the image - Click on the Link button in the bottom-right of the side panel - Add a link and save Bug: The image is too large. Explanation: The flex layout is not carried over to `img` when it's nested into an `a` tag. Redefining the flex layout on the `a` tag fixes the issue. This fixes portrait images: ```css height: 100%; width: 100%; ``` And adding this
Original PR description
Steps: - Go to "Website" > "Go to Website" - Click Edit - Add an image gallery - Add an image to the gallery - Click the image - Click on the Link button in the bottom-right of the side panel - Add a link and save Bug: The image is too large. Explanation: The flex layout is not carried over to `img` when it's nested into an `a` tag. Redefining the flex layout on the `a` tag fixes the issue. This fixes portrait images: ```css height: 100%; width: 100%; ``` And adding this also fixes landscape and smaller images: ```css display: flex; ``` opw:2394953 Forward-Port-Of: odoo/odoo#63364
Before that, that field was located under "Outgoing payment", which made no sense. Forward-Port-Of: odoo/odoo#63432
Original PR description
Before that, that field was located under "Outgoing payment", which made no sense. Forward-Port-Of: odoo/odoo#63432
Before this commit, an event listener was still active after the removal of the attachment viewer, which caused the the onLoad function to be called on an removed component if the component was unmounted before the image was loaded. part of task-2363522 Forward-Port-Of: odoo/odoo#61560
Original PR description
Before this commit, an event listener was still active after the removal of the attachment viewer, which caused the the onLoad function to be called on an removed component if the component was unmounted before the image was loaded. part of task-2363522 Forward-Port-Of: odoo/odoo#61560
This was the case before the refactoring. task-2411114 Forward-Port-Of: odoo/odoo#62942
Original PR description
This was the case before the refactoring. task-2411114 Forward-Port-Of: odoo/odoo#62942
To reproduce this issue, install the module "Accounting" in English, then switch language to Dutch, and go to a user's form. The selection field for accounting groups is missing from the users' form view. The source of the bug is the special case introduced for accounting groups in d8c5cc1335806d379134866262840fcafb05b643. The groups in that selection field are not totally ordered, and the non-ordered elements are de facto ordered by name, which is a translated field! In the example
Original PR description
To reproduce this issue, install the module "Accounting" in English, then switch language to Dutch, and go to a user's form. The selection field for accounting groups is missing from the users' form…
To reproduce this issue, install the module "Accounting" in English, then switch language to Dutch, and go to a user's form. The selection field for accounting groups is missing from the users' form view. The source of the bug is the special case introduced for accounting groups in d8c5cc1335806d379134866262840fcafb05b643. The groups in that selection field are not totally ordered, and the non-ordered elements are de facto ordered by name, which is a translated field! In the example above, the English version uses the field name `sel_groups_22_23_24_25` while the Dutch version uses the field name `sel_groups_23_22_24_25`. Because the first one is used in the form view, and it is not found in the model's documented fields (which uses the second one), the field is discarded from the view. The patch modifies the override of method `fields_get()` to consider all the possible names for that selection field, and returns them all. OPW-2394209 Forward-Port-Of: odoo/odoo#63423
Currently, scheduling the activity from the document chatter does not appear on the kanban record on activity button. and the 'onchange' action receives the ID of the activity that was marked as done and thus the 'Missing record' error So in this commit, on creation and done of activity reload the view to update the record on kanban card. The opportunity is taken to make a pass on all of the "reload" to add the `keepChanges` flag to prevent from losing pending changes on reload, espec
Original PR description
Currently, scheduling the activity from the document chatter does not appear on the kanban record on activity button. and the 'onchange' action receives the ID of the activity that was marked as done and thus the 'Missing record' error So in this commit, on creation and done of activity reload the view to update the record on kanban card. The opportunity is taken to make a pass on all of the "reload" to add the `keepChanges` flag to prevent from losing pending changes on reload, especially useful in form view. TaskID: 2362964 Forward-Port-Of: odoo/odoo#60397
This reverts commit 7e3e99adb4d8d25b74984bcfff67003d8f096d73. Usability of that new wizard was too poor. We revert it for now; it'll make a comeback eventually. For the record, it was asked by @avw-odoo , and discussed with @qdp-odoo and @nseinlet . We decided to make an exception to the fact 14.1 is normally frozen. Forward-Port-Of: odoo/odoo#63425
Original PR description
This reverts commit 7e3e99adb4d8d25b74984bcfff67003d8f096d73. Usability of that new wizard was too poor. We revert it for now; it'll make a comeback eventually. For the record, it was asked by @avw-odoo , and discussed with @qdp-odoo and @nseinlet . We decided to make an exception to the fact 14.1 is normally frozen. Forward-Port-Of: odoo/odoo#63425
STEPS: * create a recurring event: * date: now() - 8 weeks * time: now() + 1 hour + 3 minutes * Repeat every 1 week, until "now() + 8 weeks" * Reminders: "Notification-1 hour", "Email-1 hour", "SMS-1 hour" * wait 3 minutes * Run manually cron "Calendar: Event Reminder" * Wait 0-5 minutes * Check menu ``[[ Settings ]] >> Technical >> Discuss >> Messages`` * Check menu ``[[ Settings ]] >> Technical >> Phone / SMS >> SMS`` BEFORE: you get mail/sms/UI notifications for all p
Original PR description
STEPS: * create a recurring event: * date: now() - 8 weeks * time: now() + 1 hour + 3 minutes * Repeat every 1 week, until "now() + 8 weeks" * Reminders: "Notification-1 hour", "Email-1 hour", "SMS-1…
STEPS: * create a recurring event: * date: now() - 8 weeks * time: now() + 1 hour + 3 minutes * Repeat every 1 week, until "now() + 8 weeks" * Reminders: "Notification-1 hour", "Email-1 hour", "SMS-1 hour" * wait 3 minutes * Run manually cron "Calendar: Event Reminder" * Wait 0-5 minutes * Check menu ``[[ Settings ]] >> Technical >> Discuss >> Messages`` * Check menu ``[[ Settings ]] >> Technical >> Phone / SMS >> SMS`` BEFORE: you get mail/sms/UI notifications for all passed dates AFTER: you get mail/sms/UI notifications only for the comming event WHY: in v13.0-, recurring calendar.event records were virtual, so _get_occurrences was used to generate those virtual records. In Odoo v14+ it's not needed --- opw-2389877 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#62701
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#63457
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#63457
Fine tuning of this commit: https://github.com/odoo/odoo/commit/6e374e25943106be84711233f3960f2f3a4b9aa9 To fix the issue when l10n_ch_qriban is not installed opw:2416809 Forward-Port-Of: odoo/odoo#63467 Forward-Port-Of: odoo/odoo#63453
Original PR description
Fine tuning of this commit: https://github.com/odoo/odoo/commit/6e374e25943106be84711233f3960f2f3a4b9aa9 To fix the issue when l10n_ch_qriban is not installed opw:2416809 Forward-Port-Of: odoo/odoo#63467 Forward-Port-Of: odoo/odoo#63453
This reverts commit b929c899f921da13bb1b06a1a272895cc71fce29. The company_id field wasn't storable, so the constraint is disabled. Forward-Port-Of: odoo/enterprise#15339 Forward-Port-Of: odoo/enterprise#15337
Original PR description
This reverts commit b929c899f921da13bb1b06a1a272895cc71fce29. The company_id field wasn't storable, so the constraint is disabled. Forward-Port-Of: odoo/enterprise#15339 Forward-Port-Of: odoo/enterprise#15337
[FIX] sign: Download signed PDF even with several signatures What are the steps to reproduce your issue ? 1. Install "sign" 2. Create a request with a new template 3. Add two signatures with two person (Azure Interior and Deco Addict for example) 4. Send request 5. Check the first mail request and sign 6. Try to download PDF What is currently happening ? A password will be requested for the first person trying to download PDF And the document wil
Original PR description
[FIX] sign: Download signed PDF even with several signatures What are the steps to reproduce your issue ? 1. Install "sign" 2. Create a request with a new template 3. Add two signatures with two…
[FIX] sign: Download signed PDF even with several signatures
What are the steps to reproduce your issue ?
1. Install "sign"
2. Create a request with a new template
3. Add two signatures with two person (Azure Interior and Deco Addict for example)
4. Send request
5. Check the first mail request and sign
6. Try to download PDF
What is currently happening ?
A password will be requested for the first person trying to download PDF
And the document will not be up to date for all other signers
if that the first signer downloaded the document before it is fully signed.
What are you expecting to happen ?
Do not ask for the password if the PDF is not encrypted
Why is this happening ?
A password is requested if the document data is not complete.
The data is complete when all people have signed. But when requesting
to download the pdf all the people have not yet finished signing and
therefore the data is not complete, which means a password request
How to fix the bug ?
Request a password only if there is no data after all people have signed
In case the person wants to download after signing the document but he is not the only signer.
Generate the pdf so that he has access to the latest version.
opw-2390906
Forward-Port-Of: odoo/enterprise#15333
Forward-Port-Of: odoo/enterprise#15095before this commit, - scheduling the activity from the document chatter does not appear on the kanban activity button. - favorite and activity button display outside the kanban record when the document chatter is opened. after this commit, - scheduling the activity on the document chatter will appear on the kanban activity button. - favorite and activity button will not appear outside the kanban record. The opportunity is taken to make a pass on all of the "reload" to add the `keep
Original PR description
before this commit, - scheduling the activity from the document chatter does not appear on the kanban activity button. - favorite and activity button display outside the kanban record when the document chatter is opened. after this commit, - scheduling the activity on the document chatter will appear on the kanban activity button. - favorite and activity button will not appear outside the kanban record. The opportunity is taken to make a pass on all of the "reload" to add the `keepChanges` flag to prevent from losing pending changes on reload, especially useful in form view. TaskID - 2362964 Forward-Port-Of: odoo/enterprise#14235
Issue On archiving a product having some quantities and value, in the "Warehouse Analysis" dashboard, "Inventory value" gets decreased. Solution Include archived products in "Warehouse Analysis" dashboard. opw-2409542 Forward-Port-Of: odoo/enterprise#15329
Original PR description
Issue On archiving a product having some quantities and value, in the "Warehouse Analysis" dashboard, "Inventory value" gets decreased. Solution Include archived products in "Warehouse Analysis" dashboard. opw-2409542 Forward-Port-Of: odoo/enterprise#15329
Some assets can be encoded with very long names. While cutting them in the html report is fine, we want to display them entirely in the exported files, otherwise it makes them worthless. Forward-Port-Of: odoo/enterprise#15325
Original PR description
Some assets can be encoded with very long names. While cutting them in the html report is fine, we want to display them entirely in the exported files, otherwise it makes them worthless. Forward-Port-Of: odoo/enterprise#15325
This commit adds a name to the generation.simulation.link email. Previous behaviour : The title of the mail was : 'generation.simulation.link,%d' % wizard.id. Expected behaviour : The title of the mail is the name of the employee if set, and of the applicant if not set. Task-2377814 Forward-Port-Of: odoo/enterprise#15250
Original PR description
This commit adds a name to the generation.simulation.link email. Previous behaviour : The title of the mail was : 'generation.simulation.link,%d' % wizard.id. Expected behaviour : The title of the mail is the name of the employee if set, and of the applicant if not set. Task-2377814 Forward-Port-Of: odoo/enterprise#15250