Skip to content
Tickets Please

General Settings

General Settings

Your event calendar’s baseline behavior starts here. The General Settings panel controls how many events appear on archive pages, which calendar view loads first, and whether visitors can submit their own events.

Navigate to Events > Settings > General in your WordPress admin to access these options.

Events Per Page

The Events per page field sets the number of events shown on list and archive pages before pagination kicks in. The default is 10. Set this to any positive integer that fits your layout — sites with image-heavy event cards often work better at 6 or 8.

This value applies to all front-end event listings. Individual shortcodes and blocks can override it with their own per_page attribute.

Default Calendar View

The Default view dropdown determines which calendar layout visitors see when they land on your main events page. Options are:

  • List — A chronological list of upcoming events. Best for sites with fewer than 20 events per month.
  • Month — A traditional calendar grid. Works well when events are spread across dates.
  • Day — A single-day agenda view. Useful for venues that host multiple events daily.

Visitors can switch between views using the navigation bar. This setting only controls the initial load.

Show Past Events

When Show past events is checked, event archive pages include events whose end date has already passed. The default is No (unchecked).

Enabling this is useful for organizations that want a searchable event history. Past events appear after all upcoming events in list view, sorted by most recent first.

Community Events

Two settings control community-submitted events:

  1. Enable community events — When checked, logged-in users see a front-end event submission form. Default is No.
  2. Community event approval — When checked, community-submitted events start in pending status and require an administrator or editor to publish them. Default is Yes. Uncheck this only if you fully trust all registered users to publish events without review.

Community events respect the same validation rules as admin-created events. Required fields (title, start date) are enforced on the front-end form.

How Settings Are Stored

All General Settings are stored in the tickets_please_settings serialized array in the WordPress wp_options table. You can access them programmatically:

$settings = get_option( 'tickets_please_settings', array() );
$per_page = isset( $settings['events_per_page'] ) ? (int) $settings['events_per_page'] : 10;

Changing settings takes effect immediately on the next page load. No cache flush is required.

Common Questions

Can I set different events-per-page values for different views? Not from the settings panel. Use the pre_get_posts hook to modify the query for specific view types.

Does “Show past events” affect the REST API? No. The REST API returns events based on the parameters you pass. The setting only applies to front-end archive pages.

What happens if I disable community events after users have submitted some? Existing community-submitted events remain in whatever status they had (published, pending, or draft). Only the submission form is removed.

Can I limit which user roles can submit community events? Community event submission requires the edit_tribe_events capability. By default, Contributors and above have this. Adjust role capabilities to restrict further.

Where is the main events page URL configured? Tickets Please uses the tribe_events post type archive. The URL slug is set under Events > Settings or via the tickets_please_event_rewrite_slug filter (default: event).

Next Steps

  • Display Settings — Customize date formats, maps, templates, and related events.
  • Payment Settings — Set up Stripe, PayPal, or WooCommerce for paid tickets.
  • Import & Export — Bulk-load events, venues, and organizers from CSV files.