I keep getting this message. I have a new "Admin users" role for creating authenticated users. It works fine and the new user becomes active but I keep getting this message as a warning! What am I missing or is this a bug?

Files: 
CommentFileSizeAuthor
#1 administerusersbyrole.module.patch992 bytessir_squall

Comments

StatusFileSize
new992 bytes

Hello,

I have found the solutions, I have created patch.

I'm getting this message too.

I'm finding that my privileged roles are able to unblock new registrations when I give permissions, but I'm seeing this error message. The above patch seems to change the logic. For me the logic seems to be working, just an erroneous error message.

We're also using Role delegation 7.x-1.1

My patch only add a test in addition to correct the error message, it does not change the logic.
I don't know why you have this.

Title:You do not have permission to unblock XXXXXYou do not have permission to unblock <username>

Patch seems to work (no more erroneous error messages), but I don't know if it's the right solution. The message is very confusing for users, so a commited fix would be great.

Status:Active» Fixed

The hook function where this error message was being generated has been removed from the module altogether (http://drupalcode.org/project/administerusersbyrole.git/commit/98413a8), so I'd say this is fixed.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Could a new release be made with this improvement?

Version:7.x-1.x-dev» 7.x-1.0-beta1

I have also this message:
You do not have permission to unblock <username>
How can i fix it? Can i use the patch in #1 ? Or should i use the dev version?

PS: When can we expect a rollout 7.x-1.0-beta2 release of Administer Users by Role?

You should use the dev version.

I don't believe that "use the dev version" is an acceptable solution for a live website. It's fine for development. I would very much like to see this fix rolled into the recommended release of the module. Thank you.

Can I second aaronpinero's message. Please can this patch be rolled out to the recommended release.

We use aegir and have a number of sites that get this message.