Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesHelp! Suddenly I can't access site settingsHelp! Suddenly I can't access site settings
Previous
 
Next
New Post
4/6/2015 2:17 AM
 

I've been working on a new module locally (DNN 07.04.00) for some time. The module is working fine.

Today I tried to browse to my Site Settings in the Admin menu (as I need to set up some custom user profile properties) and I get the following error. I have another dnn site on my dev machine that does not have this issue. How can I work out what the problem is? I haven't edited sitesettings.ascx or anything else in this part of the site. What could have caused this? The only thin g I did remotely in this region recently was I started using some of the DNN wrapped Telerik controls in my module, and to support that I copied some dll files around my DesktopModules bin folders (but not anywhere near Admin). I can't think of anything else that might be interfering.

Error: Site Settings is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: c:\LocalWebsites\dnn\DesktopModules\Admin\Portals\SiteSettings.ascx.cs(934): error CS1061: 'DotNetNuke.Web.UI.WebControls.DnnPageDropDownList' does not contain a definition for 'Roles' and no extension method 'Roles' accepting a first argument of type 'DotNetNuke.Web.UI.WebControls.DnnPageDropDownList' could be found (are you missing a using directive or an assembly reference?) ---> System.Web.HttpCompileException: c:\LocalWebsites\dnn\DesktopModules\Admin\Portals\SiteSettings.ascx.cs(934): error CS1061: 'DotNetNuke.Web.UI.WebControls.DnnPageDropDownList' does not contain a definition for 'Roles' and no extension method 'Roles' accepting a first argument of type 'DotNetNuke.Web.UI.WebControls.DnnPageDropDownList' could be found (are you missing a using directive or an assembly reference?) at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean ensureIsUpToDate) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleControlFactory.LoadModuleControl(TemplateControl containerControl, ModuleInfo moduleConfiguration) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

 
New Post
4/6/2015 2:30 AM
 
I've hacked a temporary workaround to this.

In SiteSettings.ascx.cs I've commented out these recently added lines of code (the last five lines of this method.) Any idea why they would be causing me grief?

private void InitializeDropDownLists()
{
var undefinedItem = new ListItem(SharedConstants.Unspecified, String.Empty);
cboSplashTabId.UndefinedItem = undefinedItem;
cboHomeTabId.UndefinedItem = undefinedItem;
cboRegisterTabId.UndefinedItem = undefinedItem;
cboUserTabId.UndefinedItem = undefinedItem;
RedirectAfterLogin.UndefinedItem = undefinedItem;
RedirectAfterRegistration.UndefinedItem = undefinedItem;
RedirectAfterLogout.UndefinedItem = undefinedItem;

//RedirectAfterRegistration.Roles.Add(PortalSettings.RegisteredRoleId);
//RedirectAfterRegistration.Roles.Add(int.Parse(Globals.glbRoleAllUsers));

//RedirectAfterLogin.Roles.Add(PortalSettings.RegisteredRoleId);
//RedirectAfterLogin.Roles.Add(int.Parse(Globals.glbRoleAllUsers));

//RedirectAfterLogout.Roles.Add(int.Parse(Globals.glbRoleAllUsers));
}
 
New Post
4/6/2015 3:14 AM
 
Compare the working site against the non-working?

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
4/6/2015 4:42 AM
 

Well, that's more or less what I did. I had a previous version of the whole site prior to the last DNN platform upgrade, and looking at the differences there led me to make the code change I mentioned above.

This is a code change directly in the DNN Admin sitesettings module. I never went near this previously. It has only changed as the result of an upgrade, so I can only assume that there is no bug in this code. I've basically just commented out the prepopulation of some combo boxes that I wasn't editing anyway.

Something else in my configuration must be causing this in the first place. It smells like I have the wrong version of a DLL somewhere, but no idea which DLL or where it is wrong.

Something to do with the new Roles property on the DnnDropDownList class, I'd bet.

 

 
Previous
 
Next
HomeHomeDevelopment and...Development and...Building ExtensionsBuilding ExtensionsModulesModulesHelp! Suddenly I can't access site settingsHelp! Suddenly I can't access site settings


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out