summaryrefslogtreecommitdiff
path: root/addons/web/static/src/js/views/basic
diff options
context:
space:
mode:
authorRomain Derie <rde@odoo.com>2018-05-08 17:50:52 +0200
committerRomain Derie <rde@odoo.com>2018-05-09 11:02:16 +0200
commit665fcb62cfc0231125fc5d0815668b945e2a8d0d (patch)
tree7485f71346f7f9f0c797334d3047cc1c5303a68a /addons/web/static/src/js/views/basic
parent020906659e55bd41a07ab0e4e79da903af7b50c1 (diff)
[FIX] website: always show menu if its a container with visible menus
Before this commit: 1. If a menu was used as a container (dropdown) and had an unpublished page_id (website.page), we would never show that menu (and so its submenus) even if it has visible submenu. Some users are stuck with this since they: a) create a new page 'A' (unpublished by default) included in menu. b) create a new page 'B' (unpublished by default) included in menu. c) set 'B' as a submenu of 'A' in the menu manager d) decide to publish the website.page linked to menu 'B' Then, since menu 'A' is linked to an unpublished page, the menu 'A' and 'B' are never visible. 2. If a menu is being created with an URL that match a website.page URL, the m2o relation will automatically be set (website.menu.page_id). Still, if the user type the URL without the leading slash, the m2o won't be set. This could be misleading since on the page property in the page manager the URL is being shown without the leading slash even if it is stored in DB. Now: 1. We always show menu container if they contains visible submenu, even if the container menu is linked to an unpublished page 2. The page URL search is more clever and will match URL even if the only difference is the leading slash. This closes #24635
Diffstat (limited to 'addons/web/static/src/js/views/basic')
0 files changed, 0 insertions, 0 deletions