The Events Calendar Settings Overview

You can access the settings for The Events Calendar by heading to Events → Settings from your site admin bar or sidebar. The settings offer a lot of cool options to get your calendar looking just the way you want it.

General

  • Show The Events Calendar link: You will notice this in the large box at the top of this page. It adds a small link to the bottom of your calendar pointing to The Events Calendar project.
  • Number of events to show per page: Defines the number of events showing on each page. This applies to most list-style views: List, Photo, Map, Venue, and Organizer views. Other events are accessible from Previous/Next Events nav links. Note that this does not apply to Day View, which always shows all events on that day regardless.
  • Recurring event instances: When checked only the next upcoming event in a recurring event sequence will show. This can be useful to unclutter your calendar. When unchecked, all instances will show.
  • Front-end recurring event instances toggle: Gives a bit more flexibility than the Recurring event instances setting covered above. When enabled, this offers a frontend setting for users to decide whether they want to show an entire recurrence pattern or just the next event in that series.
  • Clean up recurring events after: Use this setting to decrease clutter in your backend events list. Recurring events older than the inputted months will be deleted.
  • Create recurring events in advance: This setting controls how far in advance recurring events instances are made. For example, you could have your recurring events made 12 months in advance, so users would always see 12 upcoming instances on your calendar.
  • Activate Block Editor for Events: When enabled, the Gutenberg Block Editor will be active on the edit screen for events pages.
  • Show Comments: this feature is not available with your BBWP site.
  • Show Custom Fields metabox:This option allows you to show or hide the default “Custom Fields” meta box when editing events within your dashboard. If you aren’t already familiar with using this feature, you can go ahead and disable it. This will help to clean up the dashboard when creating events.
  • Include events in main blog loop: Events will be included where a Posts feed may be displayed. They will continue to show in all calendar views. We don’t recommend you enable this option.
  • Events URL slug: Determines where on the frontend your events will live; defaults to /events but can be changed to whatever you see fit. The link that appears below the field will take you directly to your events page.
  • Single event URL slug: Similar to the Events URL slug, this determines the URL structure for a single event. Note that while you want this to be similar to the Events URL slug, they cannot be identical — notice how if the Events URL slug defaults to plural “events”, the Single Event URL Slug has to be singular “event.” Keep this in mind as you make changes.
  • End of day cutoff: Let’s say you have an event that runs from 6 pm on Friday until 2 am on Saturday; technically, that’s a Friday & Saturday event — but to readers on the frontend, and for all intents & purposes, it’s a Friday night event that runs long. This is where the end of day cutoff comes into play; if you set the dropdown here to 2:30 a.m., for example, your Friday-Saturday event would only show on Friday in relevant views.
  • Default currency symbol: This allows non-US users to change the currency symbol for Event Cost. The symbol can also be changed on an individual post.
  • Currency symbol follows value: Users with a default currency that follows the amount (for example 10 zł) can check this box to have the currency symbol show after the money value.
  • Duplicate Venues & Organizers: You might find duplicate venues and organizers when updating The Events Calendar from an outdated version. This option allows you to automatically merge identical venues and organizers. This option should not be necessary with BBWP.
  • Move to trash events older than: This option allows you to automatically move past events to trash based on their end date.
  • Permanently delete events older than: This option allows you to bulk delete past events based on their end date. Be careful and backup your database before removing your events as there is no way to reverse the changes.

Map Settings

  • Enable Google Maps: This checkbox allows Google Maps integration for single event pages and venue pages. You can then turn maps on or off on individual event pages.
  • Map view search distance limit: This sets the distance for the Location search. For example, if set at 20, a Location search for New York City will show all events within 20 miles (or km, depending on the setting below) of New York City.
  • Map view distance unit: Allows you to change the default distance unit to kilometers instead of miles.
  • Google maps default zoom level: Defines how the map looks on Venue and Event pages. A low number will show a zoomed-out map, while a high number (max 21) will be completely zoomed in.

