DNNCommunity / DNN.Blog

The official blog module for the DNN Platform
Other
38 stars 41 forks source link

Error Blog in DNN 9.1.1 #126

Open idasbv opened 6 years ago

idasbv commented 6 years ago

I get this error when trying to open the detail view of a blog post: InnerMessage:Object reference not set to an instance of an object.

InnerStackTrace:

at DotNetNuke.Modules.Blog.Common.ViewSettings..ctor(Int32 tabModuleId, Boolean justLoadSettings) at DotNetNuke.Modules.Blog.Common.ViewSettings.GetViewSettings(Int32 tabModuleId) at DotNetNuke.Modules.Blog.Common.BlogModuleBase.get_ViewSettings() at DotNetNuke.Modules.Blog.Common.BlogContextInfo..ctor(HttpContext context, BlogModuleBase blogModule) at DotNetNuke.Modules.Blog.Common.BlogContextInfo.GetBlogContext(HttpContext& context, BlogModuleBase blogModule) at DotNetNuke.Modules.Blog.Common.BlogModuleBase.get_BlogContext() at DotNetNuke.Modules.Blog.Controls.ManagementPanel.Page_Load(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at DotNetNuke.Entities.Modules.PortalModuleBase.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Is the latest version of the blog module compatible with DNN9.1.1 ?

idasbv commented 6 years ago

Looks like it depends on the template you use...

idasbv commented 6 years ago

Most templates give an error in DNN 911... tested in several DNN911 instances

valadas commented 5 years ago

I cannot reproduce this using the provided templates. Can you drop a template that makes this issue occur so we can investigate further.