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

HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...dnn 7: can't change to edit mode and can't move modules to a new panednn 7: can't change to edit mode and can't move modules to a new pane
Previous
 
Next
New Post
6/12/2013 3:08 PM
 
I had the same issue and found this thread while problem solving. Reporting back, I fixed mine just now by re-setting the files and folder permissions to the wwwroot folder in the hard drive to give Network Service full permission including sub folders. It is supposed to be that way already, but re-doing those permissions did solve the problem. Try it. Mark Buelsing
 
New Post
8/26/2013 3:45 PM
 

And no official DNN ansver ??? Is this support forum or chitchat club??

 

A lot of users have this problem, so we expect at least explanation.

 

Thank you!

 
New Post
8/27/2013 2:04 AM
 
please notice that these forums are part of DNN community. DNN Corp employees may answer in their spare time, but official support is provided for Evoq customers only.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
3/26/2014 7:57 AM
 
after upgrading an install from 568 to 722 I had again that pesky windows security login dialog and forgot what I did last time.
For me the solution was:
make sure in your web.config:
1. < system . webServer>
< modules runAllManagedModulesForAllRequests="true" >
and:
2. < remove name ="FormsAuthentication" / >
< add name="FormsAuthentication" type="System.Web.Security.FormsAuthenticationModule" preCondition="" / >
(beware of the spaces in the above!)
And after that: log off, leave the website, close your browser, open your browser again, clear all your cookies in your browser, browse to site, login and try again. It worked for me...

Peter Schotman
Cestus Websites voor DotNetNuke oplossingen in Nederland
Contact us for your custom design and skinning work.
 
New Post
9/17/2014 3:04 AM
 
Ran into this issue tonight and thought I should share my diagnosis in case it helps others...

When the Control Panel has issues in DNN7 and wont allow you to go into Edit mode, add modules, or select various other options it is usually because there are problems with the AJAX service requests that the Control Panel needs to make to perform those actions. If you hit f12 in your browser you may even see a bunch of Javascript errors that are being generated by the page when it attempts to make the service calls. This would lead you to believe it is a client-side problem, so you may try doing a browser refresh or incrementing the Version in Client Resource Management. But if you login to another browser you will notice that the problem still exists... so it is clearly a server-side issue.

In my particular case it was caused by a custom HTTP Module. Since HTTP Modules run on every request, there need to be written very carefully so that they only affect certain types of requests. If they are not careful, they can affect the behavior of AJAX service requests. In my case the HTTP Module was throwing errors for service requests because many of these requests do not have DNN Context ( ie. PortalSettings ). And in many cases the unhandled errors in HTTP Modules will simply be swallowed by the system and never written to the Event Log. This leads to phantom problems which are very difficult to diagnose.

In my case I had to remove the registration for the HTTP Module from my web.config and immediately my Control Panel began to work perfectly again. Then I was able to review the code of my custom HTTP Module, identify the problem, and ensure it only processed requests for "default.aspx" that had valid DNN Context.

The common solution I have seen is to set unAllManagedModulesForAllRequests="true" - and although this can resolve the problem in some cases, it is a bit like ingesting all of the medicine in your medicine cabinet to fight a common cold. It is generally better practice to identify the specific problem and resolve it so that the rest of the system is not affected.

My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Upgrading DNN P...Upgrading DNN P...dnn 7: can't change to edit mode and can't move modules to a new panednn 7: can't change to edit mode and can't move modules to a new pane


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