Closed CRogos closed 2 weeks ago
Are you sure the problem is with this module? I've installed it with hr
locally and haven't had any issue (all without including your changes).
Do you have any extra module installed on your instance?
I could reproduced the issue in runbot, by installing the hr module.
But I just realized this issue only occurs in the development mode! (?debug=1)
It seems that we will have the same problem with any other custom m2o widget, isn't it? Can't we do anything that don't force to declare that extra options on each widget?
I think it's not possible to make it more abstract... I have tried different options to avoid that extensions but nothing works... @chienandalu do you have any ideas to avoid them?
Yes, I tried changing the order of asset loading, but I wasn't able to make the error go away.
Ups :sweat_smile:
I will try it, I have tried with patch but patching the props directly
Any idea why this only occur in developer mode?
Any idea why this only occur in developer
Sometimes non-blocking errors are hidden to users, so they are only visible to developers. However, this doesn't mean they shouldn't be fixed.
What about using
patch()
: https://github.com/odoo/documentation/blob/17.0/content/developer/reference/frontend/javascript_reference.rst?plain=1#L168-L169
It does not work either
@CarlosRoca13 @chienandalu can we go with this solution as long we do not have any better way?
What do you think @chienandalu?
@CarlosRoca13 shall we continue without @chienandalu ? Maybe this solution is not the best, but it fixes the js error in developer mode.
/ocabot merge patch
On my way to merge this fine PR! Prepared branch 17.0-ocabot-merge-pr-2921-by-pedrobaeza-bump-patch, awaiting test results.
Congratulations, your PR was merged at f28a0d1b26f93e8699f350ca5e1b5b35e2236d53. Thanks a lot for contributing to OCA. ❤️
When web_m2x_options is installed, and you install the employee module, you cannot open the employee app and get this error message (development mode needs to be active):
The components Many2OneAvatarUserField and KanbanMany2OneAvatarUserField causing this error.
I am not sure if this is the best solution, because it also changes the dependency from "web" to "mail".Review feedback highly welcome.