TOPIC: Registering Multiple Individual Registrations

I'm running into an problem with registrations for an event.

Running 2.6.9a
I know this isn't the latest version, but I have run a bunch of events and done a lot of customization. For a while, I was running every a,b,c release of 2.7 all the way to i, but they all broke my existing events and messed up my custom forms.

Here's the problem I'm having:
In the past we used the both setting to allow group and individual registrations. That ended up creating a nightmare for trying to process check-ins at the event.

It was much easier to follow if we only allowed individual registrations.

So now this is happening to some people:
An person needs to register 2 people.
They submit the form the 1st time and all goes well.
2nd time they do it, they end up not creating a new form, but instead they have just UPDATED the 1st registration they made.

How can I prevent this?

I don't believe it's possible in DTRegister (any version) for 1 username to register two times as two different people when doing so via the "Individual" registration.

I believe the hook is the username (or email address) for event registration.

So if [email protected] (with username 'joe') registers for an event and tries to register his buddy for the same event, it won't work because DTRegister pulls the username (and/or email address for username 'joe') from the environment variables.

From my experience (having only ever used Individual Registration), 'joe' would need to log out and log in as his buddy (which would mean creating a username for him if the buddy doesn't already have one) then register for the event.


-soccerbum

Guys... few comments on this...

1) Once you complete a registration, that session is ended so clicking back to the list of events and starting over will NOT modify the previous record. After submitting the registration, I'm wondering if you someone is clicking the back button in the browser and the resubmitting. That would be a bad idea and if you think people would actually do that, you need to post some instructions saying NOT to do that. The user must click a link that takes them back to the list of events to start a fresh registration process.

2) When logged in, the user CAN modify any auto-populated profile data and register someone else as long as you have disabled the "View Only Profile Data" setting.

3) wbaccus - sorry you had 2.7 issues. We're about to release 2.7.2d which is MUCH better than the last version you probably tried. As you mentioned "all the way to i" means you were in the 2.7.0 series. Tons of stuff has been fixed and improved on and the new package we are about to release (tonight or tomorrow) is the way to go. Thanks.

I look forward to trying the new version. The cart will be a great benefit for what I'm doing.

Here's the thing: None of these folks are logged in. These are public registrations.

I thought that they might be hitting the back button as well, but they're not.

I actually tried it and it did the same thing to me. I get a blank form on the 2nd attempt, but when I fill it out, it references the same confirmation number, though it doesn't update the registration record.

FYI, I tried the new d release today, and after trying to set it up on my localhost, it just won't work. Events lose their titles, and you can't add them back. The only way around it seems to be to make a copy of an event and then set it up again.

wbaccus - sounds like you probably didn't go through the 2.6 -> 2.7 migration completely. Follow ALL of the instructions in the readme file. Right after installation, you will likely appear to have missing data. Running the 2.6 migration tool should get everything in order.... unless you've already run the JEvents Unsync tool.

If you're events are stilled synced with JEvents, try this... install our new JEvent Update plugin that came with the 2.7.2d package. Install and enable. Then open an event in JEvents and re-save. See if it updates the event in DT Register... it should update title, date and time. If the update doesn't happen, then you've lost the sync.