SplatDev.Umbraco.Plugins.CacheManager 2.1.8

CacheManager

Umbraco cache management and warming plugin — multi-layer caching with EF Core second-level cache, response caching, static file compression, and automated cache warming via background service. Consumes the SplatDev.Cache abstraction for ICacheService/ICacheProvider. Supports Umbraco 13 (net8.0) and Umbraco 17 (net10.0).

Compatibility

Installation

dotnet add package SplatDev.Umbraco.Plugins.CacheManager

Quick Start

Register in Program.cs:

builder.CreateUmbracoBuilder()
    .AddBackOffice()
    .AddWebsite()
    .AddCacheManager()   // <-- add this
    .Build();

Architecture — Cache Layers

The plugin wires multiple cache layers via CacheManagerComposer:

Configuration

// appsettings.json
{
  "ConnectionStrings": {
    "umbracoDbDSN": "Server=.;Database=Umbraco;..."
  },
  "CacheManager": {
    "EFCacheMinutes": 30,
    "StaticFileMaxAgeDays": 30,
    "ResponseCacheMinutes": 5
  }
}

Backoffice Dashboard

The plugin adds a Cache Manager dashboard under the Settings section:

Cache Warming

CacheWarmerBackgroundService runs as a hosted service:

1. Scrapes published content URLs from CacheWarmerEntry table
2. Issues HTTP GET requests to warm the response cache
3. Logs results to CacheWarmerEntryRepository
4. Tracks "not found" URLs in UrlNotFoundRepository

Trigger manually from the backoffice dashboard or let the background service run on schedule.

Dependencies

• SplatDev.Cache — cache abstraction layer (ICacheService, ICacheProvider)
• EFCoreSecondLevelCacheInterceptor — EF query result caching
• Microsoft.EntityFrameworkCore — DB context for cache tracking tables

Changelog

2.1.8 — 2026-08-22

• The dashboard can reach its API on Umbraco 17. Umbraco 13 routed the controller by convention at /umbraco/backoffice/api/CacheWarmer/…; Umbraco 17 does not route its management controllers that way, so nothing was mapped and every call 404'd. The controller now declares an explicit route on the Umbraco 17 target, and the dashboard calls it. Umbraco 13 keeps the URL its AngularJS bundle already uses.

2.1.7 — 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.1.6 — 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.
• 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.
• Internal extension namespace corrected — it was left over from another plugin.

License

MIT © SplatDev

Feedback