SplatDev.Umbraco.Plugins.Restricted 2.5.4

Restricted

Content restriction plugin for Umbraco — member-only content gates using Umbraco's built-in IPublicAccessService with role-based access and a backoffice dashboard.

Compatibility

Installation

dotnet add package SplatDev.Umbraco.Plugins.Restricted

Quick Start

The plugin auto-registers via Umbraco's composition system. No explicit Program.cs registration required.

Features

• Member-only content gates using Umbraco's built-in IPublicAccessService
• Role-based access: restrict nodes to specific member groups
• Paywall support: redirect unauthorized visitors to a login or error page
• Backoffice dashboard to manage restricted nodes
• View component for rendering access status in Razor views

API Endpoints

Usage in Razor

@await Component.InvokeAsync("Restricted", new { nodeId = Model.Id })

No EF Core Required

This plugin uses Umbraco's own public access infrastructure — no additional database tables needed.

Known Limitations

• Relies entirely on Umbraco's IPublicAccessService; cannot enforce restrictions outside of Umbraco's content delivery pipeline
• Role-based access is limited to Umbraco member groups — no support for external identity providers
• Redirect behavior (login vs error page) must be configured per-node

Changelog

2.5.4 — 2026-08-26

Fixes a duplicate registration on sites that still have a physical App_Plugins folder for this plugin, left behind by an older release that copied content into the site. Umbraco registered those extensions twice - once from its own scan of the folder, once from this package's embedded manifest - and logged "Extension with alias ... is already registered". The embedded manifest now yields to the physical copy.

2.5.3 — 2026-08-24

Restores the Common group and the Brazilian Portuguese translation that shipped with the Umbraco 8 package.

2.5.2 — 2026-08-24

Removes a dashboard screenshot that showed an error toast. It was captured against a site where this plugin's API was unreachable, so it advertised a broken dashboard. No screenshot is better than a misleading one; a replacement will be taken against a working install.

2.5.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.5.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.4.0 — 2026-08-23

• You can restrict or unrestrict a page from the page itself. The plugin shipped a dashboard listing restricted nodes and nothing on the node, so protecting a page meant leaving it, finding it in a list somewhere else, and coming back.
• The button writes Umbraco's own public access — the same entries the dashboard creates — so the page is protected everywhere, not only where this plugin renders. Choose the member group on the page, or set defaults on the data type.
• Unrestricting asks first, since that is the direction that exposes something.

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

License

MIT © SplatDev