When using dynamic registration and having the choice to opt-in to my newsletter, the user gets added to the opt-in list/users view even if they choose not to opt-in (via the dynamic reg checkbox). They are added and are correctly not associated with the list. That part makes sense but why are they added to this view at all? My list is going to get hard to manage if every user to my portal is added to it regardless of if they opt-in or not.
And...when I delete the user from dnn users account, the user remains in the opt-in list/users view.
How is this suppose to work as some of this seems counterintuitive? I would expect a user to be removed from this list when their main dnn user account has been deleted. Maybe there are cases where this would not be the desired result but I would think those are unique. Also, I'm not sure why the user would show up in the opt-in list/users view when they did not subscribe to the list in the first place.
Thanks,
Paul
Still looking for some info here.
Thanks Chad...I will look into geting the sql event setup to remove the user when the user core account is deleted. I know you know from an admin standpoint any module that pulls data from the main core user accounts needs to be tightly integrated with the core module and to have multiple config options. If not, the admin is going to have more admin work to do trying to make sense out of user lists that might have different users than the core list.
The last part makes sense and I can see why it is integrated this way as it is a nice end user feature that the optin/out module is pre-populated with their info.
Thanks for clarifying things. I appreciate it.