Odoo Changelog — 2022-10-03

Monday, October 3, 2022

84 changes · master

Improvements(5)

Enhancements to existing features

[IMP] web: Add property list view

CoremasterwebMedium

Property values can now appear as columns in list views, making it easier for users to compare and review custom information without opening each record. These columns are for viewing only and cannot currently be sorted or edited directly from the list.

Original PR description

Adds columns in the list view for properties.

Dynamically create 'fields' for list views
that copy the characteristics of their 'properties' field.
Allows for seamless display of property values in the list view.

Note:
These columns cannot be sorted (requires python ORM modifications)

These columns cannot be edited (not easily achievable)

task #2980121

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#list view#properties#custom fields

[IMP] barcodes{,_gs1_nomenclature}: interpret GS character

PR #99730

Coremasterbarcodesbarcodes_gs1_nomenclatureMedium

Odoo now better recognizes hidden GS1 separator characters used by barcode scanners, including scanner-specific substitutes. This helps prevent lot numbers and quantities from being mixed up when scanning GS1 barcodes on desktop or mobile devices.

Original PR description

Let's say the company uses a GS1 nomenclature and a user scans such a
barcode:
`(01)11111111111113(10)xyz(30)40`
It means a product:
- that has the barcode value '11111111111113'
- for the lot 'xyz'
- with a quantity equal to 40

The GS1 nomenclature explains that a lot consists of a prefix `10` and
of up to 20 alphanumeric characters. In the above example, we could
believe that the lot is actually `xyz3040`. To prevent this kind of
issue, the GS1 standards use a special character: the Group Separator
(its hex value is `\x1d` and does not have any visual representation).
So, when reading the barcode of the above value, the barcode reader will
detect the GS between `z` and `3` (so we know that this is the end of
the lot name).

Because GS has no visual representation, the way the GS character is
given by the scanner to the device depends on the scanner itself. For
instance, some barcode readers try to encode GS thanks to its unicode
input (as used on a Windows device): it enters Alt+0+2+9 (i.e., the
unicode value of GS). This is an issue since we filter out all keydown
events with the `Alt` key pressed.

Also, our way to interpret the barcode value depends on the device: on a
desktop device, we listen the events. As explained above, this could be
an issue (for instance with Alt+029). On a mobile device, we let the
barcode reader write in an hidden input and we then extract the written
value. There is also an issue here: the GS is not present in the
extracted string.

For these reasons, some changes are need. The idea is to let the user
lists the ways his barcode readers will encode the GS character (the
scanners often give the possibility to set a value manually.). There is
already a field for this:
https://github.com/odoo/odoo/blob/320025ee630acadd4a5cbd32f425cddee4f81c1e/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L18-L20

However, this is not correctly working. Suppose we now stop to filter
out the `Alt` keys: in the above example, the scanned value becomes
`011111111111111310xyzAlt0293040`(as you can see, there is an `Alt029`
at the end of the lot). Suppose also that we defined
`gs1_separator_fnc1` with `Alt029`. When parsing the barcode value, we
have:
https://github.com/odoo/odoo/blob/1c0dec6d5813fa81a0fec8668ee13d8036cde5c5/addons/barcodes_gs1_nomenclature/static/src/js/barcode_parser.js#L91-L98
So, when we try to extract the lot name, the values will be:
- barcode: `10xyzAlt0293040`
- regex: `^(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})(?:(Alt029))?`

And here is the issue: `Alt029` will be caught by the second capturing
group of the regex (instead of the third one), so it will be considered
as part of the lot name, we still have an issue => considering the
`Alt`/`Control` keys and defining some values in `gs1_separator_fnc1`
are not enough, we need to parse twice:
- The first parsing is used to convert all occurrences of
`gs1_separator_fnc1` into the hex `\x1d`. Then, it is also used to
remove all useless `Alt`/`Control`/`Shift`.
- The second parsing is the already-existing one and this parser is
already able to catch all `\x1d` as group separators:
https://github.com/odoo/odoo/blob/1c0dec6d5813fa81a0fec8668ee13d8036cde5c5/addons/barcodes_gs1_nomenclature/static/src/js/barcode_parser.js#L90

For the mobile device, it means that the users will have to define a
special character that stands for GS (e.g., `#`), so we will retrieve it
in the input.

OPW-2930873

Master base property field 2022 std backup

PR #99146

