|
Katy Schroeder
|
March 8, 2014 at 7:21 pm
I have an event occuring next Friday March 14th, and currently the EE4 is just sending confirmation that doesn’t include how many tickets they actually bought for each show. I need a way to send every attendee a ticket. When I try to go back to EE3, it tells me I have fatal errors and disrupts the whole ticketing system. I realize you don’t have a Ticketing addon for EE4 yet, so is there a way to go back to EE3 without affecting any of the already purchased tickets and keep the system running without shutting it down.
Thanks!
|
|
Tony
|
March 10, 2014 at 6:26 am
so is there a way to go back to EE3 without affecting any of the already purchased tickets and keep the system running without shutting it down.
Tickets purchased through EE3 or EE4?
EE4 was designed so that EE3 data could be migrated from EE3 to EE4 and the original EE3 data would not be lost, however tickets purchased within EE4 will not migrate to EE3 as they are totally different systems. (EE4 custom post types, EE3 custom tables)
When I try to go back to EE3, it tells me I have fatal errors and disrupts the whole ticketing system.
Without the full error we can only guess but are you trying to activate both EE3 and EE4 at the same time? You can have either EE3 or EE4 activated but not both.
Do you currently have registrations taken through Event Espresso 4 for this upcoming event?
|
|
Katy Schroeder
|
March 10, 2014 at 10:13 am
Yes we have them for both. I have figured out how to registrations reports but wish there was a ticket template for 4. Very disappointing transition. Had I known it was going to be this much trouble, I never would have updated.
|
|
Josh
|
March 11, 2014 at 12:23 pm
Hi Katy,
Can you let us know which version of Event Espresso you are using right now?
|
|
Katy Schroeder
|
March 11, 2014 at 12:26 pm
EE4. I can’t go back to EE3 or I lose all the registrations for EE4 don’t I?
|
|
Josh
|
March 11, 2014 at 12:36 pm
This is correct. Have you tried customizing the default message template for the emails that you’re sending out? They can be made to look more ticket like. With that, here is some example content that can be added to the [TICKET_LIST] section of the messages template:
<ul>
<li class="ticket-name"><strong>Ticket Name:</strong> [TICKET_NAME]<br><em>[TICKET_DESCRIPTION]</em></li>
<li><strong>Price:</strong> [TICKET_PRICE]</li>
<li><strong>Quantity Purchased:</strong> [TKT_QTY_PURCHASED]</li>
</ul>
<hr />
Then you’ll add [TICKET_LIST] to the Main Content section of the message template.
The above will display how many tickets they actually bought for each show in the email confirmation message.
|
