I'm creating an app where people are requried to sign up. When they sign up, they get a user specific page setup which is publicly viewable (kinda like a profile page I guess). Would i be better of storing the info that is displayed on that page in the users profile? or as properties on the page?
If you are creating the users as members in Umbraco, I would prefer to store the data on the member. This makes the best sense on my world. Then all details of a given member is stored ON the member, and not on some kind of member-page in the config-tree.
I'd be tempted to store it in the profile I guess (that way it's tied to the user). If you do it that way, you wouldn't necessarily have to create a physical page for each user, you could just use a URL rewriting rule to pass the username (or whatever) to a template with a macro that pulls out the details from the profile and displays it.
As the two above answers imply you should probably store the information on the member. You don't need to make any URL rewriting to serve up the user details. You just need one page and a template in, which you retrieve the information from the current member by either a XSLT macro or using the member API.
Cheers guys. I was only contemplating the other route as the users (and therfore their pages) wlil be searchable and I thought it could help simplify the search machanism.
I'll stick to keeping it in the profile though I think, as the searching should only be based around the name, so shouldn't be much of a problem.
Best place to store information?
Hi Guys,
I'm creating an app where people are requried to sign up. When they sign up, they get a user specific page setup which is publicly viewable (kinda like a profile page I guess). Would i be better of storing the info that is displayed on that page in the users profile? or as properties on the page?
Many thanks
Matt
If you are creating the users as members in Umbraco, I would prefer to store the data on the member. This makes the best sense on my world. Then all details of a given member is stored ON the member, and not on some kind of member-page in the config-tree.
/Kim A
I'd be tempted to store it in the profile I guess (that way it's tied to the user). If you do it that way, you wouldn't necessarily have to create a physical page for each user, you could just use a URL rewriting rule to pass the username (or whatever) to a template with a macro that pulls out the details from the profile and displays it.
Hi Matt
As the two above answers imply you should probably store the information on the member. You don't need to make any URL rewriting to serve up the user details. You just need one page and a template in, which you retrieve the information from the current member by either a XSLT macro or using the member API.
/Jan
Cool,
Cheers guys. I was only contemplating the other route as the users (and therfore their pages) wlil be searchable and I thought it could help simplify the search machanism.
I'll stick to keeping it in the profile though I think, as the searching should only be based around the name, so shouldn't be much of a problem.
Matt
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.