Orchard 1.3.0 Upgrade
Orchard CMS, upgrade to version 1.3.0
Orchard version 1.3.0 was released on Mon Oct 3 2011 at 7:00 AM. And soon after that many of the Orchard sites that I visit were down. This gave me a clue to make sure to go thought the upgrade process several times on my machine, as it was obvious others were having issues.
I upgraded Locally several times, and in the upgrade from Orchard 1.2.4 site to 1.3.0, I got the same errors and issues on both tries.
I already knew that Lucene was going to be a problem as I tried to upgrade Lucene 1.3 to a Orchard 1.2.4 site and it killed it, so I copied the backup over and checked the hash code in the App_Data cache.dat and folder /dependency and dependency.compiled.xml entry from Lucene to make sure it was the same and that fixed that.
In the upgrade process it got two issues, Lucene as stated above and the Contrib.HtmlField.
I blogged about how to fix this here http://www.publiuslogic.com/blog/fix-orchard-module-installation/ . As I explained before any module installation problems can be fixed by removing the module.txt file, and to get it back like it was coping over the Modules/_backup files.
On my upgrade process I deleted the module.txt files and removed the statements for both modules in App_Data/dependency/ dependency.compiled.xml and dependency.xml, and the App_Data/cache.dat, file; Orchard removes the statements by it self after the module.txt file is removed.
I deleted the Lucene and Contrib.HtmlField folders and refreshed my site and all was OK.
Then all I had to do was finish the Orchard 1.3.0 upgrade by reinstalling the new 1.3.0 versions of Lucene and HTML.File field.
Orchard has several new features of which you have to turn on, Including the updates to the blog module.
You may have modules installed I do not so there could be other old installed modules issues. If you are having issues with upgrade check the updated modules lists on Orchard compare it to the versions of the modules installed on your site. if you have versions below 1.3.0 then they could be your issue, and just move the module.txt file out of the modules in question and it should be simple enough to find and fix your Orchard upgrade issue.
