Make SqLite database name configurable, Select All checkbox UI updates, and a demo about making our Training Demo module as a standalone solution! Oh, and have we mentioned our very special limited offer for DotNest? Head to our post, and let's see the details! Orchard Core updates Make SqLite database name configurable This change sets the default database to OrchardCore.db for new sites. Existing sites that were created in the past using yessql.db will still work as before using yessql.db. This all happens seamlessly and does not introduce any breaking change. There is a new setting called DatabaseName that can be set to a custom name using the appsettings.json file. Here, you can see we just simply extended the AutoSetup example section by providing the name of the database. Select all Content Types This is about mainly updating the JavaScript code for the Select all content types checkbox. As you can see on the screen, you can select the indexed content types or the content types that you want to track using the Audit Trail feature by using the Select all checkbox. If you uncheck one of the content types, the Select all checkbox will be unticked but if you click on the Select all checkbox after that, every content type will be selected again. Demos Lombiq Training Demo module as a standalone solution The Lombiq Training Demo for Orchard Core is our Orchard Core tutorial module containing a lot of documentation that teaches you to become an Orchard Core developer. If you like to learn from code then this is for you. This is only about development and the basic concepts and not the user-facing part of Orchard Core. The point is that we have some simplification here. We got feedback over time that using the Training Demo is hard. Specifically, its context is hard to use because previously you had to use our Open-Source Orchard Core Extensions parent project. This solution contains all of Lombiq's Orchard Core-related projects as submodules. It also uses Node.js for client-side builds, linting, and whatnot. And to run that solution, you have to go through some setup steps. So, a lot of setup is needed just to be able to work with the Training Demo module. But not anymore! We simplified the Training Demo a lot and now if you clone this repository or just download the source code, you get a full solution with an Orchard Core web application with the Training Demo module. After that, you just need to hit F5 or CTRL+F5 if you are using Visual Studio, and it will run. No other dependencies or setups are needed, just .NET. Here we are using Visual Studio but that's not needed either, you can do this from the .NET CLI or you can use another IDE. When you start the application auto setup runs with a recipe to demonstrate the Training Demo. If you want to see this new solution in action, head to YouTube for a recording! News from the community DotNest is 10 years old DotNest is our content management framework as software as a service, for you and your clients. Sign up and create any number of Orchard Core sites you want. Don't worry about deployment, maintenance, and upgrades - your Orchard site just works. And DotNest just turned 10 this week! Celebrate it with our very special limited offer and launch your new site at a discount with free 1-1 consulting! Interested in creating your own Orchard Core site with just a few clicks? Check out this post for the details! Orchard Dojo Newsletter Lombiq's Orchard Dojo Newsletter has 477 subscribers! We have started this newsletter to inform the community around Orchard of the latest news about the platform. By subscribing to this newsletter, you will get an e-mail whenever a new post is published to Orchard Dojo, including This week in Orchard of course. Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here! If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Extending ISetupEventHandler with new events, do not specify placement position in the content field/part display drivers, and a blog post about the reliability of your DotNest sites! Let's see the details in our post! Orchard Core updates Extending ISetupEventHandler with new events We have an ISetupEventHandler interface in Orchard with a method called Setup. When there is a setup on a new tenant, we call this method. Now this method is marked as an obsolete one and will be removed in future releases. If you rebuild your Orchard Core solution in the future, it will tell you to use the new SetupAsync instead. If you have an implementation of this interface, it will still work because the newly added FailedAsync and SucceededAsync methods have default implementations. It means you don't need an abstract base class. Do not specify placement position in the content field/part display drivers Content elements or fields can be attached to a content type. Their UI placement should follow the subsequent guidelines. So, if the first step defines a position, we use that position and look no further. DisplayDriver. A placement is defined on the UI using the OrchardCore.Placements. The placements.json file. Default Position in the content type. Otherwise, it should fall back to the physical placement of the object in the content definition. For this logic to work as expected, the ContentPartDisplayDriver or the ContentFieldDisplayDriver should define a placement location by default, but not a placement position. This way, we can allow to change the order using Steps 2-5 as needed. In the following drivers, we seem to be defining a placement position that prevents the user from being able to change that position at all. FacebookPluginPartDisplayDriver BagPartDisplayDriver FlowPartDisplayDriver HtmlBodyPartDisplayDriver LiquidPartDisplayDriver MarkdownBodyPartDisplayDriver TaxonomyPartDisplayDriver TitlePartDisplayDriver For example, today if you use HtmlBodyPart, there is no easy way to change its placement because the HtmlBodyPartDisplayDriver defines a position 5. Meaning if you have a placement in the driver, there is no easy way to override it from the UI. If we leave these positions, blank it will fall back to the user settings. News from the community Your DotNest site (almost) never goes down Orchard Core and Orchard 1.x sites you host on DotNest almost never go down, with 99.99% availability in the last 3 months. Check out the details in our latest blog post here. If you haven't done it already and want to host your sites on the hugely reliable DotNest, create your site here! We also guarantee reliability in our Terms of Service. Orchard Dojo Newsletter Lombiq's Orchard Dojo Newsletter has 505 subscribers! We have started this newsletter to inform the community around Orchard of the latest news about the platform. By subscribing to this newsletter, you will get an e-mail whenever a new post is published to Orchard Dojo, including This week in Orchard of course. Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here! If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

