Recent Posts and Articles
As with many others that switch to a new blogging engine, I wanted to be able to change my theme fast and without too much of a hassle.
Normally, the first part is easy. If you know your way around in asp.net mvc and if you understand some razor, then you will find yourself in known surroundings. It is easy to change some colors, some views and other things, by working on the CSS and _Layout.cshtml files. No need to worry there.
When that is done, you probably want to start tweaking the look and feel by adding information, removing information, changing how information is shown.
I've talked about the main new features in Orchard 1.4 in a number of Orchard CMS Tutorials. Various features like Autoroute, Projector Module, new custom fields, and Orchard performance enhancements are a wonderful addition to Orchard. Now I would like to write a series of blog posts about those features in Orchard 1.4 that aren't so obvious and probably not even documented. Unless you are an Orchard Web Developer who has been developing Orchard Websites for quite some time, you are probably not even aware of these changes. First Up - Orchard Data Migration Classes Automatically Update in Orchard 1.4.
Recently we had the problem getting lots of spam by our new website that we rebuilt using the Orchard-Framework.
So we had to find a way to fight against Spam-bots. First we tried the Orchard.Captcha Module that could be found using the Gallery. After the installation and activation of this Module the Settings of our Website could not be loaded.
The reason was an bad designed database-entry that causes a NULL-Value inserted into a non-Nullable column in the SQL Database. Also there was a compile error, because there was a reference to an Assembly that is not used. After we made this project compileable, we found no documentation on how to use this Module. So we decided to try another way.
After a short search we found out, that Microsoft already has a Captcha support in their Microsoft.Web.Helpers Library. Since Orchard is built using MVC and @Razor, it should be possible to use and integrate it into the Orchard Project. In the sample below you can read how to integrate the Captcha of the Microsoft.Web.Helpers library into the Orchard.Comments Module.
Orchard 1.4 was released the other day and has some very important features as well as a lot of bug fixes and performance enhancements. It also comes with some breaking changes that will make upgrading to Orchard 1.4 a bit more effort. Since the Orchard 1.4 release notes just don't capture the coolness of this release, I thought I would play Orchard Developer Evangelist for a day and provide much more detail and context around the new features in Orchard 1.4 and why now is a great time to learn more about this ASP.NET MVC Content Management System ( CMS ).
The main new features in Orchard 1.4 include Autoroute and Alias, Projector Module, and new Fields.
The Rules module in Orchard enable you to set-up “if this then that” types of rules. The system is fully extensible in terms of what “this” and “that” are of course, but Orchard comes with everything you need out of the box to set-up comment notifications. Let’s create this rule...
Finally! Today we officially announced the new Orchard release - version 1.4. It's a big step forward from the previous, 1.3.10 version, both in terms of performance and features.
Unfortunately, it comes with a price... There are some breaking changes which might cause some modules to stop working. Especially those modules that utilize the routing features (ie. deal with all the items accessible by URLs). It also affects the Advanced Menu module, so the current 1.3 version won't work with Orchard 1.4 out-of-the-box. I'll be submitting the compatible version to the Gallery tomorrow.
You can find detailed information on the release notes page.
One of the new features in Orchard 1.4 is Autoroute, which like most features, arrives in the form of an Orchard Module. Autoroute is a new Content Part that attaches to Content Types and replaces the Route Part to offer much more flexibility in routing patterns for routable content types. Autoroute provides the ability to create and select custom route patterns, override patterns on a case by case basis, and the ability to regenerate the route when new versions of the content item are saved. In addition to specifying static values in the routes, Autoroute also leverages tokens in Orchard that allow you to create routes based on dynamic information such as creation date, user, and other information that may vary from content item to content item.
Drivers in Orchard are responsible for taking content parts and using them to generate shapes for the rendering engine to transform into HTML. A little known fact is that there can be more than one driver for any given part. You might be wondering what this can be used for: one shape per part seems like a reasonable assumption.
I’ll show one case where this ability to add a driver to the one that already exists came in really handy.