Skip to content

Display Settings

Display Settings

Events need to look right for your audience. The Display Settings panel controls date formatting, map embeds, template styles, and whether related events appear below your event content.

Navigate to Events > Settings > Display to configure these options.

Date and Time Formats

Two fields control how dates and times render across your event pages:

  • Date format — A PHP date format string. Default: F j, Y (e.g., “January 15, 2026”). Common alternatives: m/d/Y for US numeric, d/m/Y for international, Y-m-d for ISO.
  • Time format — A PHP time format string. Default: g:i A (e.g., “2:30 PM”). Use H:i for 24-hour format.

These formats apply to all front-end event displays including list view, single event pages, and calendar tooltips. Admin screens use WordPress core date settings from Settings > General.

For a full list of PHP date format characters, see the PHP date documentation.

Map Settings

Two settings control venue map embeds on single event pages:

  • Show map on venue — When checked (default: Yes), a map embed appears on single event pages that have a linked venue with address data.
  • Map provider — Choose between Google Maps and None. Google Maps requires an API key configured in Integration Settings.

When the map provider is set to None, no map renders regardless of the “Show map on venue” checkbox. This is useful if you want to display venue addresses as text without a visual map.

Events Template

The Events template setting controls the overall styling approach for your event pages. Select from available template styles to match your theme’s design language.

Template files can be overridden in your theme. Copy any template from wp-content/plugins/tickets-please/templates/ to wp-content/themes/your-theme/tickets-please/ and modify it. The plugin checks your theme directory first.

Use the tickets_please_template_path filter to point to a completely custom template directory:

add_filter( 'tickets_please_template_path', function ( $path ) {
return get_stylesheet_directory() . '/my-custom-events/';
} );

Three settings control the related events section that appears below single event content:

  • Show related events — Checkbox, default Yes. Displays a grid of related events at the bottom of single event pages.
  • Related events count — Number of related events to show. Default: 3. Set between 1 and 6 for best layout results.

Related events are matched by shared categories and tags, with preference given to upcoming events.

Override the visibility or count programmatically:

// Disable related events on specific events.
add_filter( 'tickets_please_show_related_events', function ( $show ) {
if ( get_the_ID() === 42 ) {
return false;
}
return $show;
} );
// Show 6 related events instead of the default.
add_filter( 'tickets_please_related_events_count', function ( $count ) {
return 6;
} );

Both filters run at display time, so changes take effect immediately without clearing caches.

Common Questions

Do date format changes affect existing events? No. Date formats only change how stored dates are displayed. The underlying _tribe_event_start_date and _tribe_event_end_date meta values remain in Y-m-d H:i:s format.

Can I use different date formats on list view versus single event pages? Not from the settings panel. Use the tickets_please_frontend_event_details filter to modify the HTML output for specific views.

Why does the map not show even though “Show map on venue” is enabled? Check that your venue has a full address and that a valid Google Maps API key is entered in Integration Settings. The map requires both a provider and geocoded coordinates.

Do related events respect event visibility settings? Yes. Events marked as hidden from listings (_tribe_event_hide_from_listings) do not appear in the related events section.

Can I style the related events grid with CSS? Yes. Related events render inside a container with predictable class names. Override styles in your theme’s stylesheet.

Does the template override work with child themes? Yes. The plugin checks the child theme directory first, then the parent theme, then falls back to the plugin’s own templates.

Next Steps