Hi there,

I've been testing some features of Dynamic Registration. In short I'd like to create a registration proces that allows user A (after registration) to register users B, C and D.

So what have I done so far?

- Created the initial registration page for user A.
This page contains a field for the e-mail address and 2 fields with misc. info I'd like to collect (text fields connected to DNN custom fields). I've setup DR to use the e-mail address as username and generate a password on the fly.
Users are automatically logged in after registration.
They are assigned a security role which allows them to reach the page that should be used to register user B, C and D.

* note: I've setup this page in the Datasprings testsite. Not sure if this site should send out e-mails after registration but if so, I didn't recieve any. Perhaps I overlooked a option in the DR backend.

- So next, I've created a page that's only visible to users that have the right security role. The page only contains a field for the e-mail address. It should allow logged in user A to fill in the e-mail address for (for example) user B, who then gets his login and password e-mailed to him.

Now, when user A uses this page to register user B, he submits the form and gets an error saying "Object reference not set to an instance of an object".

I might have an idea what causes this error but I'm not sure how to solve it:
It looks like the module thinks it's there to have user A update it's profile instead of registrering new users. For example, when user A views the page, the e-mail address for user A is already filled in. Also, the button to submit the form sais "Update profile" instead of "Register".

I'm completely new to DNN/ASP/.NET/MS-based solutions and I'm not sure if the error is related to this situation. If they are not related I hope to find solutions for both seperate problems here

Thanks in advance,
- Martijn

Martijn,

Hi. Yes well the module does work a little differently that what you have setup here. A few things.

1. Each instance of Dynamic Registration MUST have a few fields associated with it before it will work, these are identified under DNN Core Integration and are username, password, and confirm password. If you have auto create UserID turned on these fields will be turned off initially, and if you also check the boxes under DNN Core Integration, Advanced Integration Options, you can hide these as 'Hide username for registration updates' and 'hide password for registration updates'. Either way, these fields MUST be linked and reference for the module to work properly.

2. The registration page is assuming if the user is signed in that they want to update their subscription, and doesn't know that this is a new user registration because the user is signed in. In order for the module to be in 'Add mode' the user must have rights to add users as a signed in user and they must access the URL properly. For this to be setup properly:

a. Under Module Configuration, Security, specify the security that the user has access to Manage Users. This will give that user security rights to both add and manage users (unfortunatly there is no security distinction right now between manage/update so this might be a problem for you).

b. Under 'Manage Users' within the menu you will notice a 'Plus Sign'. IF you click this link you will be taken to the page as if a user is going to be added. This is the URL the user would need to be redirected to in order to add a new user to the module even if they are not signed in as a new user.


Hope this clears up some questions you have, my first guess would be that you do not have any fields linked to username, password, and confirm password and these fields are required for the registration module to function properly.

-Chad