Active
Project:
Comment Notify
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Dec 2009 at 06:15 UTC
Updated:
29 Dec 2009 at 21:48 UTC
Took me a few minutes to realize that even if admin/settings/comment_notify looks right, I still have to manage permissions at admin/user/permissions.
Could these permissions also be displayed at admin/settings/comment_notify? That would help immediate comprehension of the product and show all relevant settings in one place.
I am OK if this needs to be applied to 7.x first.
Comments
Comment #1
gregglesCan you think of any other modules which do this? The installation instructions that come with the module do include this instruction, so I'm hesitant to add it elsewhere unless that other place is a standard place to add it.
Comment #2
dave reidSetting up permissions for a module is standard procedure. You have to do the same thing for all core modules. Why should we make contrib modules do anything different? Also see http://drupal.org/getting-started/install-contrib/modules
Comment #3
aren cambre commentedHmmm, maybe then it's a wider issue. I just feel it's unintuitive for the module admin page not to tell me there's additional setup somewhere else. I wonder--is the permissions system flexible enough that the module's current permissions could be displayed on the module admin page?
Comment #4
gregglesThe module admin page does tell you about settings on nodes if you haven't set those up properly, so I'm fine with making some messages here.
Maybe if none of the roles have the right permission we would set a message that says "You probably want some of your users to be able to use this dang thing! [link to permissions page]"
Comment #5
dave reidIf anything I'd recommend a hook_requirements check. In D7 we have links to the permissions for the module on the admin/config/modules page to let you know which modules have permissions to assign.
Comment #6
greggleshook_requirements is out of the context of the module, though. People go to admin/settings/comment_notify - we should give them all the information they need right there to configure it and do so in a way that once it's done they are no longer bothered by it (i.e. the green line in the report of hook_requirements "you configured permissions for module X" would get extreme really quickly).
Comment #7
dave reidI'm thinking more like how update.module does it and how I've implemented this in gravatar.module:
Comment #8
gregglesAha - ok. That makes a lot of sense. This makes more sense to put these kinds of things in a hook_help.