Added {exp:member:role_groups} template tag

[swierczek]

Add {exp:member:role_groups} template tag to get info about which Role Groups a member is assigned to.

Documentation will still be needed if this is accepted, which I am happy to update too. I didn't want to do all of the work if this will be declined by the mods though.

Demo template:

{!-- existing functionality --}
<h1>Roles</h1>
{exp:member:roles}
	<p>role ID: {role_id}</p>
	<p>role name: {name}</p>
{/exp:member:roles}

{!-- new functionality --}
<h1>Role Groups</h1>
{exp:member:role_groups}
	<p>role group id: {role_group_id}</p>
	<p>role group name: {role_group_name}</p>
{/exp:member:role_groups}

Output for member not assigned to any Role Groups:

Output for member in a Role Group:

[intoeetive]

@swierczek I think it's good addition! We're planning to roll out some Member functionality updates in 7.4, so it might go there as well.

I added a couple of comments, and also the code needs to be made PSR-12 compatible (e.g. a space is needed after foreach)

[intoeetive]

Is there a specific reason to call asArray here? RoleGroups is already iterable

[swierczek]

Nope, I didn't realize it was iterable 👍

[intoeetive]

Casting array to boolean is not PHP-version-proof. It should be better to use empty() check instead

[matthewjohns0n]

This tag isnt working for me - I'm testing with a super admin account and have one role group called "all" which contains all roles.

This is the output of the example template tag:

When I dig into the code, I'm seeing that during the loop, $roleGroup->group_id is 0 and it hits the continue. I'm not sure why I'm not getting the correct role groups here.

[matthewjohns0n]

This should be inverted - fixed here: f8bf5ac

[matthewjohns0n]

After the above fix, it is parsing it as if there is no member role group. This is still incorrect because I should have one member role group.

Current output:

[intoeetive]

It appears that besides member roles assigned to groups, role groups can be assigned directly to members (don't ask me why! :) - although you can't assign those directly to superadmins.

The template code was only respecting the second, and not the first - so I added that.

@matthewjohns0n please re-test