-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[17.0][FIX] web_responsive: Fix blank screen on search (support menus w/o xmlid) #3105
[17.0][FIX] web_responsive: Fix blank screen on search (support menus w/o xmlid) #3105
Conversation
This might also affect the 18.0 version (#3037) |
Please rewrite the commit message (and the PR title) according guidelines: https://github.com/OCA/odoo-community.org/blob/master/website/Contribution/CONTRIBUTING.rst#commit-message |
b8105dc
to
18638cb
Compare
…mlid) If a menu item is created manually via the Odoo UI, then it (likely) won't have an xmlid. As a result, the `t-foreach` fails, resulting in the whole Odoo UI crashing (a blank white screen is shown). This code should use `id` as the `t-key` instead, as that is *always* available, even for menu items created manually.
18638cb
to
a1b29f3
Compare
@pedrobaeza Apologies, fixed now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ocabot merge patch
On my way to merge this fine PR! |
Congratulations, your PR was merged at 457b9ed. Thanks a lot for contributing to OCA. ❤️ |
If a menu item is created manually via the Odoo UI, then it (likely) won't have an xmlid. This code should use
id
as thet-key
instead, as that is always available.Fixes #3104
Explanation: With asset debugging enabled, we get an error
Error: Got duplicate key in t-foreach
, because multiple elements have a blank""
xmlid, and so we hit a key conflict.