Coremasterbase

This update appears to adjust how base property field backup handling works in Odoo. It likely improves reliability for internal data configuration, helping reduce the risk of issues when property-related settings are backed up or restored.

#property fields#backup#configuration

[IMP] account: UX improvements

PR #98323

Coremasteraccount

The accounting screens now avoid offering quick-create options where they are unnecessary or cannot be used. This reduces confusing choices for users and helps keep accounting configuration workflows clearer and more reliable.

Original PR description

Remove quick create from the places that is either not needed or not possible

Task #2850996
Related Enterprise PR: odoo/enterprise#30525

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#accounting#user experience#configuration

[IMP] account: UX improvements

PR #30525

Enterprisemasteraccount_accountantaccount_asset

Accounting screens now avoid offering quick-create options where they are unnecessary or cannot be used. This reduces confusion during reconciliation and asset account setup, helping users complete accounting workflows with fewer dead ends.

Original PR description

Remove quick create from the places that is either not needed or not possible
Task #2850996
Related Community PR odoo/odoo#98323

#accounting#user experience#data entry

Bug Fixes(4)

Resolved issues and error corrections

[FIX] rating: fix ratings according to company

PR #101410

CoremasterratingMedium

Customer rating reports now only show ratings that belong to the user's company. This prevents teams in multi-company setups from seeing ratings from other companies and keeps reporting aligned with each business entity.

Original PR description

Before this commit, in helpdesk > reporting > customer rating the ratings were visible to all companies even if they don't belong to that company

So in this commit, the ratings are visible to the respective company only

task-2995118

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

#customer ratings#multi-company

Other(75)

Miscellaneous changes

[FW][FIX] website_hr_recruitment: fix apply fields

PR #101808

Coremasterwebsite_hr_recruitment

Previously, it wasn't possible to add fields to the form using the web editor on the apply page. This commit also set the "job_details" field on the hr.job model as a translatable field. task-2990154 Forward-Port-Of: odoo/odoo#101156

Original PR description

Previously, it wasn't possible to add fields to the form using the web editor on the apply page.
This commit also set the "job_details" field on the hr.job model as a translatable field.

task-2990154

Forward-Port-Of: odoo/odoo#101156

[FW][FIX] [15.0] hr_expense: Fix compute amount

PR #101503

Adds columns in the list view for properties. Dynamically create 'fields' for list views that copy the characteristics of their 'properties' field. Allows for seamless display of property values in the list view. Note: These columns cannot be sorted (requires python ORM modifications) These columns cannot be edited (not easily achievable) task #2980121 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Let's say the company uses a GS1 nomenclature and a user scans such a barcode: `(01)11111111111113(10)xyz(30)40` It means a product: - that has the barcode value '11111111111113' - for the lot 'xyz' - with a quantity equal to 40 The GS1 nomenclature explains that a lot consists of a prefix `10` and of up to 20 alphanumeric characters. In the above example, we could believe that the lot is actually `xyz3040`. To prevent this kind of issue, the GS1 standards use a special character: the Group Separator (its hex value is `\x1d` and does not have any visual representation). So, when reading the barcode of the above value, the barcode reader will detect the GS between `z` and `3` (so we know that this is the end of the lot name). Because GS has no visual representation, the way the GS character is given by the scanner to the device depends on the scanner itself. For instance, some barcode readers try to encode GS thanks to its unicode input (as used on a Windows device): it enters Alt+0+2+9 (i.e., the unicode value of GS). This is an issue since we filter out all keydown events with the `Alt` key pressed. Also, our way to interpret the barcode value depends on the device: on a desktop device, we listen the events. As explained above, this could be an issue (for instance with Alt+029). On a mobile device, we let the barcode reader write in an hidden input and we then extract the written value. There is also an issue here: the GS is not present in the extracted string. For these reasons, some changes are need. The idea is to let the user lists the ways his barcode readers will encode the GS character (the scanners often give the possibility to set a value manually.). There is already a field for this: https://github.com/odoo/odoo/blob/320025ee630acadd4a5cbd32f425cddee4f81c1e/addons/barcodes_gs1_nomenclature/models/barcode_nomenclature.py#L18-L20 However, this is not correctly working. Suppose we now stop to filter out the `Alt` keys: in the above example, the scanned value becomes `011111111111111310xyzAlt0293040`(as you can see, there is an `Alt029` at the end of the lot). Suppose also that we defined `gs1_separator_fnc1` with `Alt029`. When parsing the barcode value, we have: https://github.com/odoo/odoo/blob/1c0dec6d5813fa81a0fec8668ee13d8036cde5c5/addons/barcodes_gs1_nomenclature/static/src/js/barcode_parser.js#L91-L98 So, when we try to extract the lot name, the values will be: - barcode: `10xyzAlt0293040` - regex: `^(10)([!\"%-/0-9:-?A-Z_a-z]{0,20})(?:(Alt029))?` And here is the issue: `Alt029` will be caught by the second capturing group of the regex (instead of the third one), so it will be considered as part of the lot name, we still have an issue => considering the `Alt`/`Control` keys and defining some values in `gs1_separator_fnc1` are not enough, we need to parse twice: - The first parsing is used to convert all occurrences of `gs1_separator_fnc1` into the hex `\x1d`. Then, it is also used to remove all useless `Alt`/`Control`/`Shift`. - The second parsing is the already-existing one and this parser is already able to catch all `\x1d` as group separators: https://github.com/odoo/odoo/blob/1c0dec6d5813fa81a0fec8668ee13d8036cde5c5/addons/barcodes_gs1_nomenclature/static/src/js/barcode_parser.js#L90 For the mobile device, it means that the users will have to define a special character that stands for GS (e.g., `#`), so we will retrieve it in the input. OPW-2930873

