We're testing a site upgrade from DNN 3.0.13 to 3.3.7.  The only thing that has us totally stumped is that the Text/HTML module is "not available".  You can drop a new Text/HTML module onto a new page and it works fine ... until you put content into it, then (although the content gets persisted to the db) the module becomes "unavailable".

The specific error is a NullException that occurs in the module page_load.  What's null is the HtmlHolder property.  This particular property appears in HtmlModule.ascx and no place else, and only twice: when it's declared and when it's accessed in the page_load.  I imagine it's actually populated by an event that's not happening.

Anyhoo ... anyone have any idea what HtmlHolder is *supposed* to be?  FreeTextBox, maybe?  Also, can anyone point us in the direction of a solution?   Log dump is below.

Thx,

--Bob

ModuleId: 1480
ModuleDefId: 102
FriendlyName: Text/HTML
ModuleControlSource: DesktopModules/HTML/HtmlModule.ascx
AssemblyVersion: 03.03.07
PortalID: 25
PortalName:
UserID: 1
UserName: host
ActiveTabID: 746
ActiveTabName: World Team
RawURL: /dnn33/PTICentral/WorldTeam/tabid/746/Default.aspx
AbsoluteURL: /dnn33/Default.aspx
AbsoluteURLReferrer: http://localhost/dnn33/PTICentral/NewReports/tabid/773/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; Feedreader; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: f0ad5f43-88ff-4408-bf3b-4f4e644cbf00
InnerException: Object reference not set to an instance of an object.
FileName: C:\pti_dnn3\DesktopModules\HTML\HtmlModule.ascx.vb
FileLineNumber: 107
FileColumnNumber: 6
Method: DotNetNuke.Modules.Html.HtmlModule.Page_Load
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Html.HtmlModule.Page_Load(Object sender, EventArgs e) in C:\pti_dnn3\DesktopModules\HTML\HtmlModule.ascx.vb:line 107 --- End of inner exception stack trace ---

We were running v3.1 of this module.  I upgraded to 3.3 and it works now.  Thanks.

Where, if anyplace, is the guidance for what module versions are compatible with what DNN versions?  (I'm talking about those offered as projects from this site, I understand that vendors / authors would have to be consulted regarding 3rd party modules).  It doesn't seem right to go through whole-hog and upgrade everything, because some modules may have dependencies in DNN 4.x and I'm only taking this as far as DNN 3.3.7 at the moment.

As an aside, I wonder about the wisdom of offering core updates that do not address or at least flag / warn you about breaking changes to existing installed modules.  Judging from what I can find here and elsewhere on the net, DNN upgrades are needlessly painful, partly for this reason.

Ultimately in getting this rolled out we found that we needed to update the Links module to the current version as well.  That one shows on the download page as requiring at least DNN 3.0.13, which is the version we were upgrading from.  I tried to upgrade Links on that 3.0.13 installation and it failed with various DB errors.  So did the Text / HTML module.  However they both upgraded fine once I had actually upgraded the rest of the site to DNN 3.3.7.

From this I have to conclude that documented minimum requirements in the manifest or elsewhere may or may not actually be accurate.

At any rate we seem to have whistled past the graveyard on those modules and the site appears to be working correctly.  I will work in the other module upgrades one at a time over the coming weeks and keep my fingers crossed.

Thanks again for your help.

--Bob