Two problems with current members only (not new registration)

1.  At login, it's making previously registered users fill in information that we already have in the system.   

2. We use the login module on the left side of our homepage, and when someone logs in, it doesn't direct them to a separate page, instead it tries to fit the the profile page into same page as the module and squeezes everything off the page.    The first problem really affects the 2nd problem, but the 2nd problem shouldn't happen either.

Please help ASAP, as this is already slowing down business quite a bit.

There are some behavior differences, that were introduced in 3.3/4.3 that will affect how users use the Login Module.

One requirement in the new profile features was the ability to force users to update their profile (if the administrator adds a new required profile property).  The only way to enforce this is to embed the profile control in the login control.  This gives rise to the behavior you are seeing (as the Login control now contains an embedded Profile control which gets displayed in these circumstances). 

Sebastian's solution is correct.  If you wish to have the same behavior as you used to have you have two choices.

1. Do not add any new required profile properties, as this will trigger an automatic "update profile" during login
2. If you would like to take advantage of the new required profile property features then either switch to the default login process or change your page layout to accomodate the wider profile control.

I will add an enhancement request to allow (through a User Setting) the administrator to disable the "update profile" behavior.  This would mean that the user is not forced to update their profile on login, but they would be required to enter valid information if they do update their profile.

---

Charles Nurse Chief Architect Evoq Content Team Lead, DNN Corp. Want to contribute to the Platform project? - See here

MVP (ASP.NET) and ASPInsiders Member