Remove quick create from the places that is either not needed or not possible Task #2850996 Related Enterprise PR: odoo/enterprise#30525 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Before this commit, in helpdesk > reporting > customer rating the ratings were visible to all companies even if they don't belong to that company So in this commit, the ratings are visible to the respective company only task-2995118 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

This commit fixes three issues regarding the top left search input of the Media Dialog. First, following this flow from the website builder: - Start the Media Dialog with no images, => A visual indication to guide you to use the search input is there - Type a search query in the top left search input, - Erase completely the search query, => The visual indication is not displayed again. When [1] reworked the Media Dialog with components, it wrongly defined the ImageSelector web_unsplash patch to load unsplash images: if there was no query string, the state.isFetchingUnsplash variable was set to true and never to false, therefore the component was acting as if there was still some fetching in progress. Secondly, pressing 'enter' when the input was focused would trigger a reload of the window. This was due to an obscure html spec described in [2]: "When there is only one single-line text input field in a form, the user agent should accept Enter in that field as a request to submit the form." When [3] reworked the design of the Media Dialog, it added a t-if on the second "url" input, making the form with a single input. This commit fixes this wrong behaviour by using div elements instead of forms. Lastly, [3] also removed the position-fixed on the loading images, which was preventing to modify the container height before resizing them. This led to visual glitches before seeing the resized images. This commit adds back this class to prevent that visual glitch. [1]: https://github.com/odoo/odoo/commit/31cc10b91dc7762e23b4bde9b945be0c4ce3fe3b [2]: https://www.w3.org/MarkUp/html-spec/html-spec_8.html#SEC8.2 [3]: https://github.com/odoo/odoo/commit/ff0b2d441252560a076a3609d81c369f0ce42d19 task-2687506 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101613

Setting the attributes `can_create` and `can_write` in views which are not editable is useless as you cannot edit the record in these views. This allow to gain some KB when serving the view to the web client, as well as making the view cleaner. e.g. the graph view in the CRM > My Pipeline menu Before: ```xml <graph string="Opportunities" sample="1"> <field name="stage_id" can_create="true" can_write="true"/> <field name="user_id" on_change="1" can_create="true" can_write="true"/> <field name="color" modifiers="{"invisible": true}"/> </graph> ``` After: ```xml <graph string="Opportunities" sample="1"> <field name="stage_id"/> <field name="user_id" on_change="1"/> <field name="color" modifiers="{"invisible": true}"/> </graph> ``` This revision takes the opportunity to port the `editable` concept from the server to the web client MockServer, in order to be able to test the removal of these attributes from the views in the QUnit tests. The `_editableNode` JS function added here is the translation of the existing `def _editable_node` method in `addons/base/models/ir_ui_view.py` https://github.com/odoo/odoo/blob/f5edde3624f4fe40f87cc7fed7dcfc4bbce1f19f/odoo/addons/base/models/ir_ui_view.py#L1282-L1301 Forward-Port-Of: odoo/odoo#101014

