A consequence of using this 'shop user' seems to suggest that there can only be one class of user used per site as the site.ini only has space for the class and group new users should be part of. However, i may be wrong here but i don't know if you can add others...
Is it indeed not sensible to have, say two classes of users on a site, eg one user for shops and one user for forums? If you were a forum user and wanted to buy something then perhaps a single user may be best but maybe the users should be different and information simply shared between them.... but im really not sure at the moment...
On ez.no we have created a shop account handler ( as we call it ) which enables you to shop without beeing logged in. If you're logged in it will fetch the user information from your account. We've also done a check if you've previously purchased somehting and prefill the values of your account.
This enables people to shop without beeing a registered user. The information like address/company is stored in the order ( serialized xml ). You do not need to create a special user class, but it's possible to solve it that way as well.
I hope this answered your question, a bit late though ;)
How could I accomplish something like what yuo have done here on ez.no? What kind of modifications I have to do? Template coding, hard coding/modifications?
P.S. It would be great if you could share somewhere these kind of solutions for others in community to use also. That way all of us could become more and more efficient with eZ and start building more and more complex systems with eZ.
Thanks, Jerry
You must be logged in to post messages in this topic!