Community Blogs

Umbraco Features with Claude Worktrees

Running several Claude Code sessions on one Umbraco site? Here’s the PowerShell hook that gives every git worktree its own database, media and ports.

Cascading Country and Location Dropdowns in Umbraco Forms, with Email Routing per Location

How we built a dynamic country and location dropdown in Umbraco Forms that sends each enquiry to the right location's contact using a single email workflow.

Umbraco 13 End of Life: Why You Should Migrate from Umbraco 13 to 17 Now

Umbraco 13 and .NET 8 lose security support by December 2026, leaving sites exposed and putting Cyber Essentials certification at risk. Here’s why and how to migrate to Umbraco 17.

Introducing Engage Healthcheck: what state is my Engage database in?

A free, read-only tool that tells you which Umbraco Engage version your database is on, and what differs from it. A personal open source project.

Umbraco testiesimerkit nyt Umbraco 18:lle

ℹ️ Opin suomea Tämä on mulle harjoitus oppimaan suomea. Voit myös lukea englanniksi. Olen päivittänyt testiesimerkkirepositorion Umbraco 18:ksi. Tässä on muutokset: Tärkein muutos: end-to-end testiesimerkit ovat muuttuneet typescriptiin Ensin, testit olivat dotnetiksi, mutta olen muutanut niiden typscriptiin. Olen päätänyt sitä koska C#:n generated clientin päivittämisen Umbraco 18:lle oli tosi vaikea. Mun piti käyttää ruma work-aroundia tai muuttaa sen manuaaliseen toteutukseen. Molemmat tuntuivat pahalta. Lisäksi, dotnetissa Playwrightilla on kovat haitat, jotka Node:ssa Playwrightilla ei ole. Kerron lisää uudesta end-to-end testista typescriptissa toisessa blogissa. Published content on muuttunut Umbraco on siirtänyt muutamaa ominaisuusta IPublishedContent:sta IPublishedElement:iin. Olen päivittänyt unit-testing esimerkien niin että ne toimivat Umbraco 18:ssa. Nämä muutoksilla ei ole vaikutusta unit-testiin. Lisähuomautus Umbraco oli muutanut Umbraco 17:ssa miten indexit ovat alustaneet. Muutokset yksinkertaistavat in-memory sovelluksen ja se tulee helpompi tarkistaa onko sovellus käynistänyt integration testissä. Repositorio ei ole vielä ajan tasalla noiden muutoksien suhteen. Kohta päivitän integration testiä. Siinä on kaikki päivitys oli lyhyt. Vain end-to-end testit ovat paljon muutuneet. Jos et ole vielä katsonut, menee repositorioon nyt. Se on oppiopas aloittamaan testata Umbracossa.

Umbraco testing examples now also for Umbraco 18

I updated the testing reference repository to support Umbraco 18! Here are the changes: Most important: End-to-end testing examples have been migrated to typescript. It used to be in dotnet, but I changed it into typescript. I made this decision because updating the generated C# client for the Management API to Umbraco 18 was very difficult. I would have had to either use ugly work-arounds or replace the generated client with a manual client. Neither option seemed right to me. In addition to that, I had already noticed that Playwright in dotnet had significant downsides compared to Playwright in node. I will share more about how the new tests work in a separate blog. Published Content has changed Umbraco has moved several properties from IPublishedContent down to IPublishedElement. Those changes have been mirrored in the unit testing examples in the FakePublishedElement and FakePublishedContent types. These changes have no effect on existing unit tests. Additional note Umbraco has already made changes in Umbraco 17 to how indexes are initialized on boot. The changes reduce the complexity of the in-memory website and make it easier to detect when Umbraco has fully started in integration tests. The repository does not reflect those changes accurately quite yet. I have the code ready for it and I will update the examples soon. That's all It was a short update. Apart from the end-to-end testing examples, not much has changed, everything is still relevant. If you haven't yet, please check out the repository, it is made as a learning resource so you can also get started with testing in Umbraco.

Articulate 7 and 8 are out for Umbraco 17 and 18

