Developing a new module errors were given.
Two different sets of symptoms, for different versions of DotNetNuke.
To correct both of these errors ensure that no key for the module is set to ‘Settings‘. I like to also avoid module files being called Settings too.
DotNetNuke 3.1.1
In this version of DotNetNuke I found that the module ignored the settings which had been defined, via the database.
When clicking on the option to edit the settings for the module a blank page was presented.
DotNetNuke 3.2.2
The module settings were available when rendering the page.
However, selecting the module settings options gave the following error message.
Unhandled error loading module. DotNetNuke.Services.Exceptions.ModuleLoadException: Unhandled Error Adding Module to ContentPane ---> System.InvalidCastException: Specified cast is not valid. at DotNetNuke.Modules.Admin.Modules.ModuleSettingsPage.Page_Init(Object sender, EventArgs e) in C:\Inetpub\wwwroot \admin\Modules\ModuleSettings.ascx.vb:line 566 at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.UserControl.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Control.AddedControl(Control control, Int32 index) at System.Web.UI.ControlCollection.Add(Control child) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) in C:\Inetpub\wwwroot\admin\Skins\Skin.vb:line 559 --- End of inner exception stack trace ---
