SplatDev.Umbraco.Plugins.MemberGroups 2.3.1

UmbracoCms.Plugins.MemberGroups

Member group management plugin for Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

Upgraded from Umbraco 8 (net472) to modern SDK-style multi-targeting.

Upgrade Summary (Umbraco 8 → 13/17)

Features

• Assign/remove members from groups
• Create and edit user groups
• Enable/disable Umbraco users
• Look up members by email
• List member groups and member types
• Bulk operations via API

API Endpoints

Note on Password Management

In Umbraco 13+, direct password hash assignment (RawPasswordValue) is not available. Password operations must use the Umbraco Users API or IMemberService.SavePassword(). The ChangeUserPassword and ResetUserPassword methods log a warning and return guidance.

Changelog

2.3.1 — 2026-08-24

Package metadata only: the listing now carries an icon and search tags, and the project and repository links point at the organisation that actually hosts this code. No code changes.

2.3.0 — 2026-08-23

The Razor view behind @await Component.InvokeAsync(...) is now compiled into the package. It was previously carried as a loose file that nothing packed, so the component threw "view not found" on every install and the front-end usage shown in this README could not have worked.

2.2.4 — 2026-08-22

• You can create a member group from the dashboard, and add a member to one by email. The dashboard shipped a helper for calling these endpoints that nothing ever called, so six of the nine operations the API exposes had no way in — the three tabs were read-only lists and a lookup box.
• Looking a member up now leads somewhere: the result carries a group picker and an Add to group button, rather than ending at a card of facts.
• Creating a backoffice user group no longer reports success when it failed. On Umbraco 17 the call was passing an empty user key, which the API rejects; the failure was logged as a warning and the caller was told the group had been created, with an id of 0.
• The Member Types tab now says where member types are actually edited instead of presenting a list with no way to act on it.

2.2.3 — 2026-08-21

• A failed request now says so in the dashboard. Previously the dashboard kept its previous (usually empty) state, so a refused or failed call looked identical to having no data.

2.2.2 — 2026-08-21

• Dashboard now sends the backoffice token with its API calls. On Umbraco 17 those calls were arriving unauthenticated and coming back 401, which the dashboard rendered as an empty state rather than an error.
• A failed request now raises a notification instead of leaving the dashboard looking like there is simply no data.