Notifications templates

Notification Templates lets an administrator change the subject and content of JEM emails without editing language files. Use named variables such as {user_name} and {event_title} to insert the actual information.

JEM 5.1.0: This article describes the completed template editor, including notifications for new and edited events and venues. Earlier beta packages may not include all these templates.

1. Open the template editor

  1. In Joomla administration, open Components → JEM.
  2. From the JEM Control Panel, open Notifications.
  3. Use the Templates tab and select a language.
  4. Filter by workflow and recipient to find the message you want to change.
  5. Open the template to edit its subject, plain-text body and optional HTML body.

The administrator needs the JEM permission to manage notification templates. The entry is also subject to the features available in the selected JEM operating profile.

Sending emails still depends on Joomla mail settings and the JEM Mailer plugin. Open System → Manage → Plugins, find the JEM Mailer plugin and check which notifications and recipients are enabled. Editing a template does not enable a notification or send an email.

2. Choose the correct message

WorkflowWhen it is used
Registration confirmation A registration is confirmed.
Waiting-list confirmation A registration is placed on the waiting list.
Waiting-list movement A registration moves between waiting and confirmed attendance.
Attendance status A supported attendance response or status is recorded.
Invitation An invitation notification is generated.
Registration cancellation A registration is cancelled.
Scheduled reminder A configured reminder becomes due.
Event submission and changes An event is created or edited.
Venue submission and changes A venue is created or edited.

Check the Recipient and Variant before editing. A user message and an administrator message are separate templates. Registrations can also have variants for actions on behalf of another person and messages with a comment. Event and venue notifications have New item and Edited item variants.

Who is “User”? For a registration, this is the booking holder. For an event or venue submission, it is the user performing the action. Notifications to creators, attendees and other configured recipients continue to follow the Mailer recipient settings.

3. Edit, preview and save

  1. Enter the Subject. It must be a single line and may contain variables.
  2. Write the required Plain-text body.
  3. Optionally write an HTML body for formatted emails.
  4. Select the field where you want to insert a variable, place the cursor and click the variable in the help panel.
  5. Use Preview with example data to check the content. Refresh the preview after changes.
  6. Select Apply to save and continue editing, or Save to save and return.

The preview uses example data. It does not send a message or show a particular user's booking. Test the relevant action on a test site to check the final message and recipient settings.

The Mailer plugin's HTML setting controls the delivered format. If HTML mail is enabled, JEM uses the custom HTML body when one is provided, with the plain-text body as its alternative. If there is no custom HTML body, JEM safely converts the plain text to HTML. With HTML mail disabled, it sends the plain-text body.

Changing a template does not rewrite an email that was already generated. A queued reservation notification or retry can retain its saved content. Use a new test action to check a changed template.

4. Use named variables

Keep the braces and spelling exactly as shown. You may move a variable, repeat it or omit information you do not need. The help panel lists the variables available for the selected template; not every variable is available in every workflow.

VariableMeaning
{user_name} The booking holder in registration messages; the submitting or editing user in event and venue messages.
{actor_name} The person performing the action, where supplied by the workflow.
{event_title}, {event_date}, {event_time} The event name and formatted start date and time.
{venue}, {city} The venue name and city, when the event has a venue.
{places} The number of places supplied by the registration workflow.
{event_description} The event description as plain text.
{event_url} A link to the event.
{action_date} The creation or modification date in event and venue submission messages.
{publication_status} The publication message and, where applicable, its link. Event messages also include lifecycle status and permitted online meeting information.
{venue_url} The JEM venue page.
{venue_website} The external website entered in the venue's Website field.
{street}, {postal_code}, {country} Address fields in venue submission messages. Country is the stored country code.
{venue_description} The venue description as plain text.
{event_image_url}, {venue_image_url} The public image URL when the corresponding image exists. An unavailable image produces an empty value.
{site_name} The Joomla site name.

New custom templates use named variables, not %s placeholders. JEM can still read and convert older positional translations for compatibility.

Unknown variables and invalid syntax are rejected when saving. Omitting a recommended variable produces a warning, allowing the administrator to decide whether it is appropriate. Subject and plain-text body cannot be empty.

