SplatDev.Umbraco.Plugins.Blog 2.3.1

SplatDev.Umbraco.Plugins.Blog

Blog engine plugin for Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

Compatibility

Installation

dotnet add package SplatDev.Umbraco.Plugins.Blog

Features

• Blog posts with title, slug, content, excerpt, author, category, tags and view counter
• Categories and tags with slug-based routing
• Archive browsing by year/month
• Comment system with moderation (approve/delete)
• RSS feed at /umbraco/api/blog/rss
• Backoffice dashboard (Umbraco 17: Lit 3 element; Umbraco 13: AngularJS)
• ASP.NET Core View Component for front-end rendering

REST API

Database

Uses EF Core against Umbraco’s own database. Schema: blog. Run migrations to create tables:

The tables are created for you the first time the site starts: the plugin runs its own Umbraco migration against the database Umbraco is already using, on whichever provider it is configured with — SQL Server or SQLite. There is nothing to scaffold and nothing to run by hand.

Front-end View Component

@await Component.InvokeAsync("Blog", new { page = 1, pageSize = 5 })

Building the client

cd client
npm install
npm run build

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.

The view also still referenced the package's pre-rename namespace, so it would not have compiled even had it shipped. That is fixed, and the view is now built with the project — a broken view fails the build instead of failing a visitor's request.

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.
• README no longer tells you to scaffold EF Core migrations by hand — the plugin creates its own tables on first start, on SQL Server or SQLite.

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.
• The plugin's tables are created on startup. They were never created before, so anything touching them failed on a fresh install.
• Runs on SQLite as well as SQL Server. It previously assumed SQL Server and failed with "Keyword not supported: 'cache'" on the database Umbraco's installer offers by default.

License

MIT © SplatDev