Many Orchard developers, including ourselves act as early adopters of the Orchard source and use the code from the 1.x and other work-in-progress branches. While it gives us the opportunity to try the new features and get the latest bugfixes, some changes introduce important bugs every now and then. That was the case lately on the 1.x branch, when a problem surfaced regarding the infoset storage: for shifted, versionable content parts the infoset data was not saved in the ContentItemVersionRecord table, but into the ContentItemRecord table instead. Sébastien discovered this issue before 1.8 release and provided a method to fix it, along with a well-detailed description on the Orchard discussion board.

< More >

Sébastien just tweeted about his new blogpost to tell you how Orchard manages the content items' data in the database by demostrating simple use-cases and the corresponding queries. It's a great read even if you're new to Orchard or a seasoned veteran!

< More >

Forum topics from the Orchard discussion board that we found interesting:

• Running Orchard on two nodes: this is a tricky thing but in this discussion there some good tips
• Community features in Orchard: a lot of built-in and third-party modules bring "social" functionality to Orchard. You won't be able to just install Contrib.Facebook but there are some decent fundamentals.
• A tale of database table locking, transactions and low-level data access in Orchard: sometimes you just have to bury deeper.

< More >