Variable values are escaped when inserted into HTML. A description variable does not execute HTML or scripts from an event. The template editor is not a PHP or conditional-template editor.

For an online event without a venue, omit the venue line if it is not useful. A missing value becomes empty; JEM does not automatically remove surrounding text such as “Venue:”. A template applies to its workflow and language, rather than to one individual event.

5. Languages and updates

Custom templates are saved separately for each language. Editing English does not change Spanish or German. The editor requires an active Joomla content language and the corresponding JEM Mailer language files. A language without those files is unavailable for editing.

JEM selects the recipient's configured language when a matching Mailer language package is available. Otherwise, it falls back to the site's default language and then English. For a missing default translation key, JEM also checks its fallback languages.

A saved custom template is used for that template and language. If none exists, JEM uses the translated default. Custom templates survive JEM updates; they are not automatically rewritten when the default wording changes.

To remove a custom template, open it in the correct language and select Restore Default. Confirm the action. This removes only that template's customisation for the selected language; other templates and languages remain unchanged.

If a previously stored custom template cannot be rendered, JEM attempts to use the translated default and records a warning. Correct the custom template before relying on it again.

6. Shared footer and privacy disclaimer

Use the Footer and Privacy disclaimer tabs for text shared by notification templates. These sections have their own language-specific customisations and settings for user and administrator messages.

Shared content is added after the message body when enabled. Avoid repeating the same footer in every individual template. Use the variables offered in these sections, such as {site_name}, {site_url}, {contact_email} and {privacy_url}.

JEM may also add workflow information, such as why a configured recipient receives a message or details of an assigned venue configuration. Changing the template does not change permissions, booking rules, recipient selection, reminders or payment status.

7. Examples

Example 1: A short registration confirmation without a venue

Choose Registration confirmation → User and the relevant variant. This can suit an online workshop.

Subject

Your booking for {event_title}

Plain-text body

Hello {user_name},

Your booking for {event_title} is confirmed.
Date: {event_date}
Time: {event_time}
Places: {places}

Event details: {event_url}

For Ana's booking of two places, JEM inserts Ana's name, the event details and the value 2. There is no empty “Venue:” line. Remember that this template also applies to other registrations using the same variant and language.

Example 2: A newly submitted event awaiting publication

Choose Event submission and changes → User → New item.

Subject

We received your event: {event_title}

Plain-text body

Hello {user_name},

We received your event on {action_date}.
Title: {event_title}
Date: {event_date}, {event_time}

{publication_status}

If the event is unpublished, the publication message reflects that state. The template does not publish the event or promise that a visitor can already access it. Keeping {publication_status} helps avoid misleading confirmations.

Example 3: Tell administrators that a venue was edited

Choose Venue submission and changes → Administrator and configured recipients → Edited item.

Subject

Venue updated: {venue}

Plain-text body

{user_name} updated {venue} on {action_date}.

Address: {street}, {postal_code}, {city}, {country}
Venue website: {venue_website}
JEM venue page: {venue_url}

{publication_status}

Here, {user_name} identifies the editor, not the administrator receiving the message. JEM still sends only to the recipients enabled in the Mailer settings.

Example 4: Add a formatted HTML version

Keep the plain-text body and add the following HTML to an event registration template. Use the HTML editor's source mode when pasting HTML.

<h2>{event_title}</h2>
<p>Hello {user_name}, your booking is confirmed.</p>
<p><strong>Date:</strong> {event_date} at {event_time}</p>
<p><strong>Places:</strong> {places}</p>
<p><a href="/{event_url}">View event details</a></p>

Enable HTML email in the Mailer plugin to use this version. The plain-text body remains available as the alternative.

8. Check your changes

  1. Use a test site and email addresses you control.
  2. Confirm that the Mailer notification and its recipients are enabled.
  3. Make a new registration or create/edit a test event or venue, matching the selected template.
  4. Check the recipient, subject, names, dates, links and publication wording.
  5. Check plain text and HTML when both formats are used.
  6. Repeat for another recipient language if the site is multilingual.
  7. Check an event without a venue or image if those cases are used on your site.

If the old wording still appears, check the language, recipient and variant first. Also check whether you are looking at an already-generated message. The notification history covers supported reservation workflows; it is not a complete record of every event or venue submission email.