I've built a local test copy of my DNN 4.3.5 site, in hopes of upgrading it. The situation isn't identical: the production site is hosted and uses SQL Server 2000 and ASP .NET 2.0, while the local copy is on a Vista Home Premium laptop running IIS 7, SQL Server 2005 Express and .NET 3.0. Pretty much everything either works, or fails in a predictable way, with one exception.
We have several instances of the Gallery module which we use to display photos. The files are all there on the test site, including the photos; the database was restored from a backup of the production database. But the instances of the Gallery don't exist. A page which had a gallery has this error:
|
A critical error has occurred.
Object reference not set to an instance of an object. |
In addition, either there is NO visible module, or there is a module with a visible title, but with no module handles - no arrow in the upper left corner allowing editing etc., no "settings" icon in the lower right corner. I tried installing a test gallery module, and got a module with some handles - you could move it or delete it, but there was no edit function, and the module settings icon led to a generic "module settings" page with no mention of special gallery settings.
Strictly speaking, I can do what I meant to, which is to validate the upgrade process on the test version. But since I don't know why the gallery modules are hosed, I can't rule out the possibility that it relates to the different SQL server version. In other words, does the gallery module require SQL Server 2000? This could be a roadblock, because I want to upgrade to 5.x.
Advice or suggestions gratefully accepted. I really don't want to lose the gallery function during an upgrade. I'm hoping someone else has seen this and knows what it is.