Miscellaneous Settings

  • View Welcome Page: Takes you to the welcome page that shows when you initially install The Events Calendar.
  • View Update Page: Takes you to the page that shows when you update The Events Calendar.

Timezone Settings

If you’ve upgraded from an earlier version you’ll want to click the Update Timezone Data button.

Screenshot showing the timezone data update tool

You will then have access to two timezone options:

  • Timezone mode: Default option is to use the site’s timezone everywhere on the calendar. You can also choose to use local timezones for each event, which are configured on individual event pages.
  • Show timezone: Allows you to display the timezone code (e.g. PST or BST) next to event times on the front end.

Display

Basic Template Settings

  • Default stylesheet used for events templates: You can choose between three different stylesheets depending on how much default styling you want on your calendar.
    • Tribe Events Styles: our most comprehensive level of default styling
    • Skeleton Styles: this is a very minimal level of styling and is ideal for those who wish to roll their sleeves up and build their own custom set of rules
  • Events template: This dropdown allows you to change the look and feel of the calendar and how it integrates with your site. The plugin comes with two templating options by default (Default Events Template and Default Page Template); your theme will likely include at least one more. Switch between these if you’re finding the calendar does not look as you want it to on the site — while they may not get you 100% where you want to be, you’ll be able to tell right off the bat which templating option is most compatible with your site and can make additional modifications as needed from there.
  • Enable event views: Allows you to choose which Views will be available to users on the front end.
  • Default view: The View selected here will show on your calendar’s initial load. From there users can change to the Views you’ve enabled above.
  • Default mobile view: When Events Calendar Pro is activated, the view selected here will show on your calendar’s initial load when on mobile devices. If you do not specify a view here, it will use the value of the above “Default view” option.
  • Disable the Event Search Bar: Check this box to return to the classic header from previous versions.
  • Hide location search: Removes the Location Search option from the Tribe Bar.
  • Hide related events: Removes the Related Events from the bottom of the single event page.
  • Month View events per day: Controls the number of events listed on each day in Month View. If there are additional events on that day there will be a link to view all events on that day.
  • Hide weekends on Week View: Allows you to show only Monday through Friday on Week View. Other enabled views will not be affected.
  • Enable Month View Cache: This setting caches your Month View so that it loads faster for users.

Date Format Settings

  • Date with year: the format you specify here will be used when showing an event from a past or future year (such as on single event pages and list-style views) and for dates in view headers.
  • Date without year: the format here will be used when showing an event from the current year, such as on the single event pages and list-style views.
  • Month and year format: this format will be used when displaying a date that is just the month and year, such as in the Month View header.
  • Week day format: the format you specify here will be used for the top row of the Week View.
  • Date time separator: this settings allows you to change the symbol or word that displays between the date and time of an event (for example January 1 @ 9:00 am).
  • Time range separator: this setting allows you to change the symbol or word that displays between the start and end time of an event (for example 9:00-10:30am).
  • Datepicker date format: the date format you choose here will show everywhere there is a datepicker on the front and backend of your site. This includes on the Add New Event page and in the Event Bar.

Advanced Template Settings

  • Add HTML Before/After Calendar: These fields allow you to add extra divs (or other HTML) before or after the calendar as it appears on the frontend of the site. You can also use shortcodes here. This can also come in handy for adding sub-heads or announcements to your calendar.

Default Content

Default Venues and Organizers are available with the Events Calendar. Learn more about using this page in the Related Article.

Additional Fields

This is where you add custom event attributes. We thoroughly cover this section of settings in our guide to Additional Fields.

Filters

See the Related Article for more information on configuring the Filter Bar.

APIs

The Events Calendar comes with one API field, for Google Maps. While many sites work fine without a Google Maps API key, other sites–particularly those with high traffic or multiple map features–need to have a key in order to properly render maps. For best results, we recommend getting a Google Maps API key and entering it in the available field.