Rename Microsoft Azure Active Directory to Microsoft Entra ID; improve workflows page load time, and announce Cloudflare CDN and protection for all DotNest sites! Let's see the details in our post! Orchard Core updates Rename Microsoft Azure Active Directory to Microsoft Entra ID A few weeks ago, Microsoft announced significant milestones for identity and network access, including the news that Microsoft Azure Active Directory (Azure AD) is becoming Microsoft Entra ID. We have Azure AD integration in Orchard Core, and in order to authenticate users with Azure AD, you must enable and configure the OrchardCore.MicrosoftAuthentication.AzureAD and the OrchardCore.Users.Registration features. You can read more about the details here. So, due to Microsoft's recent rebranding, Azure AD has been renamed to Microsoft Entra ID. This only concerns UI labels and documentation, but technical identifiers remain, so you shouldn't expect anything breaking. Improve workflows page load time It takes several seconds to load the /Admin/Workflows/Types and /Admin/Workflows/Types/{TypeId}/Instances pages when there are a fairly large number (testing size: 500_000) rows in WorkflowIndex. There is a line in WorkflowTypeController that goes through the whole table of WorkflowIndex to then calculate (group by) in the code how many workflows are there per each type. In WorkflowController line 124 with the await query.CountAsync() it is for the same purpose but for only one workflow type, but this uses some additional joins which makes it even slower. You can easily reproduce this by having a fairly large number of finished workflows. Load the workflows page, or the type-specific workflow item list page and see that it takes several seconds to load. This issue has been fixed by removing the counting of each workflow type on the workflows listing page. And on the workflow instances list page changed to only fetch the document table for the workflows that are on the current page. News from the community Cloudflare CDN and protection for all DotNest sites Last week you could read that we published a case study about migrating the content of an old version of an Orchard Core website with a custom theme and modifications in the business logic of the Orchard Core Commerce module to DotNest. You can check out the case study here about how we achieved this with Ik wil een tart, a confectionery in the Netherlands! And now all DotNest sites are protected and sped up by Cloudflare! Head to the DotNest blog and check out the details here! Orchard Dojo Newsletter Lombiq's Orchard Dojo Newsletter has 505 subscribers! We have started this newsletter to inform the community around Orchard of the latest news about the platform. By subscribing to this newsletter, you will get an e-mail whenever a new post is published to Orchard Dojo, including This week in Orchard of course. Do you know of other Orchard enthusiasts who would like to read our weekly articles? Tell them to subscribe here! If you are interested in more news about Orchard and the details of the topics above, don't forget to check out the recording of this Orchard meeting!

On the last (third) day of this year's Orchard Harvest we announced the results of the Orchard community's second module development competition, the Orchard Spring Harvest Challenge. The amount of submissions may be small ("only" 6), though in quality they certainly made up for it. The top 3 places are the following: MiniProfiler by Daniel Dabrowski Inline Editing by Matías Molleja Dynamic Forms by Cybage Software Pvt. Ltd. Congratulations to all participants! We also had the opportunity to bring in Daniel, the author of the winner module via Skype to the conference, where he did a live demonstration of the capabilities of the MiniProfiler module. For more information and the details about the event please visit its website and see the "Rules" page. If you'd like to know more about the last Orchard Harvest, you may want to read our reports written on-site about each day: Orchard Harvest - Day 1 Orchard Harvest - Day 2 Orchard Harvest - Day 3 Happy Orcharding until next time!

In case you haven't heard from the Lombiq content network and its neighbours, a module competition named Orchard Spring Harvest Challenge has begun yesterday! The aim of this contest is to give Orchard module developers some more motivation to upgrade their old modules to Orchard 1.8, or create new ones that are compatible with latest version of Orchard. You can find more information on the event's (DotNest-hosted) website.