Single Email address, multiple unique profiles

The problem with this is that it goes against how the signup module works...

I figured out that our needs would require something much more simple so I created a module... all it does is add a new pane to the ubercart checkout where you can fill in some extra information for each attendee.

I'll be done with the code in a day or so... let me know if you want it!

"The problem with this is that it goes against how the signup module works... "

I'm not sure that's the case. There are a couple of ways of working with signup.module to make this kind of a feature work. We can generate accounts for the other users without email addresses, or folks can work on #349228: Signup anonymous users without email. I think the biggest challenge for uc_signup would be smoothly integrating this into the UI while preserving current use cases.

@ezra-g - you're absolutely right... I wasn't really aware of this at the time but this is potentially the best way to go long term.

However, as I'm sure you will understand, I was working to a deadline and this seemed like the easiest way to get the job done given the time frame. The code I wrote is *EDIT* attached in a comment lower down...

I haven't had a chance to read your code, @jackread. Since Drupal's Profile module requires a unique account, and therefore email address, one way to get around this is to generate accounts with emails that are based on the original email, so if I register as bill@example.com then the system asks for the contact information of all 3 of Bill's guests and creates Drupal user accounts with addresses like bill+1@example.com. In keeping with the primary goal of this module, we should make a process like this easy to use (and hide when it is disabled) :).

Changing the issue title for clarity, at least for me. Feel free to suggest a better title ;).

Hi, I've been trying to apply this patch for a few hours, using gnuwin32 at first and now with cygwin. I'm afraid I am getting failure errors, and this is the rej file.
I'd appreciate any advice here.

Hunk #5 failed at 684

***************
*** 653,658 ****
if (empty($account->uid)) {
$form_state['values']['mail'] = $mail;
$namenew = preg_replace('/@.*$/', '', $mail);
// From the email registration module:
if (db_result(db_query("SELECT count(*) FROM {users} WHERE LOWER(name) = LOWER('%s')", $namenew)) > 0) {
// Find the next number available to append to the name
--- 684,690 ----
if (empty($account->uid)) {
$form_state['values']['mail'] = $mail;
$namenew = preg_replace('/@.*$/', '', $mail);
+ $namenew = str_replace('+', '', $namenew);
// From the email registration module:
if (db_result(db_query("SELECT count(*) FROM {users} WHERE LOWER(name) = LOWER('%s')", $namenew)) > 0) {
// Find the next number available to append to the name

thanks @crystaldawn

i've actually started work on something similar to this completely outside of ubercart using a generic payments framework that I'm building.

@pstead,

I'm having the same problem with the patch. Hunk #5 keeps failing at 684.

Did you manage to get it working?

@jackread Thanks for the uc_attendees module. Looks good. However, when I try to purchase more than one place at an event, I am still required to input an email address for each seperate attendee.

UPDATE: Looks like I needed to disable signup for the event. This works independently.

I can confirm that @vkareh's patch works like a dream with uc_signup 6.x-1.0 beta5.

I'm still amazed by the generosity of people on these forums. Thanks @vkareh for all your help.

I've come across a few issues after applying @vkarehs patch.

I have a repeat event for children (soccer coaching courses).
The person who registers will be a parent and will not be attending the event.
I have added profile fields which require completion at user registration - Child Name, age etc.

The parent often wants to signup another child. In the UK at least, children rarely have email addresses, and @vkareh's patch lets the user add a guest without email.

With @vkareh's patch everything works fine the first time.
However, next year when the parent logs in to the site, they will receive the message:
"we already have your details" (i.e. the details of the child you signed up last year)
However, the parent may now be signing up a different child, and their "Child Name" profile field is now wrong.

There is also an issue with the creation of a "Guest 1" account.
Maybe the parent will pay for a different child for the next course.
The "User+1" system-generated user account already exists with another child's details in its profile fields.

Does anyone have any ideas how I can build the following ?

Parent signs-up up to 4 children.
Payment method is paypal or cash/cheque.
Each child's details are submitted (name, age, medical condition etc)
A discount is offered for booking more than one child (rules out signup_pay)

I agree with you Jack - I came across a few other issues with a profile-based signup that uc_signup uses. It's particularly problematic for repeat events, when users are booking places for their guests/family.

For example, uc_signup would store dietary requirements in the user profile, but if those requirements change, you would be relying on the user to amend their site profile for each event. I'm not sure that many would do that. If you are booking for a colleague, you would be even less likely to amend their information. This is particularly crucial issue when you are requesting medical information from each user.

Another major point is the amount of information you need to request from a new user as soon as they create a new account on the site. I don't think people would be ready to submit such personal information until they are further down the line of booking event places. User-name and email address is all you should be requesting on account creation.

I think that extra user info needs to be requested for each and every booking outside of user profile information. Your uc_attendees module is a great start - ideally it would include signup functionality for event admin. Or signup would need a non-profile/email address based approach to attendee management.

For the problem in #20, pstead, maybe you can set a Trigger/Action or Rule that deletes guest accounts after the event is past.

This might not be relevant for this project, but I did work on a website where we used the Subuser module to have Parents create Kid accounts. The Subuser module allows the Parent to essentially administer their own Kids' accounts, so they could sign them up for events as if the Kid themselves were signing up.

subscribing

this is excellent progress... although it might take a bit more to implement, this should be configurable per node+signup not just globally.

Hi guys,
Does anyone know how can I find the same module (uc_attendees) for Ubercart 3.0 in Drupal 7 ?

Any help would be really appreciated :)