Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.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 |
|---|---|---|---|
| #2 | tac_lite_config_path_2.patch | 1.78 KB | alduya |
| #1 | tac_lite_config_path-1200550.patch | 1.69 KB | xjm |
Comments
Comment #1
xjmPatch implementing this menu change attached.
Comment #2
alduya CreditAttribution: alduya commentedI agree with the change of configuration paths.
I altered the patch so that the 'Access by Taxonomy' link is shown in the configuration screen.
Comment #3
Dave Cohen CreditAttribution: Dave Cohen commentedAlthough personally I believe access control settings belong next to user permissions, I do see the drupal.org doc sites access control modules as an example for what belongs under admin/config/people.
Thanks for the patches, sorry for the delay.