Support

September 28, 2015 at 5:14 am

Hi there,

So did this effect only individuals that purchased both this and last year?

Meaning these individuals:

Many other individuals had no issues…

Were registrations that only purchased this year?

Are the events separate events or an event with multiple datetimes?

How did you select the registrations to send the newsletter?

September 29, 2015 at 11:32 am

The problem here is the newsletter message type is a ‘contact’ based message type.

So EE is pulling the contact for the registration but if the contact has more than one registration assigned to it (they purchase both last year and this) EE doesn’t know which registration [RECIPIENT_TICKET_URL] should be used to build out the shortcode. It pulls the first registration (which will be last year if they purchased that) and build the shortcode using that.

It will work with contacts that have a single registration, but not if they have multiple registrations.

I’ve opened a ticket to discuss how we can work around this and will update this thread with any news.

October 2, 2015 at 5:15 am

Yes deleting last years registrations will work, as then those contact only have a single registration assigned to them, so [RECIPIENT_TICKET_URL] can only return that registrations tickets…

However removing last years registrations will lose the record of that registration and each also registration will need the payments from the transactions to be removed first before the registration can be removed, depending on the amount of registrations that’s going to take a lot of work.

So within your other thread here:

https://eventespresso.com/topic/more-shortcode-fields-in-the-newsletter-message-template/#post-174895

You mentioned that a single email with all of the tickets within that email would work, so for that we can actually use a custom Reg Approved message and and force EE to ‘resend’ that custom message for the event.

It’s a workaround to get your correct tickets sent out and will take a little fiddling around but as I explaining in your other thread above, the Reg Approved message is an event based message type and so the content/shortcodes within that message are specific for the event that was used to trigger the message, meaning the registrants will receive the correct ticket link.

I would advise first creating a couple of test registrations on this years event.

At least 1 registration for a single ticket and another for at least 2 tickets, this is to test to your custom email works as expected, before sending it on to your registrants.

Then go to Event Espresso -> Messages.

Find your Registration Approved message and click the ‘Create Custom’ button on the right – http://take.ms/YUKnI

EE will create a custom Reg Approved Message and open the editor for that message, add a title and a description for the message so you know what it is, using a descriptive title makes it easier to select later on – http://take.ms/pYfFD

When you first edit the message you’ll be in the ‘Event Admin’ context. I’m assuming you don’t need this in this case, so set the ‘To’ field to nothing and save the template. This disables the ‘Event Admin’ context.

Now switch the template to the Recipient – http://take.ms/CUUDu

Now we are in the Recipient context, this is the message that will be set to the registrant shortly. You can alter this message as much as you want but the only change I will make is to add the tickets URL.

So for me I’ll add:

Your tickets are available here: [TXN_TICKETS_APPROVED_URL]

Within the ‘main content’ section – http://take.ms/GmNWr
(I’ve wrapped it within h2 tags just to make it stand out)

[TXN_TICKETS_APPROVED_URL] parses to a link that will output all of the tickets for the Approved registrations within a group (if it’s a single registration then its just one ticket)

Place that anywhere you prefer within the Main Content, save and then preview to see how it looks (the link will not actually work in preview).

After previewing I moved the code up into the main section, above the EVENT_LIST, like this – http://take.ms/JSJgV

But again this can be however you prefer.

Ok so now you should have a custom reg approved message, that sends the ticket URL how you want it to, but we need to tell EE to actually use it.

Edit your Event (this years event) and scroll down to the bottom, were you have ‘Notifications’, click the Email tab and you’ll see the Reg Approved message template – http://take.ms/HSMiy

Select you custom Reg Approved there (which is why we used a descriptive name above, if you have multiple custom messages all with the same name you can’t select the correct one) – http://take.ms/ivKxM

Now update the event.

NOTE: At this point if anyone new users register onto the event, they will receive that registration approved message type. Be sure to switch it back to the previous template when finished, unless you always want to include the ticket link in that message.

Now go to the registrations for that event (Event Espresso -> Events -> {Hover over event} -> Registrations – http://take.ms/KyCw2

Select your test registrations – http://take.ms/hm7tr

Now use the ‘Bulk options’ at the top of the list and select ‘Approve and Notify Registrations’ – http://take.ms/YlUna

Then click apply.

Take note that that option will Approve your registrations if you select registrations that are not approved, so be careful which registrations you select. EE will then loop over each registration and send out the Reg Approved emails. Both the single ticket registration and group registration will receive a single email.

Here’s mine (all of those registrations used the same email, so they both go to the same inbox in this example) – http://take.ms/0vl5I

Here is the content of the MultiReg email – http://take.ms/Xd1fk

Clicking the link shows this – http://take.ms/CZoVA
(There’s 4 tickets listed there but only 2 on the screenshot)

The single registration link shows just a single ticket – http://take.ms/v46Mg

Will that work?

All of the above instructions make sense? If not please let me know and I’ll try to clarify.