Bug in the Orchard.Comments module migration


In the migration code in the UpdateFrom3 method in the Migrations.cs for the Orchard.Comments module the EnableSpamProtection column is incorrectly referred to as EnableSpamProtected. This causes the migration to fail during an upgrade to Orchard 1.6 from Orchard 1.4 - I didn't check whether or not it was introduced in Orchard 1.5. Changing the name in Migrations.cs fixed the problem for me and the module upgraded normally.


sncodeplex wrote Dec 10, 2012 at 1:10 AM

It seems that this failure in the Orchard.Comments migration caused a number of other migrations to be rolled back because the versions had been updated in Orchard_Framework_DataMigrationRecord but the database changes were not in the database, for example, the entry for Orchard.Core.Navigation.Migrations showed Version 3, but the Navigation_MenuWidgetPartRecord table was not in the database.

I have the logs from the failed migration if they would be helpful.

agriffard wrote Dec 12, 2012 at 12:48 PM

Fixed in changeset a74968d5fba3

sfmskywalker wrote Mar 28, 2014 at 1:28 AM

Fixed in changeset 8d8c53be2dd591811736886f26d50c9bf56bf7e4