Orchard Core updatesOrchardHelper content APIs should be accessible without namespaceIn previous versions, you needed to use the OrchardCore namespace in Razor pages or views to access the content helpers provided by IOrchardHelper. This is unlike other services, which can be accessed directly without needing the namespace. Starting with Orchard Core v.3, we have removed the need to use the OrchardCore namespace in Razor pages or views to access the content helpers. You can now access the content helpers directly, without needing to use the OrchardCore namespace. Note that the ContentRazorHelperExtensions has been replaced by ContentOrchardHelperExtensions.

Orchard Core updatesFluid 2.21.0Fluid 2.21.0 has been released, and now you can utilize all of its goodies if you are using the nightly build of Orchard Core! Let's check out some of the new changes!

Orchard Core updatesEnsure Content Type Restrictions are Enforced for Drag & Drop in WidgetsThis is about fixing an issue when using drag & drop in the widget zone, content type restrictions were not applied. Let's say we have a Page content type with a Flow Part attached. Our goal here would be to be able to add PageSection widgets to our Page. And the PageSection widget also has a Flow Part attached, but users can only add the built-in Paragraph widgets. This means that when users create a new Page content item and add a PageSection widget, they will have two different Flow Part editors.

DotNest has been available in the Azure Marketplace and Microsoft AppSource for quite a while. Both of these marketplaces are for people looking for Microsoft-adjacent technologies, and you could discover DotNest there. However, until now, you couldn't actually create and manage DotNest sites within the Azure Portal. But now you can!

Orchard Core updatesValidate HTML Input Name in FormInputElement PartThis addition includes several changes to the OrchardCore.Forms module to improve input validation and enhance the user interface. The most significant changes include adding a new method to sanitize input names, updating the form element part definitions, and modifying the display template for form input elements.

Orchard Core updatesAzure Search AI Module enhancementsThis enhancement includes several changes to the OrchardCore.Search.AzureAI module, focusing on improving index creation and settings management and adding support for recipe execution steps. The most important changes include modifying the index settings service methods, updating logging messages, and introducing new service classes and handlers. It also updates the AdminController to improve the handling of search index settings and operations.

Orchard Core updatesUse the history plugin for Trumbowyg editors by defaultLet's say you set up your site using the Agency recipe, and you want to customize the built-in Landing Page content item and utilize the Trumbowyg editor to edit the content of the Service and Project content items. You can do that because both content types have the HtmlBody Part attached, and you can set the editor type to Trumbowyg for both types. But there is an issue with that.

Following the migration of lombiq.com, Git-hg Mirror, Hastlayer, and Orchard Dojo from Orchard 1 to Orchard Core (and also the redesign of lombiq.com and Orchard Dojo), we had only one site remaining that was still running on Orchard 1: DotNest.com. While you could create Orchard Core sites on DotNest for years, until now, the DotNest website itself still ran on Orchard 1.