Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Porblem After upgrading to 5.2Porblem After upgrading to 5.2
Previous
 
Next
New Post
11/30/2009 2:19 PM
 

I have updated my website to 5.2 but now i have a lot of problems ... when i try to create new module it give me this error:

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\inetpub\vhosts\youpes.net\httpdocs\DesktopModules\Admin\Extensions\Editors\EditModuleDefinition.ascx.vb(582): error BC30456: 'Controls' is not a member of 'Skins'. ---> System.Web.HttpCompileException: C:\inetpub\vhosts\youpes.net\httpdocs\DesktopModules\Admin\Extensions\Editors\EditModuleDefinition.ascx.vb(582): error BC30456: 'Controls' is not a member of 'Skins'. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResult(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.ControlUtilities.LoadControl[T](TemplateControl containerControl, String ControlSrc) at DotNetNuke.UI.Modules.ModuleHost.LoadModuleControl() --- End of inner exception stack trace ---

and when i try to open a pop up from customodules or when i try to upload new module or when i try to change skin it give me this error :

Collection is read-only.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NotSupportedException: Collection is read-only.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[NotSupportedException: Collection is read-only.]
   System.Collections.Specialized.NameValueCollection.Set(String name, String value) +5259386
   System.Web.HttpHeaderCollection.SynchronizeHeader(String name, String value) +32
   System.Web.HttpRequest.SynchronizeHeader(String name, String value) +44
   System.Web.Hosting.IIS7WorkerRequest.GetHeaderChanges(HttpContext ctx, Boolean forRequest) +611
   System.Web.Hosting.IIS7WorkerRequest.SynchronizeVariables(HttpContext context) +52
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +477

pls help me my website is totally crashed :( :(

 

 

 
New Post
11/30/2009 4:56 PM
 

This happen's when there is a namespace issue, what i had to do to fix is was change

Line 497 to

DotNetNuke.UI.Skins.Skin.AddPageMessage(ctlSkin, heading, message, DotNetNuke.UI.Skins.Controls.ModuleMessage.ModuleMessageType.YellowWarning)

Line  515 to

UI.Skins.Skin.AddPageMessage(ctlSkin, messageTitle.ToString, messageText.ToString, DotNetNuke.UI.Skins.Controls.ModuleMessage.ModuleMessageType.RedError)

After this all was good.

 
New Post
11/30/2009 7:28 PM
 

I have already edited these lines and i have solved the first problem ... but i still have Collection is Read only problem !!!!!!!

 
New Post
2/11/2010 5:00 AM
 

Hello, do I have the same problem, do I have modified the file default.aspx.vb like do it appear in the post but don't it operate me, that does it be making wrong? Once modified one must rebuild?

Thank you and sorry for my stupidity

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Porblem After upgrading to 5.2Porblem After upgrading to 5.2


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.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out