Support

December 11, 2017 at 8:13 am

Hi there,

We’ve received your request for priority support. While we cannot log in to your website with the credentials you sent, we can help you get on the right track if you can outline exactly what you’re trying to accomplish with questions & ticket options.

May I ask can you post a link to the event page, and a list of each of the tickets with the questions they need to be mapped to?

December 11, 2017 at 8:38 am

Is there anyway to speak to someone directly about this? Or can you help me get you into my site?

You can resend the redeem a support token form, and send the correct information to log into your WordPress site. the information you sent appears to be the log in credentials to log into eventespresso.com, we do not need those.

That said, we probably don’t need to log into your site to help you with this.

So for example, they can purchase a ticket for one entry plus one extra class, but they can click on as many things as they want to once they’re in the reg form. Is there a way to control that?

One way would be to split those different ticket options into their own events. Then you can set up a unique custom question group for each option, then assign each unique question group to each event.

Another approach would be to keep everything within one event, but then use CSS to hide questions that shouldn’t be displayed based on which tickets were selected.

December 11, 2017 at 8:56 am

Can you outline a specific example of a division ticket, and exactly which questions would be narrowed down to?

December 11, 2017 at 9:12 am

So for example if they wanted to compete in the Men’s Bodybuilding Division and compete in two classes where they would purchase the entry plus one crossover ticket, then which options do you want to limit them to?

December 11, 2017 at 9:53 am

One issue I see is it looks to me that these questions could be re-organized to keep like data with like data. So for example if it’s class that applies to a specific age group then in one question give these options: teen, 40+, 50+. And instead of multiple choice/checkboxes, you can use radio buttons which forces the age option to one answer.

Then you set up a second question for classes that doesn’t apply to a specific age group: novice, open. If someone will compete in both novice and open, then you can set that question to be multiple choice/checkbox. If someone will compete in novice or open (not both) then that question should also be set to be a radio button question type.

Is that something you can change to get this started on the path forward?

December 11, 2017 at 10:26 am

The way to solve that problem will be to split out each division into its own event. This way you’ll have more control over the questions for each division. Would it be OK if I set up two example test events that would show an example of how that would work?

December 11, 2017 at 10:32 am

They can all be listed on one page, yes.

December 12, 2017 at 10:37 am

You’ll actually be adding new CSS that will target the new tickets and new questions.

The ticket ID’s for the tickets to target are:

43 — Early Entry Registration
44 — Early Entry Registration + 1 Crossover
45 — Early Entry Registration + 2 Crossovers
47 — Late Entry Registration
48 — Late Entry Registration + 1 Crossover
49 — Late Entry Registration + 2 Crossovers

Notes: You’ll notice that the +3 Crossover tickets do not get targeted, this is because when someone selects +3 Crossover they should see all of the crossover options.
You can get the ticket ID by clicking on the gear icon to open each ticket’s advanced editor.

The Question ID’s to target are:
28 — Men’s Physique Additional Class
29 — Men’s Physique Second Additional Class
30 — Men’s Physique Third Additional Class

The Question ID’s are found in table on the Event Espresso > Registration Forms > Questions page.

You’ll add the additional CSS to the CSS editor page located at Appearance > Edit CSS. You plug those ID’s into the CSS like this:

/* men's physique tickets */
/* zero crossovers */
/* early */
.spco-attendee-ticket-43 .ee-reg-qstn-28-input-dv,
.spco-attendee-ticket-43 .ee-reg-qstn-29-input-dv,
.spco-attendee-ticket-43 .ee-reg-qstn-30-input-dv,
/* late */ 
.spco-attendee-ticket-47 .ee-reg-qstn-28-input-dv,
.spco-attendee-ticket-47 .ee-reg-qstn-29-input-dv,
.spco-attendee-ticket-47 .ee-reg-qstn-30-input-dv {
		display: none;
}
/* one crossover */
/* early */
.spco-attendee-ticket-44 .ee-reg-qstn-29-input-dv,
.spco-attendee-ticket-44 .ee-reg-qstn-30-input-dv,
/* late */ 
.spco-attendee-ticket-48 .ee-reg-qstn-29-input-dv,
.spco-attendee-ticket-48 .ee-reg-qstn-30-input-dv {
		display: none;
}
/* two crossovers */
/* early */
.spco-attendee-ticket-45 .ee-reg-qstn-30-input-dv,
/* late */ 
.spco-attendee-ticket-49 .ee-reg-qstn-30-input-dv {
		display: none;
}

December 12, 2017 at 12:01 pm

May I ask what part do you not understand? The reason I ask is because all of the work is done that event, you just need to copy and paste in the above CSS.

December 12, 2017 at 2:45 pm

Do you mean where to change the URL for the navigation menu? If so, you can change that in WP > Appearance > Menus.