Reference: Drupal 7 Information Architecture handbook page.
According to this document:
People
Drupal path:
admin/peopleThe People section should only be used for the listing of users. Modules may expose other data here. For example, a module might list events related to each user.
However, no module should add its configuration here. Instead, use the People category under the Configuration section (below).
Examples: Lists of events related to users
Based on this recommendation, it would be better to add the module's configuration under admin/config/people instead. Per the handbook page:
People
Drupal path:
admin/config/peopleThe People category should hold all modules that would fit under the old "User Management" category in Drupal 6. (Note: Do not confuse this category with the People section above.)
Examples: Access control modules
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 1200548-path_access-config-path.patch | 6.61 KB | mrfelton |
| #2 | 1200548-path_access-config-path.patch | 3.46 KB | mrfelton |
| #1 | path_access_config_path-1200548.patch | 3.13 KB | xjm |
Comments
Comment #1
xjmPatch implementing this menu change attached.
Comment #2
mrfelton commentedAgree, slight problem with the patch though. Revised version sets the menu item type to a normal menu item rather than a callback, ensuring that a visible menu item is created in the admin menu.
Comment #3
mrfelton commentedFollow up patch fixes a bug in the way that the role id is passed to the configure form, as well as refactord the form to follow drupal standards a little better. Sorry for slipping slightly more into this patch than was originally intended, but it's kinda related.
Comment #4
mrfelton commentedFixed in git:
http://drupalcode.org/project/path_access.git/commitdiff/56ecda0?hp=2287...