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..."

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mlncn’s picture

FileSize
4.29 KB

(now actually attached)

mlncn’s picture

Status: Active » Needs review
tchurch’s picture

Assigned: Unassigned » tchurch

Thanks.
I will review and test.

tchurch’s picture

Status: Needs review » Needs work

OK. 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.

tchurch’s picture

Status: Needs work » Needs review
FileSize
670 bytes
4.86 KB

OK. 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.

maxilein’s picture

I 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.

tchurch’s picture

I 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?

maxilein’s picture

That would be just fine for me.

(In my humble opinion I would call the whole thing "Account Settings Extra Permission".)

BR, Max

tchurch’s picture

I'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.

tchurch’s picture

OK. 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.

drifter’s picture

Status: Needs review » Reviewed & tested by the community

Applied the patch and used it on my site, works great, thanks!

tchurch’s picture

Status: Reviewed & tested by the community » Fixed
tchurch’s picture

Status: Fixed » Closed (fixed)