Hi,
I'm currently seeing a new error in a custom module (a menu module developed by my co-worker). Fortunately, this is occurring on a test server version of our website. The module is still working fine on the live site. (Live site is running 7.1.2, and test server is running 7.2.1). I don't know what happened/changed to cause the error to begin occurring. (It worked fine through the last upgrade, and the problem began at some point more recently.)
What's interesting about the error, is that it only occurs in instances where the module is invoked through the skin file. When the module is placed on a page through Add New Module, it works. But when it's coded in the skin, (as I have done on many pages/skins) the error occurs consistently.
What I've also noticed is that if I add the module to a page where the error is occurring (since the module is already on the page as coded in the skin), it fixed the error for both instances. Then, both the skin-coded instance and the added module instance both seem to work OK.
Any ideas why this might be occurring and what might have caused it to begin suddenly? (The person who created the module is unavailable at this time).
Here is the error itself:
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.UI.SaviNavigation.GetNavigationNodes(DNNNode objRootNode, ToolTipSource eToolTips, Int32 intStartTabId, Int32 intDepth, Int32 intNavNodeOptions, Boolean showInvisible)
at DotNetNuke.UI.Skins.Controls.SaviMenu.GetNavigationNodes(DNNNode objNode)
at DotNetNuke.UI.Skins.Controls.SaviMenu.BuildNodes(DNNNode objNode)
at DotNetNuke.UI.Skins.Controls.SaviMenu.Page_Load(Object sender, EventArgs e)
--- End of inner exception stack trace ---
Thanks,
Tom