Ticket form too complicated

Home Forums Ticket Products Event Tickets Plus Ticket form too complicated

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1087653
    Bart
    Participant

    Hi,

    We have the Event Calendar Pro setup together with the free version of the Tickets Add-on. Based on our experiences we will upgrade to the paid version later on.

    To our surprise, we get quite a few mails from people that cannot deal with the RSVP system. I have no idea why this is as it couldn’t be more simple. (you’ll find an example on our Dutch site here: http://www.wtnschp.be/tribe-events/stem-onderwijs-overheid-en-ondernemers-op-het-zelfde-spoor)

    My only guess is that people get confused because the fields for name and email don’t appear before you choose at least one ticket. And they might miss the resulting message after clicking RSVP..

    1) Would it be possible to add an explanation above the form so we can explain people what to do?
    2) Can we have the fields appear by default (and not only after you change the number of tickets from 0)
    3) Would it be possible to have the result of the RSVP appear on top of the page? now, it appears at the bottom and if people don’t scroll down the page they might miss the message about success or failure.

    #1087721
    George
    Participant

    Hey Bart,

    Sorry to hear about the confusion here!

    I will address your three questions to try and lead to a more useful RSVP form.


    1) Would it be possible to add an explanation above the form so we can explain people what to do?

    YES, but only with custom coding. 🙁 We cannot help with custom code, so if you are curious about adding this explanatory text to your template files, you would need to do it using the methods described here → https://theeventscalendar.com/knowledgebase/themers-guide/

    The specific file you would be customizing and adding the message to is this one:

    src/views/tickets/rsvp.php

    You could theoretically also add the explanation using CSS3 pseudoelements. It’s a bit of a “hack” but an easier method if you’re not comfortable with the method shared above. To this, you would add CSS like the following to the bottom of your theme’s style.css file. The explanation goes between quotes for the content value below. For example:


    .tribe-events-tickets.tribe-events-tickets-rsvp::before {
    clear: both;
    display: block;
    float: left;
    width: 100%;
    content: "To RSVP for this event, select the number of attendees on the left. This selection will reveal some fields which you will need to fill out, which request some basic personal info. We'll use that to reserve your seat, and will see you at the event!";
    }


    2) Can we have the fields appear by default (and not only after you change the number of tickets from 0)

    YES—add CSS like the following to the bottom of your theme’s style.css file.


    .tribe-events-tickets .tribe-tickets-meta-row {
    display: table-row !important;
    }


    3) Would it be possible to have the result of the RSVP appear on top of the page? now, it appears at the bottom and if people don’t scroll down the page they might miss the message about success or failure.

    This would unfortunately only be possible with extensive code customization using the methods shared above in my reply to your first question. I would recommend checking out those methods and tinkering around a bit.

    Best of luck with your customizations!
    George

    #1090185
    Bart
    Participant

    Thanks for the feedback. But the new version 4.1 that was just released does not hide the email/name fields anymore? They are shown immediately without the extra CSS code you specified above. Is this correct?

    Also, all text appears in English. I assume translations will follow later?

    #1090186
    Bart
    Participant

    Additionally, how can we change the layout of that part. I would like the margins wider between the fields and below the button:

    http://www.wtnschp.be/tribe-events/food-for-thought-ehb-editie-1

    #1090266
    George
    Participant

    Hi Bart,

    The ticket forms in 4.1 may indeed appear a bit differently on your site. To experiment with the appearance and see what 4.1 does on your site, simply remove the custom code I have shared temporarily. The way things look with my custom code removed are the way things look “by default” in your theme, and may indeed be good enough for you without the custom CSS I recommended earlier.

    As for the text being in English, yes, every time there is an update there are unfortunately new and different strings that might not be translated in time for the release. We unfortunately have no role in this; Translations are entirely community-generated things, and so your language simply may not be up-to-date yet with 4.1. To learn about how translations work with our plugins, and how to possibly contribute some of your own, check out these links:

    • Translating The Events Calendar: http://theeventscalendar.com/knowledgebase/translating-the-events-calendar/

    • Translating our premium add-ons: https://theeventscalendar.com/knowledgebase/adding-or-updating-a-translation/

    • Changing the language on your site: https://theeventscalendar.com/knowledgebase/changing-the-language-on-your-calendar/

    Finally, to make your margins wider or to make any other design customization on your site you will need to write custom CSS to do this. If you need to write custom CSS on your site, definitely check out a [free!] tool like Firebug if you use FireFox, or the Developer Tools for either Safari or Chrome. They have “Inspector” tools that let you zoom right over the element whose margins, colors, etc. you need to change.

    If you are not comfortable writing CSS yourself, then you will have to hire a developer to make the customizations for you. We have a list of great developers here → http://m.tri.be/18k1 (and have no affiliation with any of these folks—they’re simply some well-respected names in the community that we’ve compiled to share in situations like this one).

    Thanks,
    George

    #1097038
    Support Droid
    Keymaster

    This topic has not been active for quite some time and will now be closed.

    If you still need assistance please simply open a new topic (linking to this one if necessary)
    and one of the team will be only too happy to help.

Viewing 6 posts - 1 through 6 (of 6 total)
  • The topic ‘Ticket form too complicated’ is closed to new replies.