Support

January 23, 2020 at 2:23 pm

Hi there,

Is this in the admin or registrant context?

To answer your question, yes, it is possible and you can use [TKT_QTY_PURCHASED] in the Main content, however it depends on the specific email and context which you are sending if that is a valid shortcode or not.

January 23, 2020 at 2:36 pm

Let’s try to clarify then. When you wrote:

is there a possibility that the registration confirmation you get by email

May I ask, who is the “you” that gets the email? The person registering or is it the person organizing the event? Or are you asking about both emails?

January 23, 2020 at 3:08 pm

Here’s how you can add the number to your email:

1) You go to your site’s Event Espresso > Messages > Default Message Templates page
2) In the row “Registration Approved”, click on the “Edit Event Admin” link
3) Add:
Number of Tickets: [TKT_QTY_PURCHASED]
to the Main Content section of the template
4) Click Save

January 27, 2020 at 6:47 am

Hi,

Can you share a link to the event in question so we can see how it’s registration form is set up? The answer will depend on how that event’s form was set up.

January 28, 2020 at 7:51 am

Hi there,

Whilst it is possible to force EE to display only the ‘Primary Registrant’ details on that email, your event is set up to collect registration questions for each individual ticket.

That means a user could select 3 tickets and input different details for each ticket but you, as the event admin, would only see the ‘first’ registrant’s details and then a qty.

I can give you some details on how to set that up if it will work for you?

January 29, 2020 at 4:57 am

Ok.

You would need to edit the message template, assuming you are using the default templates go to:

Event Espresso -> Messages -> Default Message Templates -> Registration Approved -> Edit Event Admin

Go to the ATTENDEE_LIST section and copy all of the contents within that section.

Now, in the EVENT_LIST, switch to ‘Text’ mode on the editor and find the [ATTENDEE_LIST] shortcode.

Replace that shortcode with the contents of ‘ATTENDEE_LIST’ that you just copied.

Like so – https://monosnap.com/file/QLQ8YSwRsuQP5VFGPnhLZM05OIXZP9

Now, you’ll need to switch out all of the shortcodes used in that new text for their ‘Primary Registrant’ equivalent.

For example:

[FNAME] => [PRIMARY_REGISTRANT_FNAME]
[LNAME] => [PRIMARY_REGISTRANT_LNAME]
[REGISTRATION_CODE] => [PRIMARY_REGISTRANT_REGISTRATION_CODE]

To show a few, but there are a couple more.

(You’ll find a list of all available shortcodes for each section by clicking on the icon)

We don’t actually have a primary registrant equivalent for [EDIT_ATTENDEE_LINK] (which takes the admin directly to edit the registration. The closest would be:

[PRIMARY_REGISTRANT_FRONTEND_EDIT_REG_LINK]

Which takes you to the front end of the site, as a user would.

So your event list section will end up with something like this:

<p class="callout"><strong>
Event: [EVENT_LINK]
Venue: <a href="[VENUE_URL]" target="_blank" rel="noopener noreferrer">[VENUE_TITLE]</a> ([VENUE_CITY], [VENUE_STATE])
</strong></p>

<h2>Registrant Details:</h2>
<h4><a href="[PRIMARY_REGISTRANT_FRONTEND_EDIT_REG_LINK]">[PRIMARY_REGISTRANT_FNAME] [PRIMARY_REGISTRANT_LNAME]</a></h4>
        <ul>
<li><strong>Registration Code:</strong> <a href="[PRIMARY_REGISTRANT_FRONTEND_EDIT_REG_LINK]">[PRIMARY_REGISTRANT_REGISTRATION_CODE]</a></li>
<li><strong>Tickets:</strong></li>
</ul>
<ul>[PRIMARY_REGISTRANT_TICKET_LIST]</ul>
<strong>Questions & Answers</strong>
<ul>[PRIMARY_REGISTRANT_QUESTION_LIST]</ul>
<hr />

You’re template now basically skips the ‘ATTENDEE_LIST section and outputs the primary reg directly. THe _LIST sections loop over all of the objects passed to them so in this case because you have 3 ‘attendees’ you can’t use that section.

January 29, 2020 at 4:14 pm

I should explain a little here, the message templates are generated on activation and then stored in the database. That’s how we are able to allow customizations to the templates in the admin.

EE doesn’t replace those templates on updates and as they are stored in the database I would only expect some kind of possible issues to arise if we are messing with said database in some way (migration data) and not simply updating the plugin.