This project is read-only.

Upgrading my Orchard 1.7 modules

Topics: Writing modules
Oct 30, 2015 at 12:55 PM
I'm returning to Orchard after not doing much work with it for a while.

I've done a trial upgrade of an Orcahard 1.7 site and some of my modules are not very happy. I think this is mainly down to the new way content parts are stored.

Is there any guidance on updating modules that were written for Orchard 1.7 and earlier?
Oct 30, 2015 at 10:09 PM
Despite the fact that most parts use Infoset storage these days, modules using database storage should still be able to use that, so the issues you're seeing may be something else. Perhaps you could share some of the unhappiness you're seeing? In any case, make sure the modules compile against the latest version of Orchard you're using.
Nov 5, 2015 at 10:37 AM
You're right. Not as painful as I thought. I was using a restored backup of a database and the permissions on tables for modules installed in production were wrong for my test machine. As my modules were complaining about tables not existing I jumped to the conclusion this was linked to infosets.

However, I would like to upgrade my modules to use infoset.

What would a migration look like that did this?