Addon: Easy Forms with Paypal, user attributes, registration

Permalink
I'm using the addon "Easy Forms with Paypal" to build a form.

So far, so good.

I would like some of the fields in the form to be associated with user attributes.

For example, I would like the first name, last name, address and phone to be associated with the user so they don't have to re-enter it every time they purchase something using a form I made with this add on.

Otherwise, should I just build these attributes into the registration form?

If so, I have (a related) question.

I'm making a customized registration form and it looks like the custom attributes are being referenced like:

akID[60][value]


Is there any way to grab these attributes and feed them into my form programmatically? Instead of cutting and pasting akID[60][value] from the original registration form which seems a bit ugly to me.

 
nicolechung replied on at Permalink Reply
Got how to do the attributes from this thread:

http://www.concrete5.org/community/forums/customizing_c5/styling-a-...

Now, is there a way to make the form send data to user attributes instead of general attributes? Or am I totally mixed up about this??
andrewsturm replied on at Permalink Best Answer Reply
You may need to override the paypal form add-on. Probably the controller. Do this at your own risk. This is about peoples money...

Plus + You'll need the UserInfo object then update it:
$ui->update($data)

Where $data is an array that can contain

uName - the username. Required.
uEmail - Email address. Required.
uHasAvatar - 1 if the user has an avatar. 0 if not.
uTimezone - the user's timezone.
uPassword - the non-encrypted password.
nicolechung replied on at Permalink Reply
You know I was thinking more on this, and it makes sense to instead *register* the user with special attributes (first name, last name, address) and then get them to log in.

Once they are logged in, they can purchase items with the paypal form, and then I would just need a way to link their purchases with their "user information".

Now that I know I might have to "hack" the form to associate their user attributes with an actual user account, maybe I will offer that as an option but say "you won't have a user account created which means you have to re-enter all of this information again when you purchase something later" or to that effect.