Attendee vs. buyer registration information

WordPress Event Management, Calendars & Registration Forums Pre Sales Questions Attendee vs. buyer registration information

This topic contains 10 replies, has 3 voices, and was last updated by  Stephen Harris 8 years, 5 months ago.

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #12477 Reply

    Hi,

    I would like to use Event Organiser to sell tickets for a single event that has multiple ticket types, e.g. Regular, VIP. I can see from http://wp-event-organiser.com/demo/events/event/4th-thursday-every-2nd-month/ that it can support this requirement. What I can’t tell is whether it can do the following: if a buyer selects, say, two Regular tickets, can it be set to collect registration information, e.g. the name, email address and lunch option, for each attendee rather than just the buyer?

    Thanks,
    Richard

    Richard Tandoh
    #12480 Reply

    Hi Richard,

    Regrettably, at this point, not. This is a feature currently in development, (albeit the early stages of). So at present there is no ETA for it either.

    Stephen Harris
    #12501 Reply

    Thanks Stephen.

    That is a shame, as it rules it out for my current project.

    I’ll keep an eye on your work though.

    Richard Tandoh
    #15573 Reply

    Hi Stephen,

    It has been 6 months since I originally asked my question, so I was wondering if this feature is any closer to being offered.

    Thanks,
    Richard

    Richard Tandoh
    #15658 Reply

    Hi Richard,

    There’s a working ‘proof of concept’, but this requires some major changes in the way the front-end scripts handle tickets (currently there is no notion of a particular ticket, just quantities of ticket types). There are some other issues (largely relating to user experience) that need to be sorted out, but the technical challenges have been resolved.

    Some groundwork is being done in the upcoming 1.10.0 release (currently in beta), they’ll be further changes in the 1.11.0 release, which means “attendee questions” could be in 1.12.0 (2-3 months).

    Unfortunately I can’t give any guarantees of this as there are some unresolved issues as mentioned above.

    Stephen Harris
    #18181 Reply

    We are also looking to use this feature – we dont really sell different ticket types, but we are hoping to capture name and other information for each ticket bought, rather than just the person buying it.

    Is there any progress on this?

    Jessie Matanky
    #18210 Reply

    Yes there is :). The current alpha version of 1.11.0 allows for attendee questions. The core version, however will not do this. A plugin shall be released alongside v1.11 which will expose an API for adding attendee question,

    Please note there won’t be an UI for this, buttghere will be an API field for adding attendee questions. There’ll be documentation and examples released too,

    v1.11.0 is still in alpha waiting on a last few features to be polished off. There remains the possibility that the above mentioned plugin will be merged into 1.11.0 but in any case it will be possible!

    Stephen Harris
    #18733 Reply

    Just an update here, but v1.11.0 is in beta and will support “Attendee questions” as outlined above. It will need a few lines of code to take advantage of the feature, as there is no user interface in the customiser for it (yet).

    Stephen Harris
    #19510 Reply

    I read through your Attendee Questions blog post. I think I now understand what you meant when you say there is currently no user interface. The questions must be established in code – there is no drag and drop as for the forms.

    I want to include an Attendee Question that is a drop down for the attendee’s lunch choice. Whoever is making the purchase is making the purchase for several people who each have a different meal choice.

    Is there already a snippet somewhere that would allow me to add the drop down lunch choice code in with the sample snippets provided in the blog?

    Thanks

    Greg MacKinnon
    #19545 Reply

    Hi Greg,

    If you follow this tutorial and simply change the definition of the fields to:

    //Define the field we want to add    
    $attendee_fields = array(
        array(
            'id'   => 'attendee-lunch',
            'type' => 'select',
            'label' => 'Choose your lunch meal',
            'options' => array(
                 'option-a' => 'Option A',
                 'option-b' => 'Option B',
                 'option-c' => 'Option C',
            ),
            'required' => true,
        ),
    );
    

    That should do it.

    Stephen Harris
    #19546 Reply

    Hi Greg,

    If you follow this tutorial and simply change the definition of the fields to:

    //Define the field we want to add    
    $attendee_fields = array(
        array(
            'id'   => 'attendee-lunch',
            'type' => 'select',
            'label' => 'Choose your lunch meal',
            'options' => array(
                 'option-a' => 'Option A',
                 'option-b' => 'Option B',
                 'option-c' => 'Option C',
            ),
            'required' => true,
        ),
    );
    

    That should do it.

    Stephen Harris
Viewing 11 posts - 1 through 11 (of 11 total)
Reply To: Attendee vs. buyer registration information
Your information:




To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax


<a href="" title="" rel=""> <blockquote cite=""> <code> <pre> <em> <strong> <del datetime=""> <ul> <ol start=""> <li> <img src="" border="" alt="" height="" width=""> <p style=""> <span style="">