|
MIGS
|
June 2, 2015 at 2:17 am
We’re trying to set Event Espresso (EE4) up for a client of ours who’s organising a conference. What we need is to create a main event (the conference itself), then create optional sub-events that attendees can sign up for. The sub-events are free, they just want to know that the attendees for the sub events have paid for the main event.
|
|
Josh
|
June 2, 2015 at 7:23 am
Hi Gabriel,
It turns out that EE4’s ability to publish multiple tickets for one event is functionally the closest thing to publishing sub-events (Publishing sub-events is not currently possible with Event Espresso).
You can make one ticket required (for the conference itself), then allow the other events to be optional. You set the main conference ticket to be required by clicking on the gear icon for the main conference ticket, then you check the box next to This ticket is required (will appear first in frontend ticket lists).
This will make the main conference ticket be required, and all of the other tickets will be optional.
Does that help?
|
|
MIGS
|
June 2, 2015 at 8:53 am
Yes. Actually, that’s the conclusion I got to myself as I was testing.
We have an “Early Bird” ticket and then the “Standard” ticket. They both need to be set as “Required”, but I don’t want both of them to show up at the same time when the user is selecting. I set the early bird ticket to be available until a certain day and the standard ticket to be available after, but they’re both showing up. One of them just states the day that it will be available for sale. Can I switch it off?
|
|
Josh
|
June 2, 2015 at 9:31 am
Hi Gabriel,
The ticket that’s not for sale yet can be hidden with CSS, which is something you can add to your stylesheet:
.ticket-pending {
display: none;
}
There is a setting for expired tickets that you can switch off in Events > Templates. At the bottom of the Template settings admin screen, you’ll see this option: Show Expired Tickets? and you set it to No.
Then, when the early bird ticket is no longer available for sale, it will not be displayed.
|
|
MIGS
|
June 3, 2015 at 3:41 am
Thanks, I’ll do that.
In the meantime, we need to implement the APCO (PayFast) payment gateway and we can’t figure it out. Could you please quote how much it will cost for you to do this for us? We can give you the API.
|
|
Josh
|
June 3, 2015 at 8:16 am
Hi Gabriel,
It turns out that PayFast developed a gateway integration in house for Event Espresso 3. They may be able to develop one for Event Espresso 4 as well. I can recommend contacting them to see if they have plans to build one.
If they’re not interested in building an integration for Event Espresso 4, we can build one and the standard sponsored development fee listed here will apply.
|
