In DotNetNuke v 5.5.0, there were a few schema changes in core database tables. The ModuleTitle, Header and Footer columns were dropped from the core Modules table since those same columns were moved to the TabModules table several versions ago. For those modules which directly queried the core Modules table for ModuleTitle rather than obtaining that data via the core API's, this was a breaking change.

Both the core Html and Events modules were affected by the change but had new releases included in the 5.5.0 packages. Third party modules such as DotNetMushroom either have or will need to release new versions that are compatible with this database schema change. Please contact DotNetMushroom directly to find out if an upgrade is yet available.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

With v5.05.0 I'm getting this Invalid Column Name error as well.  SSMS shows the ModuleTitle column exists in both the dbo.Modules and the dbo.TabModules tables.  The dbo.AddModule stored procedure shows that it will attempt to add the ModuleTitle to the dbo.Modules table - not the TabModules table. Values for all modules added (successfully) seem to appear in ModuleTitle within the dbo.Modules table and as null in dbo.TabModules.  There are no triggers associated with either table that I can find.  Would this indicate that the schema update failed when I upgraded (ModuleTitle, Header and Footer all exist within both tables).

Thanks