Community Blogs

A weekend without internet access

Two Umbraco Cloud CLI spinoffs: fetch DB and media into your local dev

Two wizard CLIs that pull a fresh database and media folder from Umbraco Cloud straight into your local dev project - spinoffs from the archiver, useful on their own.

Umbraco Member thrown out after changing password

I'm working with a migration of the website for my Umbraco-package Newsletter Studio, from Umbraco 8 to Umbraco 17. I use Umbraco Members to allow customers to login and manage their licenses, update information and download receipts. New password = Member logged out When I was working on a feature to allow customers to change password, I noticed that I kept getting thrown out from the logged in area of the website after changing the password. The Member was throw out both: When they change password them selfs When the password was changed in from the backoffice I searched around for this, and it turns out that this is security feature. Umbraco has introduce settings around concurrent logins both for Users and Members, in appsettings.json one can configure these "Umbraco": { "CMS": { "Security": { "AllowConcurrentLogins": false "MemberAllowConcurrentLogins": false } } } According to the documentation, MemberAllowConcurrentLogins will fallback to the value of AllowConcurrentLogins, which is set to false by default. What happened? When the user changed the password, it looked like a new login, since this was not allowed the user was thrown out. There is two ways around this, one could refresh the users login cookie by calling _memberSignInManager.SignInAsync() after the password change. var currentMember = await _memberManager.GetCurrentMemberAsync(); var currentPasswordIsValid = await _memberManager.ValidateCredentialsAsync(currentMember.UserName!, model.CurrentPassword!); if (!currentPasswordIsValid) { return Error(); } var changePasswordResult = await _memberManager.ChangePasswordAsync( currentMember, model.CurrentPassword!, model.NewPassword!); if (!changePasswordResult.Succeeded) { return Error(); } // Refresh member authentication cookie await _memberSignInManager.SignInAsync(currentMember, true, "");  Or, one could set AllowConcurrentLogins to true.

The Silent Developer

I built a CLI to archive Umbraco Cloud projects

When a client upgrade meant retiring an old Umbraco Cloud project, I wanted a complete local archive before pulling the plug. So I built a wizard CLI to do it.

Fixing the "maxViewItems" Limit in Umbraco Cloud Kudu

Hitting the "maxViewItems is set to 299" message in Umbraco Cloud's Kudu console? Here's the one-line fix in DevTools which I always forget!

Giving Umbraco 17 A Bigger Clock: Raising The SQL Command Timeout With A Composer

Sometimes you need to override the Command Timeout in code... Here's how I did it in Umbraco 17 with a tiny composer. Continue reading

Complete Guide: Umbraco Sequence Upgrade from Version 13 to 17

OC.PowerSort 1.2.0

Auto-Register Block Previews in Umbraco

Skip manual registration and let your project automatically discover which blocks should have preview enabled based on existing views.

From Zero to Production: A no-nonsense Umbraco 17 setup (that won't age poorly)

Most Umbraco Setups Don’t Fail Immediately—They Fail LaterEvery new Umbraco project usually starts the same—fresh solution, everyone energized and maybe even a nice architecture diagram. For a couple weeks, life’s good. Everything moves quick, flows logically, and things feel buttoned-up.Then the real world shows up.Configuration starts drifting. What worked on your laptop doesn’t quite click on staging. Naming conventions get creative—sometimes even a little poetic—with no one quite sure which approach is the right one anymore. Deployment turns into a one-person magic show, full of rituals and half-remembered steps. Suddenly, what felt solid starts to make you nervous whenever someone asks for a change.Let’s be honest: Umbraco projects rarely blow up in the first week. Most problems show up months later, buried in the details.What does it take to build a setup that actually survives? Not just in someone’s imagination, but in production, with real clients pounding on it, editors making changes, deadlines looming. We’re talking about a setup that stays reliable and feels right six months—or even a year—down the road.Let’s dive into a straightforward, practical approach for an Umbraco 17 project that won’t fall apart just when you need it most.

Editor Friendly 404 Pages in Umbraco

How to create customizable 404 pages that editors can manage, with support for multi-site setups using a ContentLastChanceFinder.