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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom Login control broke after an upgrade to 4.7.0Custom Login control broke after an upgrade to 4.7.0
Previous
 
Next
New Post
11/18/2007 8:38 AM
 

I did an upgrade from 4.5.5 to 4.7.0 . The site is up, but I cannot log in since my custom login control is not loaded. Below is what I got where the login control is

"Module Load Warning
One or more of the modules on this page did not load. This may be temporary. Please refresh the page (click F5 in most browsers). If the problem persists, please let the Site Administrator know." 

Is there anything that I can do to log in using the login control coming with version 4.7 just  so I can see what's wrong with the custom login?

Would you advise what is different between 4.5.5 and 4.7 login structure?

Any insight or thoughts would be greatly appreciated.

 
New Post
11/18/2007 8:53 AM
 

it depends, how you integrated your login control, try to login using /ctl/login/default.aspx

The login process has changed significantly in DNN 4.6.0 due to the introduction of authentication providers, which makes it easier to create custom single-sign-in solutions.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/18/2007 5:34 PM
 

Sebastian, thank you for your quick response.

Also, would you please tell me what class in 4.7.0 replaces the DotNetNuke.Security.Authentication.AuthenticationController?

 

 
New Post
11/26/2007 6:21 PM
 

Sebastian,

can you please elaborate a bit. In my case I think the issue is that I selected a specific portal page for "Login" page. But Module Load Warning comes up all the time whenever a page is loaded... It is very annoying, as upgrade from 4.6.2 to 4.7 went smoothly. Maybe I'll just stick to not upgrading...! Anyway, another lesson learned...

 

 
New Post
11/27/2007 8:23 PM
 

I have to confess that as in many cases the problem was somewhere else... The directory on the server had not had ASP.NET 2.0 enabled, so that is what it was - once I enabled it the portals work fine. However, I'm still puzzled that the upgrade worked without a problem.

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom Login control broke after an upgrade to 4.7.0Custom Login control broke after an upgrade to 4.7.0


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