summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic/basic_controller.js
diff options
context:
space:
mode:
authorRomain Derie <rde@odoo.com>2018-11-26 13:21:29 +0000
committerRomain Derie <rde@odoo.com>2018-11-26 15:04:57 +0000
commita67553c9d2a7a5fcb28e44a5fbd5c245d851b91d (patch)
tree987307b97a06c14090ea4ceefe71579902802f1a /addons/web/static/src/js/views/basic/basic_controller.js
parent6f37e2cc5d8aa8b0723610216c29772cb832b03e (diff)
[FIX] website_event: website menu on event not working
Commit 7077f18e3 tried to fix the website event menu issue. But the fix was wrong and fixed only the event having a website_id set. After the 7077f18e3 fix, event with a website_id set are working as expected but the ones without a website_id are not working. Indeed, it will create a website.menu without a website_id which will result in the menu being duplicated for each website (multi-website rule). The required on website_id when activating website menu on event was trying to hide that new issue but it was problematic since: 1. We were removing a feature for no reason as it would not be possible anymore to create a generic event (no website) with website menu activated. 2. The required would only work in form view, demo data or custo data loaded through xml without a website_id but having website menu activated would still bug and would not have a menu. Worst, the menu would be duplicated for every website and added to the website navbar. Now, regardless of the event having a website_id set or not, activating or deactivating event menu will work. closes odoo/odoo#29036
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions