Hello all, I'm in a bit of a catch-22: DNN tech support doesn't provide support for third-party vendors and the vendor indicates it is unrelated to their products. So thanks in advance for your help.
I've been steadily updating our version of DNN from 8.4.1 up to 9.6.4 (Evoq Content). Up through 9.1.1, Mandeeps Live Accordion/Tabs were working fine. By 9.6.1, I would get page load exceptions/critical errors when clicking on "Manage" or "Settings" in their products, or clicking the "Activate License" link. Here's the stack trace:
InnerMessage:Object reference not set to an instance of an object.
InnerStackTrace:
at DotNetNuke.Web.Client.ClientResourceManagement.ClientResourceManager.RegisterStyleSheet(Page page, String filePath, Int32 priority, String provider, String name, String version) at DotNetNuke.Web.Client.ClientResourceManagement.ClientResourceManager.RegisterStyleSheet(Page page, String filePath) at Evoq.PersonaBar.UI.Controllers.EvoqPersonaBarContainer.Initialize(UserControl personaBarControl) at Dnn.PersonaBar.UI.UserControls.PersonaBarContainer.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at DotNetNuke.UI.Skins.Skin.InjectControlPanel() at DotNetNuke.UI.Skins.Skin.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at DotNetNuke.Framework.DefaultPage.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
HTML-Pro and other modules seem to work fine, I have DNN Evoq Content upgraded to 9.6.4, all Mandeeps extensions and libraries are updated, and I was testing on an otherwise blank page with just the Xcillion skin applied, so I'm at a loss.
This is the only remaining roadblock for our installation, so thanks in advance for pointing me in the right direction.
Heather
Joe,
Thanks for the recommendation and apologies for the late reply. Yes, I had previously contacted Mandeeps and they had let me know that since the stack trace does not reference their product then it is most likely not the cause of the error.
I am continuing to troubleshoot the issue. If I can find a way to replicate it outside of a third-party module, I will be able to enter a support ticket with DNN.
Thanks again, and I will let you all know if and when I'm successful :)
Is this a problem only with the Mandeeps module? If so, I would point that out to Mandeeps' support. Maybe ask them to take a look at your site and at least verify the problem.
There was one other vendor's product that initially did the same thing after I upgraded, but when I applied its latest update, the problem went away. I mentioned that in my support ticket.
At this point, the two Mandeeps modules we have licensed are the only way I can replicate this issue, but I do accept what they're saying about it not being caused by their product. The stack trace references the Persona Bar only.
I feel like since nobody else here has run into this issue and it didn't come up in any internet searches that it must be specific to our test environment. There are a few things I'm trying now just to eliminate them from the list (IT needed to apply a few cumulative .NET updates on the server, there is the known issue after upgrading to V9 where changing the default skin in Manage>Themes doesn't change any of the existing pages, and it's possible there is something blocking certain scripts from running.
Crossing fingers it's something simple like that!
These Forums are dedicated to the discussion of DNN Platform.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.