Articulate 7.0.0 and 8.0.0 are now on NuGet. Articulate 7 is for Umbraco 17 and Articulate 8 is for Umbraco 18. They're both built from the same source, the only reason there's two of them is that Umbraco 17 and 18 aren't binary compatible, so each package is compiled against its own Umbraco version. dotnet add package Articulate --version 7.0.0 # Umbraco 17.7.1 - 17.x dotnet add package Articulate --version 8.0.0 # Umbraco 18.2.1 - 18.x This blog is now running Umbraco 18.2.1 and Articulate 8.0.2. Before this it was on Umbraco 12.3.10 and Articulate 5.2.2, so it skipped quite a few versions in one go. In this case, the upgrade path was easy! Just exported the BlobMl from the old site with images embedded, then created a new v18 site, installed Articulate, imported the file and adjusted my root Blog Articulate node, and ta-da 🎉 It works 😊 What's new Giscus comments - You can now use Giscus instead of Disqus, which stores comments in GitHub Discussions. Configure it globally in appsettings.json under Articulate:Comments:Giscus or per blog with the new giscus* properties. Themes can ship a giscus.css so the comments match the theme, and all the built-in themes do. Markdown editor - The responsive Markdown editor for posting from your phone or browser now signs in with Umbraco's Back Office OAuth/PKCE flow and uses the Management API, so if you have 2FA configured it just works. Rich text - Coming from TinyMCE, the upgrade switches posts over to TipTap with Articulate's default settings, and any custom TipTap config you already have is kept. New backoffice - The Articulate backoffice extensions are rebuilt for both Umbraco 17 and 18. BlogML - Import size limits are configurable, and exports use the post's published date. Performance and security - Lots of allocation and hot path fixes in routing, and CI now fails the build if any NuGet dependency has a high or critical advisory. Things to know before you upgrade Back up first - your site, database and media. MetaWeblog is off by default - Open Live Writer uses direct username/password auth, which skips Umbraco's Back Office OAuth and 2FA. If you still use it, set Articulate:EnableMetaWeblog to true and restart. Want to keep TinyMCE? Install TinyMCE.Umbraco before the first run, otherwise the editor gets converted to TipTap. Coming from Articulate 5? Custom themes need updating, since the Html and Url helpers were replaced with model extension methods, e.g. @Html.MetaTags(Model) is now @Model.MetaTags(). The full table is in the 6.0.0 release notes. The Upgrading page on the wiki has the full checklist. Two packages, one codebase The bulk of this release was done by Gavin Faux, and it's a huge amount of work. Rather than keeping a separate branch per Umbraco version, everything is built from one codebase with a small compatibility layer for the bits that differ between 17 and 18. One CI build compiles, tests and packages both versions, then installs them into brand new Umbraco sites and runs the same set of end-to-end tests against each one before a release gets published. So when a fix goes in, it ships for both versions at the same time. Thanks Gavin! The full list of changes is in the GitHub release. Give it a go, and if you run into anything, raise an issue.

Automatic log cleanup for Umbraco

Umbraco Cloud now cleans up old NuGet packages automatically. Unlog tackles the logs left behind, keeping recent messages and preserving errors for longer, on Cloud or wherever you host Umbraco.

Umbraco UK Conference

My recap of the Umbraco UK Partner Summit and Umbraco UK Conference in London: great talks, good friends, whisky and a lot of Biscoff doughnuts.

My First Umbraco UK Conference 2026: AI, Great Conversations, and the Umbraco Community ❤️

Umbraco Upgrade Decisions: Upgrade or Rewrite

If a site genuinely needs to change, the next decision is whether to upgrade it or rewrite it. In this post, I look at what a major version upgrade actually involves, when upgrading or rewriting makes more sense, and what each option costs in practice. Continue reading

Giving AI agents tools for the Umbraco backoffice with WebMCP

Chrome's new WebMCP API lets a page hand an AI agent a list of named tools, so I tried it on the Umbraco 18 backoffice to see whether an agent could get around it, Umbraco Forms included, without reading a single screenshot.