Show or hide queried fields in the booking form and/or in the mail templates

[Anonymous]

Hi, I am looking for a solution to query different dates of bookers in a single booking template or email template instead of creating multiple individual templates.
I wonder if that can be solved with attributes. On the settings page, I find no way to define custom attributes like the custom fields. Unfortunately, even with the description in the documentation, I did not understand the use of attributes.

Example of my problem:
At event (A) only the name and email fields should be requested (and displayed) for booking. At event (B), the address data field should also be requested (and displayed).
I would like to solve this with a single booking form, in which I then show or hide the data to be queried e.g. with [eme if]
Is there a way to do that? Thank you!

[Franky]

The only way to ask for info concerning multiple events in 1 form is by using the multi-booking form. But then the rsvp form (the repeated part of it) is defined identical for all, so you’d have to play with the event id (or maybe with an event category) to show/hide certain fields.
Event attributes are for events, not for rsvp forms. So in your case you’ll want to look at custom fields. I’m planning on adding some simple instruction videos this week 🙂

[Anonymous]

Thanks again for the super quick answer, Franky! An instruction video for the custom stuff sounds good 😉
Using custom fields is a good idea to add the required fields to an event without much coding, but especially for the basic fields this would be no clean data. It would be perfect if a custom field with the same name like a basic-field would overwrite / fill that basic-field, e.g.
a custom field “address1” would fill the basic-field “address1” and would not create a new field with the same name.
What do you think about that?

[Franky]

A custom field can’t fill one of the basic fields, that’s simply not manageable.
You can create custom fields that collect any needed data (even like an address) and not use the basic fields (except name and email).

[Author]

Posts