Use this screen to create a new event or edit an existing event in the JEM backend. An event can contain its own schedule, venue, categories, registration rules, images, attachments, links, display settings and metadata. It can also be part of a regular recurrence or an irregular series built from custom dates.
Tip: Most display fields offer a Use Global option. Choose it to inherit the JEM configuration, or select another value to override that setting for this event.
Navigation
In the Joomla administrator, select Components → JEM → Events, then select New. To edit an event, select its title in the Events list.
Toolbar
| Button | Description |
| Save |
Saves the event and keeps the edit screen open. |
| Save & Close |
Saves the event and returns to the Events list. |
| Save & New |
Saves the event and opens a new, empty event form. |
| Save as Copy |
Creates an independent copy. Clear the Alias before saving if JEM should generate a new alias from the title. A copied occurrence is detached from its original series. |
| Close |
Leaves the form without saving unsaved changes. |
Screen layout
The form is divided into main tabs and side panels. The fields available to an administrator can also depend on JEM configuration and Joomla permissions.
| Area | Contents |
| Main tabs |
Event, Advanced, Attachments, Links and Event Settings. |
| Side panels |
Publishing, Custom Fields, Registration, Image, Repeating Events and Metadata. |
Event tab
| Option | Description |
| Title |
The event name. This field is required. |
| Alias |
The URL-safe name used by Joomla routing. Leave it empty to generate it from the title. |
| Start Date / End Date |
The civil dates of the event. Leave End Date empty for a one-day event. The input format follows the active Joomla language; for example, English (United Kingdom) normally uses YYYY-MM-DD, while English (United States) uses MM-DD-YYYY. |
| Start Time / End Time |
The event times. An event may be saved without times when only the date is relevant. |
| Event time reference |
Select Joomla timezone, Venue timezone or Custom event timezone. Venue timezone requires a venue with a configured timezone. |
| Event timezone |
Select the IANA timezone used by the event when Custom event timezone is selected. |
| Categories |
Select one or more JEM categories. At least one category is required. A default category may already be selected by the JEM configuration. |
| Venue |
Select the event location. A default venue may be supplied by the configuration. A venue is optional. |
| Type |
Select the event type, when event types are configured. |
| Contact |
Select a Joomla contact to display with the event. |
| Featured |
Marks the event as featured so layouts and modules can highlight it. |
| Associated Article Usage |
Select None, use the Joomla article as Additional information, or use it as the event's main Content. |
| Associated Article |
Select an existing Joomla article. Depending on the configured action and permissions, JEM can also create an article when the event is saved or use an automatic category mapping. |
| Description |
The main event text, entered with the configured Joomla editor. Its use depends on the Associated Article Usage selection. |
Date input format and active Joomla language
JEM uses Joomla's locale-aware calendar field for Start Date, End Date and the recurrence end date. The format shown and accepted by these fields is therefore supplied by the active Joomla language, rather than by a separate JEM date-input setting.
| Context | Language setting used | Typical format |
| JEM backend |
The active Joomla Administrator language. A language selected in the administrator's user profile can override the default Administrator language. |
en-GB: YYYY-MM-DD
en-US: MM-DD-YYYY |
| Frontend event submission |
The active Joomla Site language, including any applicable user language preference. |
Depends on the installed and active Site language. |
| Database storage |
Not configurable. Joomla validates the local input and JEM stores the normalized date internally. |
YYYY-MM-DD |
For a United States date-entry workflow, install English (United States) - en-US and select it as the Administrator language. Also check the editing user's profile because its Backend Language selection can take precedence over the default. If users create or edit events from the frontend, install and enable en-US for the Site client as well.
Example: With en-US active, enter 9 August 2026 as 08-09-2026. Joomla validates that local value and JEM normalizes it to 2026-08-09 for internal storage. Recurrences, sorting and date comparisons therefore continue to use an unambiguous value.
Do not edit the JEM form XML only to change the date format. The fields use Joomla's translated calendar format, so an XML format value is replaced by the active language. Local source edits would also need to cover the backend and frontend forms and would be overwritten by a JEM update.
If installing the appropriate language is not suitable, Joomla Language Overrides can change DATE_FORMAT_CALENDAR_DATE and DATE_FORMAT_FILTER_DATE. Both values must describe the same format. Such overrides are global for the selected Site or Administrator client and affect other Joomla calendar fields, not only JEM. See Language Overrides.
Advanced tab
| Option | Values and purpose |
| Access |
The Joomla viewing access level required to see the event. |
| Joomla publication status |
Published, Unpublished, Archived or Trashed. This controls whether the item is published in Joomla. |
| Event status |
Scheduled, Cancelled, Postponed, Rescheduled or Moved online. This describes the real-world status and does not replace the Joomla publication status. |
| Availability |
Available / In stock, Preorder or Sold out. This can be displayed to visitors and used in structured event data. |
| Online Meeting URL |
The URL used to join an online or hybrid event. |
| Online Meeting Label |
Optional link text such as Join the webinar. If it is empty, the layout uses its default label. |
| Start Publishing / Finish Publishing |
Optional Joomla publication window. These timestamps control content visibility; they are separate from the event's date, time and timezone. |
Attachments tab
Upload documents that visitors may download from the event page. Allowed extensions and maximum upload size are controlled by the JEM and server configuration.
| Option | Description |
| Display attachments as |
Use Global, row, full-width row, uniform row, column, full-width column or uniform column. |
| Show file icon |
Use Global, no icon, normal, medium or large icon. |
| Show as button/frame |
Displays the attachment link with or without button/frame styling. |
| Attachment fields |
For each file, set its display name, description, published status, access level and order. Existing attachments can be reordered or removed. |
Links tab
Add reusable event-related links, for example a booking page, livestream, programme or external organizer page.
| Option | Description |
| Display links as |
Row, full-width row, uniform row, column, full-width column or uniform column. |
| Links order |
Choose the order of image, icon and text within each link. |
| Link fields |
Set label, description, icon/type, colour, URL, target (current or new tab), button/frame style and an optional image with maximum width and height. |
| Ordering |
Add, remove and move links to control their display order. |
Event Settings tab
These options override the global JEM display configuration for this event.
Event display
| Option | Description |
| Event details layout |
Use Global, details or compact. |
| Venue and category |
Show or hide the venue name and category, and choose whether the category is linked. |
| Author and contact |
Show or hide the author and contact, link them when applicable, and show or hide the contact category and description. |
| Status information |
Show or hide hits, publication state and availability. |
| Actions |
Show or hide Print, Email and iCal actions. |
| Event content |
Show or hide the event title and event description. |
Venue display
| Option | Description |
| Venue layout |
Use Global, details or compact. |
| Venue description / address |
Show or hide the venue description and postal address. |
| Venue link |
No link, link to the venue URL, or link to the JEM venue view. |
| Map service |
Use Global, no map, Google Maps link, embedded Google map, Google Maps API, OpenStreetMap link or embedded OpenStreetMap map. |
| Google options |
For Google map modes, the Google top-level domain and language can also be selected. |
Registration display
| Option | Description |
| Community solution |
Use Global, none or Community Builder. |
| Integration |
Link the attendee name to the profile, or display both the profile link and avatar. |
Publishing panel
This panel contains record information such as ID, creator, hits, creation date, modification date and version. Most values are generated or updated by Joomla. Administrators with the required permission can change the creator.
Custom Fields panel
Complete any custom fields enabled for events. JEM supports up to ten event custom fields; their labels, order, type and visibility are configured centrally in JEM Settings. Empty fields are normally not displayed on the event page.
Registration panel
| Option | Description |
| Event Registration |
No, Yes, or From a specified opening date. |
| Registration opens / closes |
Optional limits for the period in which visitors can register. |
| Allow cancellation |
No, Yes, or allow cancellations only until a specified date. |
| Invited users only |
Restricts registration to invited users when invitations are enabled globally. |
| Maximum places |
Total capacity. A value of 0 means unlimited capacity. |
| Minimum / maximum booked places per user |
Controls how many places one registration may request. |
| Reserved places |
Keeps part of the capacity unavailable to normal online registration. |
| Waiting list |
Allows registrations to join a waiting list when normal capacity is full. |
| Request answer |
Requests an explicit attendance response from eligible users. |
| Series event booking |
Allows registration for this occurrence and eligible occurrences in the same series. |
| Single event booking |
Allows registration for this occurrence only. |
| Available places |
A read-only value calculated from capacity, reservations and current bookings. |
Image panel
| Option | Description |
| Intro image |
The event image used by list and summary layouts. |
| Full event image |
The larger image used in the event detail view. |
| Full image layout |
Use Global, right, header, poster or hidden. |
Repeating Events panel
Choose how JEM creates additional event occurrences. A regular recurrence uses a rule; Custom dates creates a finite irregular series from an explicit schedule.
| Repeat type | Use |
| None |
The event does not repeat. |
| Daily |
Repeats after a selected number of days. |
| Weekly |
Repeats after a selected number of weeks. |
| Monthly |
Repeats on a selected monthly interval. |
| Weekday |
Repeats using a weekday-based monthly rule. |
| Yearly |
Repeats after a selected number of years. |
| Last day |
Repeats on the last day of the relevant month. |
| Custom dates |
Creates an irregular series from the exact dates and times entered in the schedule table. |
Regular recurrence types also use a recurrence end date and the configured generation anticipation window. The anticipation value controls how far ahead JEM creates occurrences; it does not change the recurrence rule itself.
Custom dates: irregular event series
Use Custom dates when occurrences do not follow a daily, weekly, monthly or yearly rule. The event's main Start Date and Start Time define the first occurrence. Each row under Custom dates adds another normal JEM event, while all occurrences remain connected as one series.
Create a custom-date series
- Complete the event's shared information, categories, venue, registration options and other settings.
- Open Repeating Events and select Custom dates.
- Use the main event fields to enter the first occurrence's start date and, when required, its start time, end date and end time.
- Enter at least one later occurrence in Custom dates. Select Add another date for each further occurrence.
- Save the event. JEM sorts valid rows chronologically and creates the series.
Schedule fields and validation
| Rule | Behaviour |
| Minimum and maximum |
A custom series requires the main event plus at least one additional occurrence. It accepts up to 249 additional rows, for a maximum of 250 occurrences. |
| Empty rows |
Completely empty rows are ignored. |
| Dates and times |
Invalid values are rejected. If an end is supplied, it cannot be earlier than the start. |
| Duplicates |
Two occurrences cannot have the same effective schedule. |
| Ordering |
When creating a series, every additional occurrence must start after the main event. Occurrences are stored in chronological order. |
| Timezone |
Every row uses the event's selected Joomla, venue or custom timezone. JEM normalizes each occurrence independently, including daylight-saving transitions. |
Edit an existing custom series
Custom-date series follow the same parent/child editing model as regular recurrences. When editing an occurrence, its date and time remain in the main event fields and the table lists the other occurrences.
| Event being edited | What changes | Schedule access |
| First event (series root) |
Supported shared fields and categories, including the title, description and venue, are automatically propagated to the other occurrences. Dates, publication state, registrations and attendees remain occurrence-specific. |
The other occurrences can be rescheduled and new dates can be added. |
| Any later occurrence (child) |
Only the event currently open is changed. This allows an exceptional description, venue, capacity, status or time without affecting the series. |
The series schedule is read-only. Edit the first event to update the complete series. |
Important: Removing a stored row from the schedule does not silently delete that occurrence. Cancel, unpublish, trash or delete the occurrence through the normal event workflow. This protects registrations and occurrence-specific changes.
Registration and lifecycle behaviour
- Each occurrence has its own publication state, event status, capacity, attendee list and waiting list.
- Creating or updating a series never copies attendees or registrations to another occurrence.
- Series booking can include the current and eligible future occurrences, while single-event booking affects only the selected occurrence.
- Save as Copy creates an independent event and removes the copied item from the original series relationship.
- If an occurrence is permanently deleted, JEM repairs the series root and ordering. If only one event remains, it becomes a normal standalone event.
Technical implementation notes
Custom-date occurrences are stored as ordinary JEM event records, so existing event views, modules, plugins, permissions and registration workflows continue to operate on each occurrence. The records are linked by series_id and ordered by series_order. Custom dates is an editor workflow rather than a stored recurrence rule: generated occurrences use recurrence_type = 0. Their UTC start values are calculated individually and stored in start_utc, which keeps chronological and future-occurrence operations reliable across different timezones and daylight-saving changes.
Metadata panel
| Option | Description |
| Meta Keywords |
Optional search metadata. JEM provides placeholders including [title], [a_name], [categories], [dates], [times], [enddates] and [endtimes]. |
| Meta Description |
A concise description for search engines and integrations. |
| Robots |
Use Global, index/follow, noindex/follow, index/nofollow or noindex/nofollow. |
| Author / Rights |
Optional metadata identifying the content author and usage rights. |
Practical examples
Example 1: a single workshop
Create the event with one Start Date, select its category and venue, and leave Repeating Events set to None. Enable registration and set Maximum places to 20 if attendance is limited.
Example 2: a class every Tuesday
Create the first class, choose Weekly, select the required weekly interval and set the recurrence end date. Use this method because the schedule follows a predictable rule.
Example 3: an irregular three-session course
Set the main event date to 10 October 2026 at 10:00–13:00. Then select Custom dates and add these two later occurrences:
| Start date | Start time | End date | End time |
| 24 October 2026 |
10:00 |
24 October 2026 |
13:00 |
| 15 November 2026 |
16:00 |
15 November 2026 |
19:00 |
JEM creates three connected events. If the November session later moves to another venue, edit that child occurrence; only it will change. If a fourth course date is announced, edit the first/root event and add the new row.
Example 4: a hybrid event in another timezone
Select Custom event timezone, choose the event's actual timezone, enter the online meeting URL and set Event status to Moved online when appropriate. Visitors and integrations can then receive a consistent event instant even when the Joomla site uses another timezone.
Example 5: entering dates in United States format
Install and select English (United States) - en-US as the Administrator language. The Start Date and End Date fields then accept MM-DD-YYYY, such as 10-24-2026. The event is still stored internally as 2026-10-24; the change affects the editing format, not the event's civil date or timezone.
Troubleshooting
| Symptom | Check |
| The event cannot be saved. |
Confirm that Title and at least one Category are present, then review highlighted date, time, access and permission errors. |
| A custom series is rejected. |
Complete the main event date and add at least one unique later occurrence. Verify that no end occurs before its start. |
| The displayed time is unexpected. |
Check Event time reference, the venue timezone and the selected custom timezone. Publication dates are a separate visibility setting. |
| The date field uses an unfamiliar format. |
Check the active Joomla language and the editing user's language preference. Use en-US for MM-DD-YYYY. If language overrides are used, verify both DATE_FORMAT_CALENDAR_DATE and DATE_FORMAT_FILTER_DATE for the correct Site or Administrator client. |
| A series-wide edit would overwrite a special occurrence. |
Edit the exceptional child occurrence when the change must remain individual. Edit the first/root event only when supported shared fields should be propagated to the complete series. |
| An attachment cannot be uploaded. |
Check the allowed file extensions, JEM upload limit, PHP upload limit and the user's upload permissions. |
Related Project Notes