CiviCRM Community Forums (archive)

G'day all,
I currently have civicrm 3.1.5 running with joomla 1.5. im using this setup for a springboard diving club website to take memberships and class registrations.

right now i have it all set up so that:
1. diver get membership and then gets a joomla login at the same time.
2. the diver logs in and can see classes that they can register for.
3. that diver must logout first before their brother or sister (or parent for adult diving!) can do their class registration.

basically each diver has their own joomla login and civicrm contact. each membership and class registrations links to the civicrm contact as normal.

everything works pretty good except for when the brother or sister comes along. surely there is a better way to handle the contacts and the memberships and the class registrations. our class registrations are quite complex where there are different squads training at different times and they choose at registrations which classes during the week they want to attend. they can attend as little or as many classes as they want.

it just doesn't seem efficient to make people logout again to register someone else for another class. it would seem better to have one login and they can register as many memberships and class registrations as they want on their own login without anything overwriting their contact details.

in testing i tried logging in and registering myself as two different people for a class and it just overwrote the initial contact with the second one. is this supposed to do that? i have the "allow register with same email" option enabled and i also have only first name and last name as my default strict duplicate matcher so im jut not sure what's going on there.

would anyone like to have a go at perhaps helping me have a more efficient logic to my website? any help is appreciated

Hi,

Another option introduced by the 3.2 is to add a "checksum", so instead of having a login, you simply send them a link to register to the event that is unique and automatically log the user in. Works if you have a few events, and that they keep the email.