There are conflicts on administerusersbyrole and me aliases modules. Me aliases module replace user uid by a "token" (by default, "me") in paths. Replaced user account edit path (e.g., user/me/edit), when processed by administerusersbyrole, results in a "You do not have permission to edit" message.

A patch is attached, but it might be reviewed.

me_aliases_compatibility.patch732 bytesarcovia


rafinskipg’s picture

Thanks for the patch, adan.

Now mine it's working.


Pinolo’s picture

Status:Active» Reviewed & tested by the community

Patch works for me with latest module's release

jarodms’s picture

works for me with latest versions: Me 6.x-2.9 and administerusersbyrole 1.4.
Thanks for the patch!

jason.fisher’s picture

Patch also successful here.

smokris’s picture

Assigned:Unassigned» smokris
Status:Reviewed & tested by the community» Fixed

@adan, your patch completely disables the edit restrictions introduced by this module — a serious security problem.

But it does seem pretty straightforward to ask me.module to translate its alias into a UID for us, so I modified Administer Users by Role to do that.

Committed to 6.x-1.x-dev as

Status:Fixed» Closed (fixed)
Issue tags:-compatibility issues, -me aliases

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