odoo/odoo#201199
Created by fw-bot
Merged
at e7d25ad3370e339e9c4a0ceb7137ddebe6a41a9f
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:master-saas-18.1-channel-invite-livechat-duplicate-key-aku-421905-fw
- head
- 2e917329412949a210011f68125f920de6de609d
- merged
- 7 months ago by Discuss, Alexandre Kühn (aku)
odoo/odoo | |
---|---|
saas-18.1 | #201017 |
saas-18.2 | #201167 |
saas-18.3 | |
saas-18.4 | |
19.0 | |
master | #201199 |
[FW][FIX] im_livechat: no duplicate t-key in channel invite
Follow-up of #198093
PR above improved channel invitation UI to show livechat operator languages and expertise, whereas it was only showing the main language.
This PR introduced the following crash by mistake:
OwlError: Got duplicate key in t-foreach: undefined
This happens because the keys were defined as index
, which is undefined
thus an operator with at least 3 languages or 2 expertise items made it crash.
The intend of t-key
was to use the index of item in the respective list, so the t-value
variable with _index
, e.g. language_index
, which this commit fixes.
Forward-Port-Of: #201017