|
Francis
|
January 28, 2014 at 4:03 pm
We are still gettting to know what EE can and cannot do, but a couple of things are proving to be a bit of headache. For our entertainment events we don’t need to collect attendee information from every person, but we often have people reserving tickets for other people, so we want to make this optional. At the moment it seems to be all or nothing, i.e. you either collect the information for all attendees or for none at all. Why is this a problem? Well, because each person has to have information entered, if all or some of the tickets are in the same name EE lists, for example, 5 x the same name in the attendee list rather than grouping the tickets as 1 x 5 tickets under one name.
Also, the person booking the tickets has to be an attendee, which is not always the case! OK, the person booking can be permitted to change the first attendee (we want to have people log in before they book so would have to allow the information to be edited), but it would be good to have the person odering separate from the attendees, like a separate record “ordered by”. This could also be set as attendee 1 as standard, but it should be possible to change attendee 1 and still keep the ordered by information.
Will version 4 do any of this better? Or can we do this better now?
WP 3.8.1
EE 3.1.36.4
|
|
Dean
|
January 29, 2014 at 5:24 am
Hi Francis,
We have tried to make Event Espresso (3 & 4) as flexible as possible to be usable by the hundreds, if not thousands, of different event set ups out there.
We don’t always manage it.
Event Espresso 4 will be similar to, but different from, EE3 in that you will still need to allocate data to attendees or not, depending on the event set up. There is no option to swap between this from a users point of view.
The attendee list will still list the individual attendees, even if the names are the same (there are plenty of John Smiths in the world) but will group them together in the attendee overview by marking them as 1 of 5 etc.
We have long stated that if your events have people who book on behalf of others, to use custom questions to obtain that information, as attendees should be that, attendees.
This data can then be easily tracked via the primary attendee for example.
|
