I'm developing an app where users register, and they get a personal page created. My question is, given that this page will only ever belong to 1 person, would it be best to use the Relation API or just have a Member Picker property on the page itself?
The relation api works 2 ways so you can from member get the page and from page get the associated member. With using member picker you can from the page get the member but to get from member to page you would have to trawl through whole site till you found the member value set in a page. I only found that out the other day from Niels when i asked difference between relating nodes through api using relations and relating nodes through pickers.
One other thing out of box you do not have a relations manager in the backend so you would have to write your own if in future you wanted to break a relation.
Thanks Ismail, I was thinking for the link back to the page, it could just be a property on the users profile? Granted you will have to manage it from 2 ends, but it least it's managable via the back end. The lack of a manger is the main reason I'm wondering if there is any huge benefit when it is a fixed 1 to 1 mapping.
Relation vs Member Picker Property
Hi Guys,
I'm developing an app where users register, and they get a personal page created. My question is, given that this page will only ever belong to 1 person, would it be best to use the Relation API or just have a Member Picker property on the page itself?
Many thanks
Matt
Matt,
The relation api works 2 ways so you can from member get the page and from page get the associated member. With using member picker you can from the page get the member but to get from member to page you would have to trawl through whole site till you found the member value set in a page. I only found that out the other day from Niels when i asked difference between relating nodes through api using relations and relating nodes through pickers.
One other thing out of box you do not have a relations manager in the backend so you would have to write your own if in future you wanted to break a relation.
Regards
Ismail
Thanks Ismail, I was thinking for the link back to the page, it could just be a property on the users profile? Granted you will have to manage it from 2 ends, but it least it's managable via the back end. The lack of a manger is the main reason I'm wondering if there is any huge benefit when it is a fixed 1 to 1 mapping.
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.