Hi Tuan,
Can I suggest an algorithm something like this to perhaps minimise the long form issue?:-
To avoid a long form, What about being directed to the same form for each individual person and save each one as they are registered? These individuals could then be 'listed' (just their name eg) with the cost against the event/category as registered on the 'first' page. Perhaps there could be an option to delete or modify here as well.
Scenario:-
For this event only individuals are able to register. i.e no group registrations allowed.
There are two events/categories A-Seniors B-Juniors
1. Five members of the one family living at the same address - two seniors and three juniors.
Step one - Option to enter as an individual or as a group (of individuals) with one payment on checkout.
* At registration a Senior person who is registering for all members is directed to the event/category form selected and then enters themselves (in the Senior category) and then enters all of the common data - address, email, phone no, etc.
* Below this there would be two buttons:- "Register another individual" and another to "Pay/checkout now".
* Selecting the first button the user data is saved and then is directed back to the first registration screen. Their name is now listed against the event they've registered for with the cost and a running total cost for all.
Step 2 The next person is entered in the category selected (Senior or Junior) but this time there is a check box asking if the same common data is to be used.
If checked then all that is required is to enter their name. If not then the common data inputs would be shown.
Step 3 This iteration would continue until the "Pay/checkout now" is pressed and you are taken to a payment page.
It would be nice if merchandise (eg T-shirts) could be included in this process as well.
Anyway, just my thoughts. I know it's easy to put in words but a 'bit' harder to implement in code.
I appreciate that you're looking into this.
Thanks,
Darryl