Reproduction: 1. Install eCommerce and accounting 2. Go to Accounting->Configuration->Taxes, add one sale tax 15%, and one 0%. Both taxes are included in the price. 3. Go to Configuration-> Fiscal Position, create a new one “test” which applies the tax mapping from 15% sale tax to the 0%. Check “Detect Automatically”, set country group as Europe 4. Go to Website->Orders->Customers, set the country of the portal user, Joel Willis, as Luxembourg. In Sales&Purchase->Fiscal Information set the fiscal position as “test” 5. Go to Website->Products->Product Variants, create a new one “test_tax_prod” with price 110, and sale tax 15%, can be sold, can be purchased and consumable. 6. Go to Website->Configuration->Attribute, create a new product attribute “test” with Display Type as Ratio, Variant Creation Mode as Never. Create a value “a” in its attribute values 7. Go to Website->Products->Products, find test_tax_prod, go to its variant tab, set attribute as “test” with value “a”, publish this product 8. Open an incognito tab, login as “portal” pwd: portal, search the product “test_tax_prod”, set the price list as “public price list”, the price is 95.65 on the page. Add it to the cart, the price is 110 Reason: When we update the order_line, we should update the price based on the fiscal position for the no_variant products too. However, based on the current workflow, the price is computed in method _website_product_id_change before an order line is created. Thus for no_variant products, the price is not updated. Fix: This issue is fixed in saas-15.3 by rewriting the workflow and calculating the price through an on_change function here: https://github.com/odoo/odoo/blob/saas-15.3/addons/sale/models/sale_order_line.py#L588-L605 In v13, we don’t have this on_change method to compute the new price, so a similar price update can be created in the cart update for website_sale. This fix solution was created here: ea25921 However, new price computation issues can happen when combining two pricelists, here: 8d6a2ca Thus the fix is eventually done in _website_product_id_change. Added a new parameter to force checking the orderlines based on the domain. The orderline is created but only can be searched based on the domain. This ensures the price is computed correctly for pricelists and for tax. opw-2856956 Fix by re-writing in saas-15.3: https://github.com/odoo/odoo/blob/saas-15.3/addons/sale/models/sale_order_line.py#L588-L605 First related fix: ea25921 Second fix to patch for the first fix: 8d6a2ca -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#101797 Forward-Port-Of: odoo/odoo#99647

`hr_timesheet`, and other timesheet related modules, overrides `_get_view` to change some timesheet time field label from "Hours" to "Days" according if the company uses hours as timesheet encoding UOM or days. Since odoo/odoo#99417, and the fact back-end views are cached, keys on which the model views depends on for the cache must be added through an override of the method `_get_view_cache_key`. Without this revision, if a database has one company using hours as timesheet encoding uom, and a second company using days as timesheet encoding uom, the label for one of the two company could be wrong according to which user/company accessed first the view, for which company the view has been put in the cache first. These overrides of `_get_view` should be replaced by another mechanism, for instance by a Javascript widget, as this mechanism doesn't really make sense when browsing multiple companies at a time (selecting multiple companies in the companies dropdown menu). When going from one record to another with the left/right arrows, the company can depend from one record to another, and therefore the label should change from one record to another according to its company, which is not the case with the current implementation. It could also be achieved by setting two different labels, with an invisible attrs based on a related field of company.timesheet_encode_uom_id. However, as we are close to release, and 16.0 is already frozen, no unstable changes should be done, hence I restore the behavior which was there before odoo/odoo#99417. Related to odoo/enterprise#31888 Forward-Port-Of: odoo/odoo#101356

