Posted By Chad on 07/31/2008 1:10 PM
1.) - We recently discovered an issue with Country field types and server side validation. I believe the issue was with Country and CAPTCHA actually. If the form field is hidden (no longer visible) and server validation is turned on, you will receive a an 'object not set to instance of object'. Can you tell me if this form might have a similar issue? Also, if you turned server side validation off temporarily do you still receive this issue. I do believe we are working on a fix, so maybe this is what is causing your problem.
Ended up that this issue had to do with my ignorance of the DR module. In that particular instance of the module where I had the problem, I did not create the three required fields to link to the Core DNN profile (username, password, confirm password). So, in essence, the module didn't have a profile to save the information to. Problem solved.
Posted By Chad on 07/31/2008 1:10 PM
2.) –Yes, I wish DNN provided for a way to handle this, where it would redirect the user the ‘User page’ if their profile was not valid. Unfortunley it does not, however, you should still be able to do this using the core. If you use the standard Login module, and you also go to Admin, User Accounts, Manage User Settings, you should be able to turn on ‘force valid profile for login’. Then, under the DNN Profile Field (the one you have mapped to the dynamic field for this) make that field checked as required. What should happen is when users sign in, they will be prompted for just that field. It will show them the CORE look and feel, but for existing users I don’t know a good way around this and would at least force them to answer that property.
The ‘other’ method, would be to use our Dynamic Login module, and allow the ability to ‘Redirect based on security role’. So after login, you could redirect users to ‘Page A’ if they were in ‘Security Role A’ and other users to ‘Role B’. etc…
I hope this helps!
-Chad
I wish this wasn't the case, but I couldn't find any other way to do it. I ended up purchasing Dynamic Login so I could redirect users in a certain user role to the page with the instance of the DR module for accepting the user agreement.
We did run into an issue with the user roles though. Originally, I had it set up that a user was assigned to a user role when they accepted the user agreement with a completion event. I then used another completion event that ran a stored SQL procedure from another thread here that checked for a user role and deleted it.
The problem arose because our site was on a shared hosting server and this kind of database load (hundreds of users from a database of 14,000+ in a few minutes) brought the site down. So, as a workaround, I'm not going to delete the user from the "Invalid Account" role. When they get added to the "Valid Account" role, their next login redirects them to the Home Page instead of the Accept User Agreement page.
This is where the Dynamic Login module works very nicely. Being able to explicitly state the priority of the Login Role Rules was essential to get this to work.
I wish we still had the ability to have users get redirected back to the previsou page if they are in a certain user role, but this will work for now.
Thanks for all your help and quick response via email, Chad!
-Xavier
|