Hi,
I'm using V04.03.05 and building a site with multiple child portals.
I found when a user registers at the main portal (portalId 0) and later at a child portal everything seems to work just fine.
When I delete the user later from the child portal (I use the UserController.DeleteUser() function), the user is deleted from the DNN tables (for this child portal) and remains as a DNN user for portal 0. This is what I want.
But... the user is also deleted from the ASP Membership and ASP User tables and won't be able to login on the main portal.
There was only one record for this user in the ASP tables to begin with even if the user registered on multiple child portals and this record seems to be deleted with the DeleteUser call.
Is this normal behaviour or am I missing something?
Thanks in advance!!
Dirk

I noticed there is a stored procedure with this name and as a workaround I use the same procedure to just delete the user record from the UserPortals table. This seems to work! (user can still login to the main portal but no longer to the child)
I think it should be addressed in the core also because the same happens when you delete a user from a child portal with the user mananger (as site admin user).

I'm wondering if I can just add an exsting user (registered on portal 0) to a child portal by adding a record to the UserPortals table instead of using the UserController.CreateUser function? It seems there is only one DNN and ASP User anyway. (different from V3 where each child portal had its own user, password, etc.)

Thanks!