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

Orchard Harvest 2026 program, Your website should integrate with your business systems - This week in Orchard (26/06/2026)

The full Orchard Harvest 2026 conference program is live, with the event taking place in Vancouver on September 10-11. Grab your early-bird ticket for just $280 and join the community for two days of sessions and networking!

Form submissions shouldn't end up in manual copy-paste routines. Orchard Core connects directly with Zapier, Make, and n8n to automatically trigger CRM updates, notifications, and more. DotNest's managed hosting makes the whole setup hassle-free!

The Health Checks module by Hisham Bin Ateya lets you restrict access by IP, apply rate limiting, and DoS protection for your health check endpoints, all configurable via JSON.

Managing multiple tenants on the same database just got easier. New RequireTablePrefix and TablePrefixPattern options, introduced by Mike Alhayek, let you enforce or auto-generate table prefixes (e.g., using the tenant name), so your setup is consistent and error-free out of the box.

No more guessing which properties to use for the Settings recipe step. Every module with configurable settings now includes a dedicated Recipe Configuration section with examples!

Ready to explore? Let's dive in!

Latest tutorials

Featured tags

AI
IIS
SMS
MCP
API
SEO
All tags >

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!