Recent Posts and Articles
In some cases, when upgrading your Orchard instance, you may see something like this in your logs and wonder, “what the hell is going on??”:
Orchard.Environment.Extensions.ExtensionManager - Error loading extension 'XXX’
System.TypeLoadException: Inheritance security rules violated by type: ‘XXX’. Derived types must either match the security accessibility of the base type or be less accessible.
This is because of some changes to assembly-level security in Orchard.
When it comes to rendering a given content item, Orchard splits it in a zones, like Header, Content and Footer. The markup produced by each of the parts contained in an item is then dispatched to one of those zones. That is what Placement.info files are mainly used for – they tell the rendering engine in which zone to put a given shape’s final markup.
But what to do if you’d like to have the whole zone (eg. a Header) wrapped up in some custom markup? And what’s more – you’d like it to do in unobtrusive way, so no matter how the whole item is rendered (whether there are some shape alternates or not) – you want a given zone to be always displayed as you want it to be.
I’ve recently came up with a nice technique for doing that. First of all – zones inside a given content item are nothing more than… ordinary shapes! So you are free to attach a wrapper to them.
Who knew a broken link could actually be useful? In this article, smartly set-up as his own site's 404 not found page, David Hayden teaches us how to create our own personalized 404 and 500 error pages in Orchard.
As promised, I have been blogging about undocumented and relatively unknown changes in Orchard 1.4 after blogging about What's New in Orchard 1.4. We all know about the new Projector Module, Autoroute, and the new Orchard Fields and performance enhancements, but there are a lot of other changes in Orchard 1.4, too. First, I blogged about how DataMigration Classes in Orchard Automatically Update, which is something useful to Orchard Web Developers who develop custom Orchard Modules. Now I want to talk about the "missing" edit links around content and widgets, which is important to those administering Orchard Websites.
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.