Germany requires support to some extent for EN 16931 from January 2025. And other EU countries will follow them soon. Under the EU’s VAT in the Digital Age (ViDA) initiative, structure eInvoicing will be mandatory for cross-border B2B transactions from 2030.

Orchard Core updatesNew page_title_add_segment Liquid tagThis newly added tag is similar to the existing page_title tag, but doesn't render it. It allows changing the page title from any Liquid view, similar to accessing the RazorPage.Title property in Razor.

Orchard Core updatesNew Filters in FluidThere are two new Liquid filters in Shopify that convert a string into a hash. The hmac_sha1 filter converts a string into an SHA-1 hash using a hash message authentication code (HMAC), and the hmac_sha256 filter converts a string into an SHA-256 hash using a hash message authentication code (HMAC).

Orchard Core updatesImprove Title Part settings by hiding the Pattern field if it doesn't applyThe pattern of a Title Part is only taken into account if the part is set to GeneratedDisabled or GeneratedHidden. This change hides the Pattern field in the Title Part settings if it is not applicable and removes outdated hint text.

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!