Thank you, Tim, for a great useful module!
I'm hoping you can roll an official Drupal 7 release.
I've included a code refresh of the Drupal 7 version.
The most major change i made was to use hook_menu_alter() rather than re-defining the entire 'admin/config/people/accounts' item in hook_menu().
Other than that the attached patch:
* uses lower-case permission names (and sentence-case titles) as is core's convention
* avoids passing a variable into the t() function (which would make it harder for translaters to find the right text)
* clarifies that help text a little
* uses the D7 standard "Implements hook..." consistently rather than the D6 "Implementation of..."
Comment | File | Size | Author |
---|---|---|---|
#10 | 1907424.patch | 4.86 KB | tchurch |
#10 | user_settings_access.install.txt | 825 bytes | tchurch |
#5 | 1907424.patch | 4.86 KB | tchurch |
#5 | user_settings_access.install.txt | 670 bytes | tchurch |
#1 | usa-drupal-7-refresh.patch | 4.29 KB | mlncn |
Comments
Comment #1
mlncn CreditAttribution: mlncn commented(now actually attached)
Comment #2
mlncn CreditAttribution: mlncn commentedComment #3
tchurch CreditAttribution: tchurch commentedThanks.
I will review and test.
Comment #4
tchurch CreditAttribution: tchurch commentedOK. First look. It doesn't work.
Because of the change in the permission names, an update is needed to the database for roles who already have the permission.
I also want to look at the uninstall too (to remove all permissions from roles).
I will look further at it.
Comment #5
tchurch CreditAttribution: tchurch commentedOK. I've uploaded a patch (I think it might be the same as the previous one) but also an install file with an update for the permissions.
Can someone confirm it's OK.
Comment #6
maxilein CreditAttribution: maxilein commentedI haven't tested your recent patch.
I would just like to mention that I think it is good practice to show the module name in the modules listing.
The module is named "Control Access to User Settings" while in the listing it shows "User Settings Access".
With all the many modules around ...
Thanks + BR.
Adding: I completely misunderstood the meaning of "user settings":
This module separates management of general account settings (/admin/config/people/accounts) from user management.
It would be great if there was a permission to manage user profile data only.
Comment #7
tchurch CreditAttribution: tchurch commentedI could change the module name or the project name in Drupal.
It might be better to change the project name to "User Settings Access" so it matches the names of the files too.
What do you think?
Comment #8
maxilein CreditAttribution: maxilein commentedThat would be just fine for me.
(In my humble opinion I would call the whole thing "Account Settings Extra Permission".)
BR, Max
Comment #9
tchurch CreditAttribution: tchurch commentedI've changed the name of the project to "User Settings Access".
Regarding managing user profile data, maybe the module userprotect (http://drupal.org/project/userprotect) would help.
Comment #10
tchurch CreditAttribution: tchurch commentedOK. Attached is the final patch that I plan to make to this version to make an official release.
I've tested it on my local system but I'd like someone else to confirm it's OK.
Comment #11
drifter CreditAttribution: drifter commentedApplied the patch and used it on my site, works great, thanks!
Comment #12
tchurch CreditAttribution: tchurch commentedComment #13
tchurch CreditAttribution: tchurch commented