From 55bdf0e8ffaa068734d5a0b9dcec0a3ce9f8aebf Mon Sep 17 00:00:00 2001 From: Goffin Simon Date: Wed, 22 Jun 2016 14:27:36 +0200 Subject: [PATCH] [FIX] website_project_issue: Only portal issues must be visible When going to routes ['/my', '/my/home'], only the project issues in portal privacy visibility must be displayed. Inpired from 56c5d0a The field privacy_visibility is not accessible in portal due to access rights. opw:676447 --- addons/website_project_issue/controllers/main.py | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/addons/website_project_issue/controllers/main.py b/addons/website_project_issue/controllers/main.py index 98f06c0c281..4c15b60761b 100644 --- a/addons/website_project_issue/controllers/main.py +++ b/addons/website_project_issue/controllers/main.py @@ -10,7 +10,15 @@ class WebsiteAccount(website_account): def account(self): response = super(WebsiteAccount, self).account() user = request.env.user - project_issues = request.env['project.issue'].search([]) + # 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'].sudo().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]) + ]) response.qcontext.update({'issues': project_issues}) return response