[FIX] website: remove 'Odoo' prefix on the WebsitePreview document title Before this commit, the WebsitePreview document title was not completely replaced with the iframe's one: it was still prefixed by 'Odoo - ' by the title service. Now, the WebsitePreview, introduced in [1], is adapted to remove the 'zopenerp' part when replacing the title (and adding it again when unmounted). While doing this, the backend's favicon is also changed with the frontend's one, to be consistent with displaying the frontend document title only. This commit also adds an effect on the Optimize SEO dialog, so that the document title matches the user's input. [1]: https://github.com/odoo/odoo/commit/31cc10b91dc7762e23b4bde9b945be0c4ce3fe3b task-2687506 ----- [FIX] web_editor, website: fix website edition with rtl languages Before this commit, for the following flow: - Add arabic language (or any other rtl language), - On one of the websites, set it as the only website's language, - Reload and go to the client action, => The frontend is correctly displayed in rtl, - Click on edit, => The frontend, in the iframe, is reverted to ltr, The WysiwygAdapter, introduced in [1], was not passing the correct direction option to the OdooEditor, which would revert the editable to the default 'ltr' direction. [1]: https://github.com/odoo/odoo/commit/31cc10b91dc7762e23b4bde9b945be0c4ce3fe3b task-2687506 ----- [FIX] website: hide "Editor Menu" on translatable websites Before this commit, the Editor Menu was confusing when opened for a translatable website: it would list the menus in the user's language, not in the displayed website's language. First, this commit shows that menu only for websites in their default language, as the user should edit his website structure in the default language. Secondly, the 'get_tree' and 'save' requests on the website menus are done with the website's language, not the user's language. This commit also fixes a bug introduced with [1]: the website override of the start method of the SnippetsMenu was incorrectly done. In translate mode, it should not activate snippets on clicks, otherwise, the LinkPopover was instantiated when clicking on navbar menus, allowing to edit the menus from the translate mode, and breaking it. [1]: https://github.com/odoo/odoo/commit/df1869153a90898bad3e0b61e5fc43a9ed3d59c9 task-2687506 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#100039

During tests, when matching ir.mail_server has `smtp_encryption` set to `starttls`, connect() will crash with an AttributeError as follows: ```python 2022-09-22 07:04:27,882 20445 ERROR tests-150-starttls odoo.addons.base.tests.test_ir_mail_server: ERROR: TestIrMailServer.test_mail_server_send_email Traceback (most recent call last): File "/home/odoo/src/odoo/15.0/odoo/tools/misc.py", line 804, in deco return func(*args, **kwargs) File "/home/odoo/src/odoo/15.0/odoo/addons/base/tests/test_ir_mail_server.py", line 261, in test_mail_server_send_email IrMailServer.send_email(message, mail_server_id=self.server_domain.id) File "/home/odoo/src/odoo/15.0/odoo/addons/base/models/ir_mail_server.py", line 575, in send_email smtp = self.connect( File "/usr/lib/python3.8/unittest/mock.py", line 1081, in __call__ return self._mock_call(*args, **kwargs) File "/usr/lib/python3.8/unittest/mock.py", line 1085, in _mock_call return self._execute_mock_call(*args, **kwargs) File "/usr/lib/python3.8/unittest/mock.py", line 1146, in _execute_mock_call result = effect(*args, **kwargs) File "/home/odoo/src/odoo/15.0/odoo/addons/base/models/ir_mail_server.py", line 313, in connect connection.starttls(context=ssl_context) AttributeError: 'TestingSMTPSession' object has no attribute 'starttls' ``` This commit adds a dummy `starttls()` method to `TestingSMTPSession` to gracefully handle such case. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#100779

Steps to reproduce: - Select a company whose currency is USD. - Create an invoice in EUR. - Go to the "Journal Items" tab. The amounts in the "Debit" and "Credit" columns are correct, but the currency symbol is € (invoice currency) instead of $ (company currency). This should not happen since both of these fields have `currency_field='company_currency_id'` in their definition: https://github.com/odoo/odoo/blob/702adc878e897461c4c9976110cee84d397ff4af/addons/account/models/account_move_line.py#L90-L99 But since those fields fulfill the conditions in `canUseFormatter`: https://github.com/odoo/odoo/blob/702adc878e897461c4c9976110cee84d397ff4af/addons/web/static/src/views/list/list_renderer.xml#L228-L229 `currencyField` remains undifined in the `formatOptions` when going through `getFormattedValue`: https://github.com/odoo/odoo/blob/702adc878e897461c4c9976110cee84d397ff4af/addons/web/static/src/views/list/list_renderer.js#L722-L734 Which is why the current fix looks at `options.field.currency_field` before falling back to `currency_id` when setting `currencyField`. A test is also added to make sure the issue does not creep back in again. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#100836

Improvements(5)

[IMP] web: Add property list view

[IMP] barcodes{,_gs1_nomenclature}: interpret GS character

Master base property field 2022 std backup

[IMP] account: UX improvements

[IMP] account: UX improvements

Bug Fixes(4)

[FIX] rating: fix ratings according to company

