Support

August 28, 2015 at 12:03 pm

Hi there,

It looks as though I have to write an email to them each time? That isn’t right is it?

No, you should not need to do that.

However to note that the batch emails use the ‘Newsletter’ message type, so you need to create a custom Newsletter message.

Which message template have you used to create your current custom ‘reminder’ message?

August 28, 2015 at 1:09 pm

Hey there,

If you look on the right sidebar, you will see which shortcodes can be used where.

Does that help?

August 31, 2015 at 3:55 am

Hi,

You can currently include event_meta within the EVENT_LIST section of messages using [EVENT_META*{meta_key}] (where {meta_key} is the meta key).

September 2, 2015 at 8:06 am

The reason you can not use the Event based shortcodes within the Newsletter message type is because that message type is used to send messages based on the ‘contacts’ for the registrations, so the newsletter messenger doesn’t know what event those shortcodes would be for, only the contact.

Its not that we’ve placed restrictions based on which message you are sending, but rather the messengers are to be used in different contexts so only have access to specific information. Therefore the shortcodes for info the messenger doesn’t have are unavailable.

So currently to provide all of the details needed for this event you would need to create a custom newsletter template, which contains all of the data you want sent to the attendee (without using shortcodes)

We have a feature request ticket for an event reminder type email, I’ve added this thread to the vote.

Depending on exactly what information you need to send to the attendee it’s also possible to use a custom registration approved message type (which will allow for shortcodes)

However to use that you will need to build the custom template, set that template to be the message approved template for the event, select the registrations to send the message to force EE to ‘resend’ (although its actually sending a new message) the message template, then set the registation approved message template back to the default within the event (otherwise any new registrations will receive the custom template)

The above can only work if all of the registrations you want to send the message to are either already ‘Approved’ and can have the status changed to Approved.

It depends on exactly what data you need to include as to whether or not that would work, but may be a better option than creating a complete message for the newsletter type?

September 2, 2015 at 8:58 am

As more and more people started to use EE3 and more features were included it became very apparent that the flaws in how it sent emails (and when/how those were triggered) was becoming a bigger problem and needed to change.

With that the messages system was introduced within EE4 with one of the requirements being that the user had ability to enabled/disable all of the message types individually. Its one of the reasons the messages system seems so complicated, because it has so many use cases it fits into…

However we do recognise that we need to work on the messages system to improve usability and this does highlight the need for an additional message type that can be used as a sort of event reminder email, which allows the use of the event shortcodes.

The message system is very complicated. I understand you are trying to offer maximum options, but it doesn’t seem to do that as we can’t actually define when and to whom the messages are sent.

You actually have more control over which messages (and to whom) are sent within EE4 than EE3, although they are different messages and work differently than EE3.

I can try your solution above, but does that mean it will also send the same message upon each approved registration? That’s not really ideal and doesn’t solve the need for a ‘follow up’ email either.

I’m not sure what you mean here? The registration approved message allows you to use shortcodes within the message, so it will dynamically alter the content for each registration if you are using the shortcodes.

September 2, 2015 at 12:33 pm

What I mean is that by using your work around, the user will receive the same message upon registration as they would when I ‘force’ it to resend. Which isn’t want I want.

No, they would receive the custom template that you create and set as the Registration Approved message at the time of forcing the resend. So although your basically telling EE to resend the Registration Approved message, at that point the registration approved message is your custom message template.

Once you’ve sent the batch email, change the event back to use the standard registration email template.

Its essentially the same as you are requesting, however in this case your using a default template for something it isn’t intended for, it should work but requires more work.

Here’s an example of how I would do it.

Go to Event Espresso -> Messages.

Click to ‘Create Custom’ on the Registration Approved template – http://take.ms/ovrfP

Provide a name and a description – http://take.ms/lr9Lr

Then make sure you are working on the context that will be sent to the Registrant – http://take.ms/QUaNJ

Any changes made here will only be saved to the custom template and if in the context above, sent to the user who registered.

I’ll add ‘CUSTOM TEMPLATE’ to the message content – http://take.ms/W6MKc

Save the template when ready.

(One change you will need to make is to switch to the ‘Event Admin’ context and remove the ‘TO’ field – http://take.ms/B0a5u this is to prevent multiple event admin emails being resent)

Now we have the custom template, but we are not using it.

Go to the event you want to send this template for, edit the event and within the event editor under notifications you’ll see this – http://take.ms/Qqiu1

So we are using the default ‘global’ template. If I register onto the event at that point, that is the message that is triggered (the standard message).

Now In the ‘Registration Approved’ message dropdown select your new template you’ve just created – http://take.ms/nNabQ

Update the event.

Now at THAT point, if any user registers onto the event they will receive the custom template.

So now we view the registrations for that event.

Event Espresso -> Events -> *However over the event* -> Click the registrations link for that event – http://take.ms/vQ9AG

So I only have 2 registration on this event – http://take.ms/nMNNc

Notice both are Approved! Its important as we’ll be selecting to Approve and Notify the registrants. As they are already approved it doesn’t make any difference and just notifies them.

So I select both registrations – http://take.ms/MjDwn

Then within the bulk options, select ‘Approve and notify registrants’ – http://take.ms/NtNDs

Then click Apply – http://take.ms/sXrHT

At this point Event Espresso is going to loop over EVERY selected registration, set it to approved and then trigger the registration approved message template that is currently selected for the event.

You will want to do this in batches so script doesn’t time out, about 20-30 at a time.

Once finished, edit the event again, in the notifications section set the Reg Approved message template back to Global and then save.

Once again from this point any new registrations receive the standard template.

Here are the messages I just got from that test – http://take.ms/TeHvX

Notice the ‘CUSTOM TEMPLATE’ I added in the template is in those message I just triggered.

That all make sense and sound like it will suit your purpose?

It is best to test this on a test registration first, just to make sure its working as expected before you select the bulk of the registrations.

Can I customize the message on a per event basis? I don’t think so at the moment.

You can create as many custom templates as needed and amend.

Would perhaps simply an ‘event email’ template that is managed in a similar way to the newsletter option not cover almost any scenario that a user could have (of course including all possible short codes)? Then we would have all the flexibility needed to create whatever messages are required.

This is what I’m referring to above. It’s essentially a copy of the registration approved message but with no automatic ‘triggers’ although the developers may come up with a better idea to implement this.