This project is read-only.

Call to all module authors to prepare for 1.4

Topics: Announcements, Writing modules
Feb 13, 2012 at 11:25 PM

Dear Orchard module and theme authors,

As you may know, we are currently preparing the release of Orchard 1.4. This is an important release in many ways, one of which unfortunately requires action on your part.

The new version features a complete refactoring of the way we handle URLs, in the form of new features called Autoroute and Alias. The old Routable part that was handling both permalink and title is now gone and replaced with Autoroute and the Title part.

There is a new UpgradeFrom14 feature in the 1.x branch that you can enable and that will add items in the admin menu to enable you to migrate your routes and titles from Routable to Autoroute and Title (it also has a feature that moves your data from existing Contrib field types to the new built-in fields but that is for another day).

In order to ensure that your module or theme works with 1.4 from day one, you'll need to try it with the latest in the 1.x branch as soon as you can.
If you don't have dependencies on routable, then your module is compatible and you don't have to do anything. If not, you will have some minor refactoring to do.

First, check your module.txt or theme.txt for dependencies that need to be replaced.
Second, if your code uses the title property on the routable part, well, in fact your code may already not be optimal. The recommended way to get the title of a content item is through the content manager:



For all other title needs, rely on TitlePart instead of Routable. For example, you'll want to modify your migrations so that your content types add Autoroute and Title instead of Routable.

Finally, if you have code querying on the route part, you will have to modify those queries to work with Autoroute instead. Here is an example of such a query:


var container = _contentManager
    .Query<AutoroutePart, AutoroutePartRecord>()
    .Where(c => c.DisplayAlias == slug)


Of course, please feel free to ask me any questions on this, preferably on the forums, so others can benefit from the answers.

Cheers, and thank you for your continued support,


Feb 15, 2012 at 10:45 AM

I've downloaded the latest version of the 1.x branch but some modules like Orchard.Alias, Orchard.AutoRoute,etc. are not yet included. Do we (module creators) have to download them separately and add them to the solution till the official 1.4 version is released?

Feb 15, 2012 at 12:59 PM

They should be automatically included as subrepos if you have a repository enlistment.

Feb 15, 2012 at 1:33 PM

cool thanks: here the how to url :

Feb 15, 2012 at 2:02 PM
Edited Feb 15, 2012 at 3:01 PM

Which url do i have to use to clone because the following downloads the v1.4 release:

update: i understand now. You have to update to the latest revision after you've cloned the repository.


Feb 15, 2012 at 6:04 PM

Did you "update" to the 1.x branch ?

Feb 15, 2012 at 6:31 PM

Yes i did and it worked. thanks

Feb 16, 2012 at 4:30 PM

How stable is autoroute branch right now? How many have migrated to it? 

I stayed away so far due to being new to Mercurial and didn't want to deal with figuring out how to revert or switch between branches yet, and I also have live demos to conduct this week so I wanted to stick to known stable code. Thinking about trying it out this week though. 

Feb 16, 2012 at 7:32 PM

The main issue is that not all modules that you may use have a compatible version yet. I highly recommend you take the update experimentally, on a separate clone of the repository, so you can test and report problems you find. We need to know what works and what doesn't now, so we can fix before launch.

Feb 16, 2012 at 7:37 PM

But also please do it now, and not after the release, or it will be too late ;) So please proceed !

Feb 16, 2012 at 10:40 PM

I set up a separate clone for the tip of 1.x branch. I'll test it with my app over the next few days. 

I haven't used Drupal or Wordpress before, but I'm curious to know how autoroute compares to the routing systems that they use. Is anyone able to give a brief overview of Orchard (autoroute) vs Drupal vs Wordpress? Do we have any features that they don't? 

Feb 16, 2012 at 10:50 PM

Autoroute is almost exactly what Drupal has (their module is called autopath). WordPress is, I believe more constrained: it is after all not a full CMS but was designed around the blog/post idea. I think it gives you a choice of patterns you can use but I'm not sure how extending those patterns works. I think you can write plug-ins that implement new patterns but I have never heard of a token-driven system that you can manage from the admin. Then again I may be wrong. Any WP specialist around who could chime in?

Feb 28, 2012 at 4:22 AM

I've just tried cloning a separate copy of the repository, and used the Update command to switch to the 1.x branch. Opened Orchard in Visual Studio, built everything with no error, pressed Ctrl+F5 and ended up with the VS development server simply showing a list of files at the site's root. The same thing happened when I tried on a different computer two days ago. Am I missing something?

Feb 28, 2012 at 4:35 AM

Do you have any custom or 3rd party modules running? Or are you running a custom recipe? Is orchard.web\web.config in place? 

Check the error log in app_data\logs\

Feb 28, 2012 at 6:03 PM

You need to go to /admin directly, then enable the UpgradeTo14 module, then go to the new Migrate to 14 section, and upgrade all your content types. Then you use your website. Please give us any feedback soon.


Feb 29, 2012 at 1:26 AM

Thanks for the help. The /admin shows up and asks me for an account and password. However I have none because this is a new environment. Do I need to first build it as 1.3 then upgrade to 1.4?

Feb 29, 2012 at 1:40 AM

When you went through setup, you have entered an admin password. Or are you looking at setup right now? If so, you just need to come up with an account name and password.

Feb 29, 2012 at 2:19 AM

There's no setup. I cloned the repository then updated to 1.x directly. I went to src and built then when I hit F5, I get an exception in ShellRoute.cs, line 140:

The controller for path '/OrchardLocal/' was not found or does not implement IController.

If I keep going, the VS development server just gives me a directory listing. So if I try /admin/ then I did get to first set a password.

Feb 29, 2012 at 2:30 AM

Don't try to debug, these are excepted exception. Just hit CTRL+F5 then go to /admin

Feb 29, 2012 at 2:33 AM

Full circle: when I get to admin I don't have a password to enter because I never had a chance to set one.

Feb 29, 2012 at 2:38 AM

Start over, you did something wrong. Also, this is off-topic, it should be on a different thread.