In this article we will look at something that used to keep me awake at night because I couldn't for the life of me figure out how it all worked: shapes, content types, parts, fields, drivers and placement. If you have some experience with Orchard, but still feel a bit shakey when it comes to shapes, then this post is for you.
In this post we'll see how to write a custom Workflows activity that adds content items to a list. The idea is that when a content item is created, it automatically gets added to the configured list. this could be useful when for example setting up a form with Dynamic Forms that binds input fields to new content items.
Although Autofac is not really part of Orchard's public API, it does come in handy when you need to customize how some of your classes are created and managed by Autofac.
When first starting out developing applications with Orchard, I remember well the need for more extensive documentation and samples on the API and concepts that exist in Orchard.I remember how glad I was to find Piotr's blog about the most important extensibility points. Although it didn't provide in-depth details, at least it pointed me to what services there were available, which helped me enormously getting up to speed. I kind of envy these guys who seemed to "get" Orchard as of day 1. It took me a whole lot longer before I gained creative freedom to build anything I needed with Orchard.
With Orchard, it's relatively easy to create your own content parts and editors. Typically you'll follow these steps:
Today I came across the need for a custom menu item type for a new platform being built on Orchard.For this application, a lot of custom controllers will be created, and the user will be able to navigate to the various screens using menus.So basically I needed to be able to map menu items to controller actions.
In this tutorial we are gonna checkout some of the new features that were introduced with the advent of Orchard 1.9.
Specifically, we are going to see how we can leverage Dynamic Forms and Workflows to create our own Login and Registration screens without the need for a custom module.
So shutdown Visual Studio (unless you're using it to launch IISExpress) and let's get started!
Today we will see what extensibility points Orchard provides that enable us to customize, override and take control over entity / database mapping.
LazyField<T> is a utility class that lives in the Orchard.ContentManagement.Utilities namespace and enables you to return a value in a lazy manner.It's public members are:
In this series we will be implementing a custom module to see what it takes to implement a Templated Messaging System that leverages not only basic Orchard stuff, but also more advanced APIs such as Rules, Tokens, Messaging, Channels, Site settings and Content Type/Part settings.
This is part 2 in a series of Orchard Module Development where we will be building a custom module that enables the user to create message templates that integrate with Rules and Tokens.
This is the 3rd part in a series of Orchard Module Development where we will be building a custom module that enables the user to create message templates that integrate with Rules and Tokens.
Today I am very excited! Today, we put up my very first e-book up for distribution. It's the book on Orchard Layouts.
Source code & PowerPoint slides used at Orchard Harvest 2013 Amsterdam for the Module Development Session provided below , demonstrating: