Frozen DNN,

The way I did it was by going into the database itself with --> Microsoft SQL Server Management Studio Express (From Microsoft SQL Server 2005).
Here you can login into your db with the connection string data in your web.config.
Once in you go to your database --> tables --> dbo.Modules, right mouse --> modify and enter the columnname ModuleTitle with type nchar(254). Save the table and your done.

Succes.

But what is it what you should do then? When you want to add a module?

Frank

As Sebastian indicated, adding the ModuleTitle column back to the Modules table is NOT the correct solution to this problem as it simply hides the root issue - namely that part(s) of the 05.05.00.SqlDataProvider script failed to run properly to re-create the AddModule and possibly other stored procedures. It is also very odd that the 05.05.00.log.resources file does not show any errors having been logged. If this and other stored procedures were not correctly updated you are asking for data integrity issues and problems with later version upgrades. I am actually surprised that adding the ModuleTitle column back to the Modules table appears to work as I would have expected similar errors for the Header and Footer columns which were also intentionally removed from the Modules table in the 5.5.0 update.

Can anyone who is experiencing the "Invalid column name 'ModuleTitle'" error when adding a module post the script for the AddModule stored procedure from their database as it now exists after the upgrade to 5.5.0? I am interested to see if it is still the same as in version 5.3.0 when it was last modified. It would also be interesting to compare all of the other stored procedures which were modified in the 05.05.00.SqlDataProvider script with their actual contents in the database.

---

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