Other(75)

[FW][FIX] website_hr_recruitment: fix apply fields

[FW][FIX] [15.0] hr_expense: Fix compute amount

Improvements(5)

[IMP] web: Add property list view

[IMP] barcodes{,_gs1_nomenclature}: interpret GS character

Master base property field 2022 std backup

[IMP] account: UX improvements

[IMP] account: UX improvements

Bug Fixes(4)

[FIX] rating: fix ratings according to company

Other(75)

[FW][FIX] website_hr_recruitment: fix apply fields

[FW][FIX] [15.0] hr_expense: Fix compute amount

[FIX] loyalty: amount conversion of rules without company

[IMP] hr: hide create_employee on create user form

[FIX] website_sale_renting: Rental online today is in the past

[FW][IMP] web: update owl from 2.0.0-beta-21 to 2.0.0-beta-22

[FW][IMP] mail: move code from component to models (CallParticipantVideoView)

[FW][FIX] web_editor: avoid vertical dropzones from taking too much space

[FW][FIX] hr_holidays: properly reset time off type

[FW][FIX] hr_holidays: fix leave stats widget

[FW][FIX] mail: move activity mark done inside popover and clean overflow

[FW][FIX] Stock: show stock_forecasted scrollbar

[FW][FIX] event_sale: add no event to the so template

[FW][FIX] web_editor, web_unsplash: fix media dialog search

[FW][FIX] stock: fix inventory report

[FW][FIX] web: tagline rendering box repport pdf vs preview

[FW][IMP] base, web, website, *: differentiate essential & optional cookies

[FW][IMP] web: cleanup notebook's styling in Form & Kanban examples

[FW][FIX] sale_project: Allow user to cancel SO linked to project

[FW] Fix bosnian configuration

[FW][IMP] base, web: set can_create/can_write only on editable nodes

[FW][FIX] pos_restaurant:save new split order on payment proceed

[FW] 16.0 mrp timer arm

[FW][IMP] payment: remove duplicate chatter message

[FW][FIX] payment_stripe: validation operations treated incorrectly

[FW][FIX] account: When filling gaps, create button has bad default journal

[FW][FIX] lunch: show translated description

[FW][FIX] website_sale: fix crash when using unsplash in extra images

[FW][FIX] web: inputs should be below labels in `xxs_form_view`

[FW][FIX] mail: reintroduce missing overflow on discuss sidebar

[FW][IMP] mail, *: refactor patch API to look like model definitions

[FW][FIX] web: kanban groups t-foreach key is always unique

[FW][FIX] mail: missing a space between two user avatars

[FW][FIX] website_sale: calculate the tax for no_variant product in cart

[FW][FIX] base: use higher res profile pictures

[FW][IMP] spreadsheet_dashboard: grid cursor

[FW][FIX] im_livechat: prevent crash with avatar of invalid operator

[FW][FIX] website: fix url picker editor dropdown

[FW][FIX] web_editor: remove old values in the color picker widget previews

[FW][FIX] web: reload correct record after print

[FW][FIX] project: filter stages based on the user_id

[FW][FIX] account: add latest running balance when grouping by statement

[FW][FIX] hr_timesheet: _get_view dependent on company.timesheet_encode_uom_id

[FW] Batch of website in backend fixes: website edition with rtl languages, Editor Menu hidden on translatable website, document title without 'Odoo -' prefix

[FW][FIX] web: list: do not always keep offset

[FW][FIX] point_of_sale: display bank statement lines

[FW][FIX] base: fix mock smtplib connection for server with 'starttls' encryption

[FW][IMP] mail: restore sign request activity

[FW][FIX] survey: fix sample surveys form view

[FW][FIX] website, *: fix website content list / kanban views

[FW][FIX] website: add the search params intro the editedObjectPath

[FW][FIX] web_unsplash: keep using the util method, not ICP get_param

[FW][IMP] web_unsplash: allow to configure app id in settings

[FW] Master accountpoc feedbacks wan

[FW][FIX] web: monetary formatter in readonly ignores currency_field in field definition

[FW][FIX] website_helpdesk_knowledge: delete helpdesk article

[FW][FIX] documents_{project,fsm}: fix automatic folder creation

[FW][IMP] (website_)knowledge: improve interface

[FW][FIX] sign: restore sign request activity

[FW][FIX] extract: fix various tax issues