summaryrefslogtreecommitdiff
path: root/addons/web/static/src
diff options
context:
space:
mode:
authorDenis Ledoux <dle@odoo.com>2018-06-04 15:47:01 +0200
committerDenis Ledoux <dle@odoo.com>2018-06-04 15:57:56 +0200
commit579f67166a25bd3b072edf92c24df99b3568eaf7 (patch)
tree37eaaa9ebdb5e547409bcf62a443836b307e3e7b /addons/web/static/src
parent6b0c7a33d6b749d79232082fb5716e6cf36a9967 (diff)
[FIX] websiste: determinist homepage for portal users
In the portal module, the `index` method from the `web` module controllers is overriden to redirect `/` to the portal `/my` for the portal users, instead of the regular backend `/web`. However, when `website` is installed, this behavior should not happen, as you would like the signed in portal users to be able to see the website homepage, and not to be redirected to `my` when they try to access `/` root path of the website. Because the override in the website module was done on the `index` method coming from the `web` module instead of the `portal`, according in which way the Python module were loaded, it sometimes redirected to `/my`, sometimes it correctly displayed the homepage. This is because the modules are not loaded in a determinist order. To summarize, on runbot, if you logged as portal/portal, one time on two you were redirected to `/my`, and the other time you saw the homepage correctly. As `website` depends on `portal`, we have the possibility to override the `index` method of `portal` instead of the one of `web`, to force the determinist order, and therefore the determinist behavior of the homepage for portal users.
Diffstat (limited to 'addons/web/static/src')
0 files changed, 0 insertions, 0 deletions