Support

December 2, 2015 at 9:54 am

Hi Jake,

With the newsletter message type you can create the template within the admin using the full WYSIWIG editor if you prefer, you could then just select the users to send the email to, select the custom template and then hit send.

So then you don’t need to use the front end editor, you’d just use the admin and then select your template through the front.

For example you can go to Event Espresso -> Messages.

Find the news letter message type and click ‘Create Custom’ – http://take.ms/EUKVm

Then add all of the details you need within the custom message template – http://take.ms/7ZMq9

You can either add them all to main content as above, or just add them all within the [NEWSLETTER_CONTENT] editor and it will parse within the message.

The [NEWSLETTER_CONTENT] shortcode is what is display in the form editor when sending, you could remove that completely and just use the admin editor and add your custom details to the main content if you prefer.

Basically you would be shifting all of your newsletter editing into the admin and just selecting the custom template when sending, would that work?

December 4, 2015 at 4:42 am

I do agree that in this use case the full editor would make this much easier, I have created a feature request ticket for this here:

https://trello.com/c/WNWvopcI/108-add-the-full-wysiwyg-editor-to-the-newsletter-message-type-model

Please feel free to add any additional comments to that ticket and add a vote for the feature there.

Also we often receive feedback regarding the newsletter message type in that most users would prefer the ability to send the newsletter message using specific events details and so request the ability to use Event based shortcodes within the newsletter, as you are currently using the newsletter for its intended purpose, I would be interested if you have any further feedback regarding the below…

Currently the newsletter is ‘contact’ based, in that it pulls all of the contacts assigned to the registrations you have selected and sends the message to those contacts. This means that at the time of sending the newsletter does not know what ‘event’ this is for or event what registration it is for (and so you need to manually add all additional data). This also means that if you select multiple registrations that are assigned to a single contact (say 1 user registers onto 4 events and you select all 4 of those registrations) the newsletter will only send a single message, because its all just one contact for those registrations.

Now to allow use to use event shortcodes we would need to change it to be a registrations based messenger, meaning when you select multiple registrations the messenger loops through each individual registration, builds out the message and sends. (basically the newsletter would become very similar to the registration approved message type with the shortcodes available).

This change effectively means that in the example I gave above, all 4 of those registrations selected for the same user would send an individual message, but all 4 of those message will parse shortcodes to be specific for the event they have registered onto, so for example you can use [EVENT_NAME] within the newsletter message type and it will parse to the event they register onto.

This is a significant change we are proposing but should allow users greater flexibility for their messages, as you currently use the newsletter it would be great if you could provide any feedback as to how this may effect yourselves as we may end up adding an additional message type for the above, leaving the newsletter as is if it will cause users problems.