The PORTAL-DOORS Project has been running on the DotNetNuke framework for web site content management. There are both pros and cons to using a content management system (CMS) such as DotNetNuke. And it always seems that many of the cons appear when upgrading versions. Even when an upgrade of the core framework goes smoothly, some pages in the web site may break if they depend on third-party modules that have not themselves been upgraded properly for compatibility with the new version of the framework.
So it goes. Today I upgraded this site from DotNetNuke 5.4.4 to 5.5.0 and the upgrade itself worked flawlessly. But the page for this blog broke because the NukePress 5.2 blog module is not compatible with DotNetNuke 5.5.0. NukePress expects to find the columns ModuleTitle, Header and Footer in the DNN Modules table. But the upgrade to DNN 5.5 deletes these columns (see lines 1655-1679 of 05.05.00.SqlDataProvider), and that causes the NukePress 5.2 blog module to break.
Since there are apparently no accessible stored procedures associated with the NukePress module (instead LINQ queries appear to be executed from the dll assembly), the problem can be fixed simply by restoring the columns ModuleTitle, Header and Footer to the DNN Modules table. Hopefully, Ingen Systems, the developer of NukePress, will provide a patch or an updated version of their module. Otherwise, the fix described here should do the trick for anybody else using NukePress who wants to upgrade to DotNetNuke 5.5.