Fix 1.0 to 1.1 migration issue

SiteSettings are used very early and often in Orchard, so we
can't rely on having the user be able to run migration for
SiteSettings. The workaround for 1.1 is to move the changes
we did to SiteSettings into a new SiteSettings2 Part/Record.

With this change, database compatiblity from 1.0 and 1.1 seems
to be in a good working state on a real blog site.

--HG--
branch : 1.x
This commit is contained in:
Renaud Paquay
2011-04-07 18:29:23 -07:00
parent 6b7efb2b8f
commit db3046f68f
7 changed files with 38 additions and 11 deletions

View File

@@ -197,6 +197,8 @@
<Compile Include="Scheduling\Services\ScheduledTaskManager.cs" />
<Compile Include="Scheduling\Services\ScheduledTaskExecutor.cs" />
<Compile Include="Scheduling\Models\Task.cs" />
<Compile Include="Settings\Models\SiteSettings2Part.cs" />
<Compile Include="Settings\Models\SiteSettings2PartRecord.cs" />
<Compile Include="Settings\ResourceManifest.cs" />
<Compile Include="Settings\Migrations.cs" />
<Compile Include="Settings\Drivers\SiteSettingsPartDriver.cs" />