Customize event registration form for each reg. type
In Events, I'd like to have custom registration forms associated with each registration type instead of one single registration form for the whole event (all types). This would allow me to create more complex event registrations. Example: A three-day conference has two types of registrants (Individual and Professional) at different prices. Each one has an early-bird price as well. In addition, each one can choose to register for one day, two days, or all three days -- all at prorated prices.
To do this today, I have to create separate events for Individuals and Professionals, then customize those event reg. forms. Then the choice of which days they want to attend must be an Extra Cost add-on to the registration. It's a bit awkward to implement and a bit confusing to registrants.
It's quite a bit of work, but this is on our (long-term) roadmap, I will merge into existing thread.
How difficult would it be to apply the same concept available in "Customize member database fields" to the event registration forms?
As written currently, you can customize specific database fields to appear in specific types of membership levels. For example, you might want to collect a company name for those selecting institutional membership but not for those selecting individual membership. And you can design the membership fields to only appear when a specific type of membership is available.
So how difficult would it be to apply that same concept to event forms? When someone selects a Day registration as a registration type, the registration form will show the "Select the day you wish to attend" option... but when someone selects Full registration as a registration type, the registration form WILL NOT show the "Select the day you wish to attend" option.
Another way to ask would be, if you look at the Membership fields settings page you see 3 options:
Field applies to:__ All fields, __ all fields in level ((Select membership level)), __ common for all levels.
Can the registration form fields page be changed to say:
Field applies to: __ All fields, __ all fields in type ((select REGISTRATION TYPE)), __ common for all fields.
Thanks in advance.
I'd also need conditional fields, not so much for event registration but the membership application. So that I don't have to inflate the number of membership types.
My example: Certain people can join for a reduced rate. But students would have to upload a copy of their ID (mandatory) , others not. By now I need two membership types for that..
Or: every applicant must send a CV. But this can be a link to a website OR a document to be pasted in another field (or uploaded (wishlist!), then invisible to others. I don't see how I can solve this issue now.
This makes total sense, I though we already had a thread about this but could not find one.
This thread made me think of this: http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8826646-multiple-choice-with-extra-cost-needs-more-mgmt
Would love to have a feature where the questions in an event registration changed depending on what registration type you selected. I could have used this feature on multiple occasions, but because of the current layout, I've created separate events.
For example, if we have both students and professionals attending an event, we would ask the students what University they are from, what professor they want extra credit for. Professionals, we'd ask their license number to submit continuing education credits. Right now we ask ALL these questions but they are optional to answer. Would be nice if you selected "professional" registration all the student questions went away.
This is very similar to a feature that is already available in the membership form. How certain fields only apply for certain membership levels.
Evgeny Zaritovskiy commented
Thanks for your input, we will consider this in our scenarios.
Jennifer Walker commented
I would like the ability to restrict additional cost fields to certain event registration types. For instance, I'm working with a conference that has the following registration levels:
* Full conference, early bird
* Full conference
* One day only
* Pre-conference only
The problem is that the pre-conference can be added to the first four registration types. But if I add pre-conference as a multiple choice item with extra cost, it still shows up on the pre-conference only registration type. Also, student pre-conference is a different amount so I would like to distinguish between student pre-conference and regular pre-conference and have them show up as add'l costs for the applicable registration type.
The solution would be the ability to choose which registration types an extra cost shows up for, similar to the way the membership registration form allows one to restrict some fields to targeted membership types.
p.s. - great product; keep up the great work!!
I also need more flexibility in the event set-up. We have conferences where there are several ticket types for 1 event, just like the others indicated here. We have been using eventbrite for our events and their "ticket" system works quite well. For example you can set up: (This is directly from the eventbrite event we set up.
Ticket Type Sales End Price Fee Status
Royal Flush Rate Members
Each paid membership (primary OR secondary) entitles two attendees at the Member Price. Additional attendees must pay the non-member price. Feb 26, 2010 $218.38 $6.62 ** Hidden Show
For Help On Ticket Purchase Call 970-669-6833
7 hours before event Free Tickets Sold Out Hide
Member Single Ticket
Must be a CALA Member Apr 19, 2010 $242.76 $7.24 ** Ended Hide
Member 2 Pack Special
Members BOGO 1/2 Price Special. One attendee MUST be a CALA member. Apr 09, 2010 $181.82 $5.68 ** Ended Hide
Member 3 Pack Special
Members Buy 1 Get 2 Half Price Special. One attendee MUST be a CALA member. Apr 09, 2010 $161.50 $5.16 ** Ended Hide
Non-Member Single Ticket
Apr 15, 2010 $315.88 $9.12 ** Ended Hide
Non-Member 2 Pack Special
Non-Members BOGO 1/2 Price Special Apr 09, 2010 $236.67 $7.08 ** Ended Hide
Non-Member 3 Pack Special
Non-Member Buy 1 Get 2 Half Price Special Apr 09, 2010 $210.25 $6.41 ** Ended Hide | Delete
Members - 1 Day
Each paid membership (primary OR secondary) entitles two attendees at the Member Price. Additional attendees must pay the non-member price. Apr 16, 2010 $145.26 $4.74 ** Ended Hide
Non-Members - 1 Day
Consider joining CALA for only $200/year and get your convention tickets at Member Price! Apr 09, 2010 $218.38 $6.62 ** Ended Hide | Delete
Flush Rate Members - 2 Day
Each paid membership (primary OR secondary) entitles two attendees at the Member Price. Additional attendees must pay the non-member price. Apr 09, 2010 $340.26 $9.74 ** Hidden Show | Delete
Flush Rate Non-Members - 2 Day
Consider joining CALA for only $200/year and get your convention tickets at Member Price! Apr 09, 2010 $415.05 $9.95 ** Hidden Show | Delete
Flush Rate Members - 1 Day
Each paid membership (primary OR secondary) entitles two attendees at the Member Price. Additional attendees must pay the non-member price. Apr 09, 2010 $194.01 $5.99 ** Hidden Show | Delete
Flush Rate Non-Members - 1 Day
Consider joining CALA for only $200/year and get your convention tickets at Member Price! Apr 09, 2010 $267.13 $7.87 ** Hidden Show | Delete
This is an extreme example, but it worked well for us. Also, need a way to send invitations to a select group of people.
Kim Skimmons commented
Conditional fields would be awesome too -- and not just for event registrations but for the membership application as well!
But it will not solve my complex, multi-day, multi-type registration problem.
Thanks Russell, appreciate the detailed example - this is exactly the kind of information we are looking for, please always feel to share as broadly as possible so that we understand full context.
I have a great example of this that I am having to deal with right now. This event actually covers 2 wishlist items, but that is a different matter.
I have an event with 3 Registration types.
This is a joint event between our organization and another organization, which accounts for the first 2 registration types.
1. Member Registration
2. Other Organization Member: Uses entry code to validate membership
3. Non-Member - Signing up for this costs a flat amount which will give the person membership in both organizations for a year. For this reason, we are collecting address, job title, and other contact information for these people.
The information that is being collected for Membership Type 3, does not need to be collected for #'s 1 or 2. We already have that information for existing members.
I think that this directly supports the need to have Registration Form Fields be tied to the Registration Type.
On the separate note, is the wish, which has been discussed in other places, to tie event registration and membership registration together. Since the Non-members will gain membership in our organization for a year when they pay, we will have to separately add them as members, and re enter the collected contact information into the appropriate fields under membership. It would be great to have, for example, a checkbox option to add this registration type as new members, and also to select which membership type should be applied. This would then autogenerate an invoice and payment completion with the fee that was included on the event registration form.
Another tangent: If you are able to link a membership, and a membership type, then if this is done when setting up a membership form, if you pulled the list of available fields from a membership type, and could choose to add those to the registration form so they would be directly linked like the initial contact fields are now.
Sorry those other comments are off topic. Feel free to move them if there is a more appropriate place.
I would appreciate comments from others - especially examples of when different registration forms can be needed for each registration type.
An alternative to this is for us to implement 'conditional fields', where fields are shown/hidden based on other field choices.
I would like to add to WA wish list a request to have a different form for each registration type. Something like this example:
Event: Tennis tournament
Type: Tournament with meal - price $30
Form 1 - showing meal choices
Type: Tournament without the meal - price $20
Form 2 - not showing any meal choices
Having two events is hardly good solution.
Thank you. Danusia
Anyone else would find this useful? Please comment here.
I am surprised that no other users have commented on this.
I wonder if maybe could post a specific detailed example of what you need - people might find it easier to relate to it.
I would appreciate comments from other users and additional examples.
Jason Pryde commented
From my research of the WA Event configuration UI, I don't see any way to customize the display of custom fields based on the users chosen Event Registration Type.
For certain registration types, we'd like to display specific custom fields.
An even better solution would involve hiding custom fields after a set number of user selections, ie a maximum threshold of selections for a given custom field value.
Can someone point me to an example / tutorial where this is done dynamically in JS?
We would like the "rules and terms" box which displays the club's liability waiver to show up only when non-members register for an event. Our members have already checked the box so there is not need for them to do so again.
I'd like a way to customize events so that people in certain membership groups will only see certain options in the registration form. For example, I have three registration options for a particular event, either lunch only, the seminar only or both the lunch and seminar, and all of these options have different prices depending on what type of membership you have and also a different price for nonmembers. I want a way for nonmembers to only see the nonmember registration options, and different classes of members to only see the registration options that pertain to them.
The only workaround for now is to create separate events for each member level and non-members, and only show the appropriate event to the appropriate level. This is very clunky and not user-friendly, though.