Our blog contains the activity stream of Orchard Dojo: general news, new resources or tutorials are announced here.

AI framework for .NET, New View Roles permission - This week in Orchard (28/08/2026)

Want to give support staff a way to see role definitions without letting them change anything? A new View Roles permission does exactly that.

Need to cap how long, or short, a text field's content can be? Text Field settings now support Minimum and Maximum length validation.

Building AI features outside of Orchard Core? CrestApps.Core brings the same AI Suite services to any ASP.NET Core project.

And signing into DotNest just got easier, with social sign-in via Microsoft, Google, GitHub, or Facebook.

This week's changes come from Matt Varblow, Antoine Griffard, and Mike Alhayek.

Latest tutorials

Hosting Orchard Core at Exoscale
zoltan.lehoczky
Step away from that Node.js
sara.el-saig

Featured tags

AI
SMS
IIS
MCP
API
SEO
SSL
All tags >

Agent Guidelines for Orchard Core, new marketing site on DotNest - This week in Orchard (30/01/2026)

Orchard Core 3.0 will be released soon! In this new version, we removed the default implementations from interfaces and obsolete members, which we cover in our post. You could also read about a new Agent Guidelines documentation that explains to LLMs how to build, test, and run Orchard. Don't forget to check out a case study on a new marketing website on DotNest! Without further ado, let's dive in!

Checking your infoset data consistency after upgrading from 1.x to 1.8+

Many Orchard developers, including ourselves act as early adopters of the Orchard source and use the code from the 1.x and other work-in-progress branches. While it gives us the opportunity to try the new features and get the latest bugfixes, some changes introduce important bugs every now and then. That was the case lately on the 1.x branch, when a problem surfaced regarding the infoset storage: for shifted, versionable content parts the infoset data was not saved in the ContentItemVersionRecord table, but into the ContentItemRecord table instead. Sébastien discovered this issue before 1.8 release and provided a method to fix it. At this moment, we are in the middle of upgrading all our sites to Orchard 1.8+ (+ means we are running 1.x, of course) and after careful testing in our local and staging environments we'll soon hit the big red button to make it go live: every Lombiq-related website will run on the latest source, that includes every DotNest tenant too! While upgrading your sites and testing the fix for the infoset storage, you may need to check if your data was really restored to its desired state, so here's a little help: below is an SQL-script that you can run against your DB, which checks if there's any corrupted infoset entry left, so you can verify if the upgrade mechanism worked. USE [MyDatabase]GOSELECT Item.Id AS ItemId, VersionItem.Id AS VersionItemId FROM [dbo].[MyPrefix_Orchard_Framework_ContentItemRecord] AS Item INNER JOIN [dbo].[MyPrefix_Orchard_Framework_ContentItemVersionRecord] AS VersionItem ON Item.Id = VersionItem.ContentItemRecord_id WHERE VersionItem.Latest = 1 AND VersionItem.Data IS NULL AND Item.Data IS NOT NULL ORDER BY Item.IdGO Happy upgrading!