Extending the user data that get stored within ez.

Next topic

Author	Message
Stuart Fenton	Thursday 03 April 2003 4:36:18 am I am trying to extend the user data that get stored within ez. Specifically I want to define data for address, payment info, etc but don't want to alter the standard user definition. I have created a new set of classes to store this information and need to relate it to the user. Do I relate this data to the user class similar to reviews related to products or do I get this data entered after the user has logged in and therefore have their details (current user) to do the relation automatically. If I use the second method how do I access this data when the user logs in as the data needs to be specific to the user and not all users details. Do I search for the records or use the role system to only allow access to data they have entered. -- Stuart [email protected] http://www.grandmore.com
Jan Borsodi	Friday 11 April 2003 7:20:22 am Users are normal objects like articles, the only difference is that they have the user datatype as an attribute. For instance you can extend the default user in eZ publish and add new attributes. What do you mean by accessign the user specific data? Do you mean the data create when registering? -- Amos Documentation: http://ez.no/ez_publish/documentation FAQ: http://ez.no/ez_publish/documentation/faq
Paul Borgermans	Friday 11 April 2003 10:56:19 am >Users are normal objects like articles, the only difference is that >they have the user datatype as an attribute. >For instance you can extend the default user in eZ publish and >add new attributes. Wouldn't this create problems for future upgrades? As long as the attributes do not change in the ezp 3 base, it will probably work. Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans

Author

Message

Thursday 03 April 2003 4:36:18 am

I am trying to extend the user data that get stored within ez. Specifically I want to define data for address, payment info, etc but don't want to alter the standard user definition.

I have created a new set of classes to store this information and need to relate it to the user. Do I relate this data to the user class similar to reviews related to products or do I get this data entered after the user has logged in and therefore have their details (current user) to do the relation automatically.

If I use the second method how do I access this data when the user logs in as the data needs to be specific to the user and not all users details. Do I search for the records or use the role system to only allow access to data they have entered.

-- Stuart

[email protected]
http://www.grandmore.com

Jan Borsodi

Friday 11 April 2003 7:20:22 am

Users are normal objects like articles, the only difference is that they have the user datatype as an attribute.
For instance you can extend the default user in eZ publish and add new attributes.

What do you mean by accessign the user specific data? Do you mean the data create when registering?

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Paul Borgermans

Friday 11 April 2003 10:56:19 am

>Users are normal objects like articles, the only difference is that >they have the user datatype as an attribute.
>For instance you can extend the default user in eZ publish and >add new attributes.

Wouldn't this create problems for future upgrades? As long as the attributes do not change in the ezp 3 base, it will probably work.

Paul

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans