Now, as you specified 3 prices in the example above, people should be able to book for those 3 as well. For this you need to change the setting “Registration form format” for the event.
Usually you just enter the shortcode #_SEATS there, to have a dropdown to select a number of seats to book. Now in this case, you need 3 of those, with a number behind them: #_SEATS1, #_SEATS2, #_SEATS3
E.g. the “Registration form format” could then be like this:

<table class='eme-rsvp-form'>
<tr><th scope='row'>Name*:</th><td>#_NAME</td></tr>
<tr><th scope='row'>E-Mail*:</th><td>#_EMAIL</td></tr>
<tr><th scope='row'>Phone number:</th><td>#_PHONE</td></tr>
<tr><th scope='row'>Seats for children:</th><td>#_SEATS1</td></tr>
<tr><th scope='row'>Seats for adults:</th><td>#_SEATS2</td></tr>
<tr><th scope='row'>Seats for students:</th><td>#_SEATS3</td></tr>
<tr><th scope='row'>Comment:</th><td>#_COMMENT</td></tr>
#_CAPTCHAHTML[<tr><th scope='row'>Please fill in the code displayed here:</th><td>#_CAPTCHA</td></tr>]
</table>
#_SUBMIT

See screenshot:

For more info about formfields, read the doc concerning that

• #_ATTENDNAME displays the name of the attendee.
• #_ATTENDEMAIL displays the e-mail address of the attendee.
• #_ATTENDPHONE displays the phone of the attendee.
• #_ATTENDID displays the numerical ID of the attendee.
• #_ATTENDSPACES displays the total amount of seats booked by the attendee.

• id: the ID of the event for which the unsubscribe form should be shown.

Example:
[events_delete_booking_form id=4]

• id: the ID of the event for which the booking form should be shown.

Example:
[events_add_booking_form id=4]

<table class='eme-rsvp-form'>
<tr><th scope='row'>Name*:</th><td>#_NAME</td></tr>
<tr><th scope='row'>E-Mail*:</th><td>#_EMAIL</td></tr>
<tr><th scope='row'>Phone number:</th><td>#_PHONE</td></tr>
<tr><th scope='row'>Seats*:</th><td>#_SEATS</td></tr>
<tr><th scope='row'>Comment:</th><td>#_COMMENT</td></tr>
#_CAPTCHAHTML[<tr><th scope='row'>Please fill in the code displayed here:</th><td>#_CAPTCHA</td></tr>]
</table>
#_SUBMIT


You can use the following shortcodes

• #_NAME displays a text field for the name of the respondent.
• #_EMAIL displays a text field for the e-mail address of the respondent.
• #_PHONE displays a text field for the phone of the respondent.
• #_SEATS or #_SPACES displays a dropdown field for the number of spaces to reserve.
• #_SUBMIT[] displays displays the submit button with between square brackets the text you want for the button (qtranslate compatible).
• #_SUBMIT displays displays the submit button with the text you want for the button the text configured on the Settings page.
• #_COMMENT displays a text area for a possible comment.
• #_CAPTCHAHTML displays the html between the square brackets for the captcha, but only if the captcha option has been activated. Inside the square brackets, you should use the shortcode #_CAPTCHA to display the captcha itself, otherwise nothing will happen.
• #_CAPTCHA displays the captcha part.
• #_FIELDxx displays custom made fields (replace xx by the ID of a field you created in the “Events => Form fields” page.

For any shortcode, if you start with “#REQ_” instead of “#_”, the field becomes required and cannot be left empty or 0 upon registration (e.g.: #REQ_COMMENT or #REQ_FIELDxx)
Warning: if the shortcodes #_NAME, #_EMAIL, #_SEATS or #_SUBMIT are not present, the form is not valid and will not be shown.
Also, #_NAME and #_EMAIL are always required fields, so no need to use #REQ_NAME or #REQ_EMAIL.

• id: the ID of the event for which you want the countdown to happen. If not specified: countdown until the first future event.

Example:
[events_countdown id=25]

• eventful: if set to true, only locations with events planned will be shown. Default: false.
• scope: see the explanation for [events_list]. You need to set eventful to true for this to have any effect.
• category: see the explanation for [events_list]. If eventful=true as well, then only locations with events matching the category criteria are shown.

Example:
[events_locations eventful=true scope=this_week]

add_action('eme_insert_rsvp_action','do_my_stuff');
function do_my_stuff($booking) {
 ....
}

The following hooks are available:

• eme_insert_event_action (1 parameter: $event)
• eme_update_event_action (1 parameter: $event)
• eme_insert_recurrence_action (2 parameters: $event,$recurrence)
• eme_update_recurrence_action (2 parameters: $event,$recurrence)
• eme_insert_rsvp_action (1 parameter: $booking), executed after inserting rsvp info into the db

The following filters are available:

• eme_event_filter (1 parameter: $event array)
• eme_event_list_filter (1 parameter: array of events)
• eme_location_filter (1 parameter: $location array)
• eme_location_list_filter (1 parameter: array of locations)
• eme_directions_form_filter (1 parameter: generated html for the directions form)
• eme_add_booking_form_filter and eme_delete_booking_form_filter (1parameter: generated html for the add or delete booking form)
• eme_email_filter (If defined, the standard ascii obfuscating won’t take place and you can use your own filters, eg. from an obfuscating plugin, if you define it in functions.php:
  add_filter( ‘eme_email_filter’, ‘c2c_obfuscate_email’ );)

• Nothing, you then just check that the placeholder/string mentioned in the tag is not empty: [events_if tag='#ESC_TOWN']
• is_empty=1 checks that the placeholder/string mentioned in the tag is in fact empty: [events_if tag='#ESC_TOWN' is_empty=1]
• value checks if the placeholder/string mentioned in the tag is the same as the one mentioned in value:
  [events_if tag='#ESC_ATT{color}' value='red'] color: #_ATT{color} [/events_if]
• notvalue checks if the placeholder/string mentioned in the tag has a value different than the once mentioned in value
• lt checks if the numerical value of the placeholder/string mentioned in the tag has a value lower than than the once mentioned in lt
• gt checks if the numerical value of the placeholder/string mentioned in the tag has a value bigger than than the once mentioned in gt
• contains checks if the value of the placeholder/string mentioned in the contains occurs in the once mentioned in tag
• notcontains checks if the value of the placeholder/string mentioned in the notcontains doesn’t occur in the once mentioned in tag

As extra, next to the regular placeholders you can use, I added some extra shortcodes:

• #_IS_SINGLE_EVENT (’1′ if you’re viewing a single event details, ’0′ otherwise)
• #_IS_SINGLE_LOC (’1′ if you’re viewing a single location details, ’0′ otherwise)
• #_IS_LOGGED_IN (’1′ if user is logged into WP, ’0′ otherwise)
• #_IS_ADMIN_PAGE (’1′ if on the admin pages, ’0′ otherwise)
• #_IS_PRIVATE_EVENT (’1′ if the event is a private event, ’0′ otherwise)
• #_IS_RSVP_ENABLED (’1′ if the event is RSVP-able, ’0′ otherwise)
• #_IS_SINGLE_DAY (’1′ if you’re viewing a single day, ’0′ otherwise)
• #_IS_REGISTERED (’1′ if WP user has already registered for the event, ’0′ otherwise)

Example usage:
[events_if tag='#_IS_LOGGED_IN' value='0'] You are NOT logged in [/events_if]
[events_if tag='#_IS_LOGGED_IN' value='1'] You are logged in [/events_if]
[events_if tag='#ESC_CATEGORIES' contains='red'] The event is in at least the red category [/events_if]
[events_if tag="#ESCj #ESCM #ESCY" value="#ESC@j #ESC@M #ESC@Y"] The start and end date of this event is the same, so just showing start: #j #M #Y [/events_if]
A variant of the above, using curly brackets:
[events_if tag="#ESC_{j M Y}" value="#ESC@_{j M Y}"] The start and end date of this event is the same: #{j M Y} [/events_if]
Print start date, and print end date only if different:
#_{j M Y} [events_if tag="#ESC_{j M Y}" notvalue="#ESC@_{j M Y}"] #@_{- j M Y} [/events_if]

Using this conditional tag requires some playing around …
I also added [events_if2] and [events_if3], if you want to use more than one level of logic (wordpress doesn’t like a shortcode with the same name enclosed in another one)