Yes, 1.0.1 is identical to 2.0.1, so if you upgrade through 1.0.1 then you can use 2-01to2.1

We have 2 branches of mojoportal 1.x for 1.1 framework/mono and 2.x for 2.0 .NET, the schemas for both the 1.x and 2.x were identical as of 1.0.1 and 2.0.1
since then the 2.x branch has changed a lot in db schema while 1.x has not changed at all and will not change so that we do preserve this upgrade path for when mono 2.0 stack is ready

Clear as mud? 

Joe

I'll add some notes about that to the readme for this release.

At the end of upgrading your db you need to run the stored procedure script to get the latest ones.

The other challenge you will face in upgrading is if you have a custom skin, it will need some re-work to make it more like the new ones. You should set the site to a default one like subblue before you upgrade so it will be able to load a page as an older custom skin will likely be broken.

The new skins are xhtml compliant and use no table layouts, you can use table layouts in your custom skin if you like but there are other differences you'll have to look at the new skins and compare to your custom skin to know how to fix it.

Cheers,

Joe

Yeah I was afraid of that. I generated parts of the newest upgrade script on my broken SQL 2005 machine.
Do you think  it will be difficult to edit the script? I don't have a SQL 2000 machine at home anymore, I'll have to look through my virtual machines and maybe I can find one.

I woud like to fix that script and make it compatible.

Joe