That error message shows up if the user configured at admin/config/project/project-issue-settings doesn't have the permission "access project issues"
But the permission "access project issues" is not defined anywhere in project_issue nor project.module.
My sense is that the permission should be changed to one related to editing a project issue like "user_access('edit any project_issue content', $account)" but I'm not sure. Happy to role a patch if that suggestion is accepted.
My workaround was to make uid 1 the followup user.
Comments
Comment #1
gregglesOh, and this message should really say what permission is necessary and link to admin/people/permissions so that the admin can easily fix it.
Comment #2
dwwAhh, good catch. We probably would have found it if either of these two issues were completed:
#1571400: Port auto-closing functionality to D7
#234463: Remove 'access * project *' permissions
I guess we can leave this issue open until one of those two fixes it. ;) For now, tagging as part of the d.o D7 upgrade (non-major), since this does affect d.o.
Comment #3
drummThis should loop through
project_issue_issue_node_types()and check for access to every node type. And yes, it should check for edit access.Comment #4
drummComment #5
drummDone
Comment #6
dwwCool, thanks. However, you introduced a bug here, since the call to
user_access()was no longer passing$account. Pushed a fix:http://drupalcode.org/project/project_issue.git/commit/46b13d9
Cheers,
-Derek