Need ideas for handling multiple logins that handles multiple people
Hi
I have a project where I need to handle kids that are not old enough to have a login themselfes, but where the parents have a login. If the parents are divorced its even more complicated. I'll try to explain further:
I have a family that have 3 children and 2 parents. The parents are divorced. I need each of the parents to have their own login, and when logged in, they can signup all three kids to an event, on the kids' behalf. That means that I have 2 logins that points to 3 children, meaning that each child that two 'administrative' logins connected to them each. However, when the children grows older, they will handle their login them selfes.
I really need some input on how to handle this in Umbraco. One thought was to create a membertype named 'logintype' which would be the parents. I then create another membertype names 'player' which would be the children. On the 'logintype' I would have a number of memberpickers, to select the children that belongs to that login. That would however limit the flexibility because I would have to set a specific number of 'children' pickers, fx. 5. And when the children gets older, they would have their own 'logintype' that points to their own 'player' - kind of redundant?
Anyone got any ideas to make this easy/practical to handle using members in Umbraco?
That sure sounds like a challenge! If I were to make such a site, I would combine the members section with the Umbraco relationship API. I think you'll want to create a MemberType for each of the member.. types :-)
- Parent - Divorced Parent - Child
Then create the Members with no knowledge of each other at first and then relate them to each other the way you want. I.e if you have a child with two divorced parents you'll want to create a member for each of these and then relate the two parents to the child (or the other way, or simply make it a bi-directional relation)
There's a video on umbraco.tv - developer section that explains all about using the Relationship API :-)
You might aswell contemplate the redundance of the Divorced Parent member type in my above example since a parent is... well, a parent :-) - divorced or not. However, it would maybe give a bit more overview with the membertype. I think it's a matter of taste really.
What I did was to make a custom .NET Usercontrol for adding members (and relations) and place this on the dashboard of Umbraco. I'm not sure if this is the best way to handle it, but at least it works ;-) Maybe you could look into somekind of event based stuff like: AfterMemberCreated or some such - I don't know if there's such an event in Umbraco - merely just a guess :-P
Need ideas for handling multiple logins that handles multiple people
Hi
I have a project where I need to handle kids that are not old enough to have a login themselfes, but where the parents have a login. If the parents are divorced its even more complicated. I'll try to explain further:
I have a family that have 3 children and 2 parents. The parents are divorced.
I need each of the parents to have their own login, and when logged in, they can signup all three kids to an event, on the kids' behalf.
That means that I have 2 logins that points to 3 children, meaning that each child that two 'administrative' logins connected to them each.
However, when the children grows older, they will handle their login them selfes.
I really need some input on how to handle this in Umbraco. One thought was to create a membertype named 'logintype' which would be the parents. I then create another membertype names 'player' which would be the children.
On the 'logintype' I would have a number of memberpickers, to select the children that belongs to that login. That would however limit the flexibility because I would have to set a specific number of 'children' pickers, fx. 5.
And when the children gets older, they would have their own 'logintype' that points to their own 'player' - kind of redundant?
Anyone got any ideas to make this easy/practical to handle using members in Umbraco?
Regards
Bo Kingo
Hi Bo,
That sure sounds like a challenge! If I were to make such a site, I would combine the members section with the Umbraco relationship API. I think you'll want to create a MemberType for each of the member.. types :-)
- Parent
- Divorced Parent
- Child
Then create the Members with no knowledge of each other at first and then relate them to each other the way you want. I.e if you have a child with two divorced parents you'll want to create a member for each of these and then relate the two parents to the child (or the other way, or simply make it a bi-directional relation)
There's a video on umbraco.tv - developer section that explains all about using the Relationship API :-)
Hope this makes sense!
All the best,
Bo
You might aswell contemplate the redundance of the Divorced Parent member type in my above example since a parent is... well, a parent :-) - divorced or not. However, it would maybe give a bit more overview with the membertype. I think it's a matter of taste really.
Hi Bo
Thanks for the input. I think that is the way. I can even add sibling relations :)
Now I just need a way of adding the relations from the backend, when the members are created
/Bo Kingo
Hi Bo,
Happy to help :-)
What I did was to make a custom .NET Usercontrol for adding members (and relations) and place this on the dashboard of Umbraco. I'm not sure if this is the best way to handle it, but at least it works ;-) Maybe you could look into somekind of event based stuff like: AfterMemberCreated or some such - I don't know if there's such an event in Umbraco - merely just a guess :-P
All the best,
Bo
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.