DNNCommunity/DNN.Repository

Error adding dashboard module to page

trapias opened this issue · 3 comments

trapias commented

Describe the bug

Hello, I'm getting an error as soon as I add a repository dashboard module to the same page where I just configured a new repository module.
Modules do not show up on page, and in the log I find the error:

InnerMessage:Riferimento a un oggetto non impostato su un'istanza di oggetto. InnerStackTrace: in DotNetNuke.Modules.Repository.Helpers.SetRepositoryFolders(Int32 ModuleId) in DotNetNuke.Modules.Repository.RepositoryDashboard.Page_Load(Object sender, EventArgs e) in System.Web.UI.Control.OnLoad(EventArgs e) in DotNetNuke.Entities.Modules.PortalModuleBase.OnLoad(EventArgs e) in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Control.LoadRecursive() in System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Software Versions

  • DNN: 9.7.2
  • Module: 4.1.0

To Reproduce

Steps to reproduce the behavior:

  1. Add a new repository module to a blank page, configure it
  2. Add a new repository dashboard module to the same page

Expected behavior

Modules show on page.

Additional context

The DNN site is new and has content localization enabled. I get the error both if I localize the page and if I set it to neutral language.

valadas commented

@trapias I do not use this module but just merged many PRs and tackled a few hanging fruits for a new bugfix release. Now for this one, there appears to be many things wrong in that view and it is hard for me without using the module to have a reference of even what that view does differently.

See #69 comments if you ever want to help with that effort...

albertovelo commented

@valadas thanks, I managed to update the module myself just to keep it running until we find another solution.
You can close this issue.

Thanks,
al.

valadas commented

@albertovelo Can you share your fix ?