Tuesday, October 12, 2021
11 changes · master
Enhancements to existing features
Administrators creating a foreign VAT fiscal position now get a direct link to the Apps page when a required localization module is missing. This removes extra navigation steps and helps them install the correct country-specific tax module faster, while non-admin users see the same message as before.
Original PR description
Before, when someone with settings rights created a foreign VAT fiscal position for a country in which there was no tax template yet, a banner was displayed, telling that the right l10n module needed to be installed. However, there was no link to the list of modules, and the user had to go back to the app switcher, then to the Apps menu to install the module he needed. We now display a link to this page, only for the users with setting rights. Other users will still see the same thing as before. Manual forward-port of https://github.com/odoo/odoo/pull/77687
Resolved issues and error corrections
Tax carryover lines are now easier and safer to manage by allowing users to manually adjust their dates while hiding linked report details that should not be edited. This reduces confusion in the accounting workflow and removes an irrelevant restriction that could affect carryover line handling.
Original PR description
- allow editing the date of a carryover line manually - don't display the tax report line the carryover line is linked to anymore, as the user goes through this line to open the carryover line anyway, and it shouldn't be editable. - also remove a domain that made no sense on carryover lines: pointing to a related field depending on the field defining the domain Manual forward-port of https://github.com/odoo/odoo/pull/77718
Miscellaneous changes
In some case, we know that page will contains dynamic content and that cache can be ignored whatever the cachetime. E.g. as soon as a s_snippet_form will be present in page, we know that we need the real csrf, and so we cannot use the cached response from another user. 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
Original PR description
In some case, we know that page will contains dynamic content and that cache can be ignored whatever the cachetime. E.g. as soon as a s_snippet_form will be present in page, we know that we need the real csrf, and so we cannot use the cached response from another user. 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#77602
When calling `_get_signup_url_for_action` on more than one partner, because the `url` input parameter was re-used for the actual signup URL before assigning to the partners map (in 559bdc976e72475a21f6f8d8380e0e4bb3942aae), from the second iteration onwards the signup URL will almost certainly get misgenerated to redirect to the previous signup URL (accumulating). As `signup_url` is not normally accessed in bulk this should not usually be an issue. Reported by Andreas Brückl Forward
Original PR description
When calling `_get_signup_url_for_action` on more than one partner, because the `url` input parameter was re-used for the actual signup URL before assigning to the partners map (in 559bdc976e72475a21f6f8d8380e0e4bb3942aae), from the second iteration onwards the signup URL will almost certainly get misgenerated to redirect to the previous signup URL (accumulating). As `signup_url` is not normally accessed in bulk this should not usually be an issue. Reported by Andreas Brückl Forward-Port-Of: odoo/odoo#78196
 The owl OnboardingBanner component should be full width. 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#78158
Original PR description
 The owl OnboardingBanner component should be full width. 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#78158
Before this commit, a user would be able to drop pretty much any snippet inside the product_catalog (pricelist) snippet. This was not ideal as the snippet wasn't designed to receive any other snippets inside of it. With this commit, the configuration of the snippet is closer to snippets such as timeline, allowing lines to be moved around without allowing snippets to be dropped inside it. task-2655171 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/sub
Original PR description
Before this commit, a user would be able to drop pretty much any snippet inside the product_catalog (pricelist) snippet. This was not ideal as the snippet wasn't designed to receive any other snippets inside of it. With this commit, the configuration of the snippet is closer to snippets such as timeline, allowing lines to be moved around without allowing snippets to be dropped inside it. task-2655171 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#77314
This commit fixes the survey navigation rendering by always returning valid HTML even when no buttons are displayed. Indeed, in some cases, such as on the "thank you" page, we don't display any buttons, meaning that the returned template will be an empty string, which in turn prevents the re-rendering of this part of the page in the JS part of the survey form management. To avoid this issue, we simply add an empty span tag into the template so that the template always returns valid HT
Original PR description
This commit fixes the survey navigation rendering by always returning valid HTML even when no buttons are displayed. Indeed, in some cases, such as on the "thank you" page, we don't display any buttons, meaning that the returned template will be an empty string, which in turn prevents the re-rendering of this part of the page in the JS part of the survey form management. To avoid this issue, we simply add an empty span tag into the template so that the template always returns valid HTML no matter the use case. Task-2642787 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#77534
…devices To avoid the use of certificates when using direct devices POS was redirected in HTTP With new Chrome or Edge security measures this is no longer possible. We add here the possibility to choose to redirect the POS in https by adding a specific key in the parameters 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/
Original PR description
…devices To avoid the use of certificates when using direct devices POS was redirected in HTTP With new Chrome or Edge security measures this is no longer possible. We add here the possibility to choose to redirect the POS in https by adding a specific key in the parameters 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#78154
The new version of firmware-brcm80211 20190114-2+rpt3 are unstable when we use it with the IoT. So we need to keep the original version of the last official version of raspberry-pi OS 20190114-1+rpt11 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#78151
Original PR description
The new version of firmware-brcm80211 20190114-2+rpt3 are unstable when we use it with the IoT. So we need to keep the original version of the last official version of raspberry-pi OS 20190114-1+rpt11 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#78151
The only fields added in `//page[@name='invoicing']//group[@name='accounting']` are `unspsc_code_id`, `intrastat_id` and `email_template_id`, which should all be available with only the rights for invoicing. [opw-2665030](https://www.odoo.com/web#id=2665030&model=project.task) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#78133
Original PR description
The only fields added in `//page[@name='invoicing']//group[@name='accounting']` are `unspsc_code_id`, `intrastat_id` and `email_template_id`, which should all be available with only the rights for invoicing. [opw-2665030](https://www.odoo.com/web#id=2665030&model=project.task) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#78133
Before this commit, it was impossible for a user to invite people to a channel or a group DM. This commit add the invite button on the chat windows header only on mobile. Part of task-2634175 Forward-Port-Of: odoo/odoo#77246
Original PR description
Before this commit, it was impossible for a user to invite people to a channel or a group DM. This commit add the invite button on the chat windows header only on mobile. Part of task-2634175 Forward-Port-Of: odoo/odoo#77246