From 86ae7b1e1a2b4e34ed1c8c98055fdabb574e53ff Mon Sep 17 00:00:00 2001 From: Goffin Simon Date: Tue, 3 May 2016 16:37:11 +0200 Subject: [PATCH] [FIX] website_project_issue: Issues visibility in frontend for portal users The domain used to search the project issues in the website_project_issue controller(['/my', '/my/home']) was useless thanks to the ir.rule portal_issue_rule opw:676447 --- addons/website_project_issue/controllers/main.py | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/addons/website_project_issue/controllers/main.py b/addons/website_project_issue/controllers/main.py index 942fec9da53..98f06c0c281 100644 --- a/addons/website_project_issue/controllers/main.py +++ b/addons/website_project_issue/controllers/main.py @@ -10,15 +10,7 @@ class WebsiteAccount(website_account): def account(self): response = super(WebsiteAccount, self).account() user = request.env.user - # TDE FIXME: shouldn't that be mnaged by the access rule itself ? - # portal projects where you or someone from your company are a follower - project_issues = request.env['project.issue'].search([ - '&', - ('project_id.privacy_visibility', '=', 'portal'), - '|', - ('message_partner_ids', 'child_of', [user.partner_id.commercial_partner_id.id]), - ('message_partner_ids', 'child_of', [user.partner_id.id]) - ]) + project_issues = request.env['project.issue'].search([]) response.qcontext.update({'issues': project_issues}) return response