GigRoute Events

GigRoute Events is a WordPress event management plugin built for bands, musicians, artists, stand-up performers, show business teams, venues, and entertainment websites that need a clean way to publish upcoming shows and guide visitors toward tickets. The plugin adds a dedicated Event post type, event details, ticket URLs, location taxonomies, event statuses, posters, frontend filters, and a dynamic Gutenberg block for displaying tour dates and live events anywhere on your site. Whether you manage a band website, a comedy tour page, an artist profile, a festival landing page, or a promotional website for live shows, GigRoute Events helps you keep event information structured, searchable, and easy to promote. Built for ticket promotion GigRoute Events helps visitors move from event discovery to ticket action. Each event can include a Ticket URL, venue information, date and time, city, state, country, event type, status, and an optional poster image. This makes it easier to build pages such as:

• Upcoming tour dates
• Concert schedules
• Stand-up show calendars
• Festival appearances
• Artist event listings
• Venue and city-based event pages
• Ticket-focused landing pages

The frontend block can show a clear "Buy tickets" link for each event and automatically switch to a sold-out label when an event is marked as sold out. Key features

• Custom Event post type with title, editor, excerpt, and featured image support.
• Event date and time fields with local timezone handling and stored UTC values.
• Ticket URL and external event source URL fields.
• Venue name, latitude, longitude, and related post ID fields.
• Event Type, Event Status, City, State, Country, and Tour Series taxonomies.
• Default Event Type and Event Status management.
• ISO 3166-1 alpha-2 country code support for event countries.
• Gutenberg block for displaying event lists on pages and posts.
• Upcoming, past, and all-events display modes.
• Optional frontend filters by event type, country, city, status, and series.
• Optional pagination for event lists.
• Configurable event date output formats with localized editor previews.
• Optional ticket links in frontend event lists.
• Sold-out and free-event metadata.
• Event poster image support.
• Optional global poster for all events.
• Optional poster link wrapping for ticket or promotional links.
• Recurring event templates with one-time manual generation of recurring event posts.
• Recurring event controls for active, paused, and ended series states.
• Admin recurrence filters for single events, recurring event templates, generated recurring events, and modified generated events, shown only when matching posts exist.
• Generated event overrides for ticket links, ticket price, venue, status, and indexing behavior.
• REST JSON endpoint for public event data.
• Optional Schema.org Event/MusicEvent JSON-LD for public, indexable event pages.
• Schema.org admin fields for venue address, performer, organizer, ticket offer, attendance mode, and event status.
• Registered event meta fields with REST support and revision-aware storage where appropriate.
• Shared datetime meta synchronization for classic editor, REST saves, Visual Revisions fallback paths, and Pro imports.
• REST response caching with cache headers and debug information for administrators.
• SEO controls for hiding individual event pages and preventing indexing.
• Optional /events/ archive disable mode with a 301 redirect to a selected published page.
• Compatible event editing UI for both the block editor and classic editor, without duplicate meta storage.
• Classic theme template fallback for single event and archive templates.

Recurring events GigRoute Events 2.1.0 improves recurring event wording and supports recurring event templates for repeated shows, club nights, weekly performances, annual events, residencies, and other schedules where the same event repeats over time. A parent recurring event stores the shared details and recurrence rule. Editors can generate dated recurring event posts with a one-time checkbox on update, so a normal save only stores recurrence settings and does not accidentally create or update event posts. Generated recurring events keep frontend lists, AJAX filters, REST requests, pagination, and Schema.org data working with normal event posts instead of calculating virtual dates on every request. Each sync is capped to protect the database from accidental daily schedules that span too far into the future. Administrators can pause a recurring series to stop creating new generated events, resume it later, or end it and choose whether future generated events should be kept, cancelled, drafted, or moved to the trash. The Events admin list includes a recurrence filter and visual markers: recurring event templates are marked with a crown and generated recurring events have their own indicator. Individual generated events show a direct link back to the parent event and can be detached when a specific date needs its own ticket link, ticket price, venue, status, or other event-specific data. Gutenberg block The GigRoute Events block lets editors display events without writing code. Block options include title, title tag, layout styling, number of events, event mode, ticket link visibility, grouping, pagination, filters, and date format. This is useful for building conversion-focused sections such as "Tour Dates", "Upcoming Shows", "Live Events", "Get Tickets", or "Next Performances". Event posters GigRoute Events includes poster functionality for visually promoting events. You can use individual event posters or one global poster across the site. Poster settings include:

• Enable or disable posters globally.
• Use individual event posters or one global poster.
• Set the poster display delay.
• Hide the poster for a selected number of days after a visitor closes it.
• Wrap poster media in a link when a valid destination is available.
• Use the global poster link or the individual event Ticket URL as the destination.

This can help promote ticket campaigns, new tour announcements, stand-up specials, festival appearances, or other show business events. REST API GigRoute Events provides a public JSON endpoint: /wp-json/gigroute-events/v1/events The endpoint returns published events and supports event discovery, external frontends, mobile apps, landing pages, and custom JavaScript interfaces. Supported query examples: /wp-json/gigroute-events/v1/events /wp-json/gigroute-events/v1/events?mode=upcoming /wp-json/gigroute-events/v1/events?mode=all&year=2026 /wp-json/gigroute-events/v1/events?mode=all&year=2026&month=4 /wp-json/gigroute-events/v1/events?country=ukraine&city=kyiv&event_type=concert /wp-json/gigroute-events/v1/events?start=2026-04-01&end=2026-04-30 /wp-json/gigroute-events/v1/events?mode=all&page=2&per_page=20 The response includes pagination data and event items. Empty values are removed from public event responses where possible. Event edit meta is registered for REST access, so block editor saves, revisions, integrations, and the classic editor all continue to work with the same underlying post meta keys instead of duplicated values. SEO and marketing benefits GigRoute Events helps structure event content in a way that supports marketing and organic discovery. You can create dedicated content around live shows, city pages, tour schedules, artist announcements, and ticket calls to action. The plugin separates event metadata from normal post content, which makes it easier to reuse event information across blocks, templates, REST responses, filters, and promotional sections. For SEO-focused event pages, you can use event titles, excerpts, content, featured images, event taxonomies, and location terms to create relevant pages around concerts, tours, stand-up shows, and entertainment events. For events that should appear in lists but should not have a public single page, GigRoute Events includes event visibility controls. You can hide the direct event page and prevent search indexing while still keeping the event available in public lists and REST summaries when published.

2.1.0

• Added automatic single-event and archive templates for block themes while preserving Site Editor and active-theme overrides.
• Corrected classic-theme template priority so standard single-gigroute_event.php and archive-gigroute_event.php files are never overwritten by the bundled fallback.
• Reworked bundled PHP templates with theme-neutral markup and ensured archive block styles load before classic themes print their header.
• Removed an archive poster class collision with the full-screen promotional poster component.
• Fixed classic-theme Playwright setup escaping and aligned archive assertions with the block's default accessible markup.
• Hardened public AJAX filtering with request-size, result-limit, and page-number guards.
• Sanitized AJAX-rendered event markup in the browser and limited URL history updates to the current site origin.
• Standardized the frontend ticket call to action as "Buy tickets".
• Confirmed compatibility with the WordPress React JSX runtime and Block API v3 used by React 19-enabled WordPress installations.
• Improved recurring event wording in the admin UI and documentation: generated dates are now described as generated recurring events instead of the technical term occurrences where this is clearer for editors.

2.0.0

• Added recurring event templates with generated recurring event posts for daily, weekly, monthly, and yearly schedules.
• Added recurring series controls for Active, Paused, and Ended states, with actions for future generated events.
• Simplified the recurring event admin UI so weekly-only weekday controls and advanced generation options are shown contextually.
• Added a generation guard so generated event posts are not created until the parent event has the required title, date/time, timezone, country, and city data.
• Added generated event inheritance and override support so generated dates can reuse parent fields while still allowing custom ticket URLs, ticket prices, venues, statuses, and indexing flags.
• Updated event queries so recurring event templates are excluded from public lists while generated recurring events work with AJAX filters, pagination, REST responses, posters, and Schema.org data.
• Hardened generated event inheritance for parent fields, posters, Schema.org Event Data, previousStartDate, ticket price, and ticket links.
• Improved the Events admin recurrence filter so generated, parent, and modified generated event options are shown only when matching posts exist.

1.3.0

• Added an optional /events/ archive disable mode with a 301 redirect to a selected published page.
• Switched archive redirect settings from a stored URL to a stored page ID for safer domain, protocol, and permalink changes.
• Added the gigroute_events_archive_redirect_url filter for multilingual redirect targets.
• Improved classic theme template lookup for standard archive-gigroute_event.php and single-gigroute_event.php overrides.

1.2.2

• Moved performer Schema.org values to global settings so they can be reused across event pages.
• Expanded event schema type options to include additional Schema.org Event subtypes while keeping MusicEvent as the default.
• Locked venue city, country, and country code to values resolved from assigned taxonomies and country code term meta.
• Removed per-event Schema.org enable toggle; JSON-LD now outputs automatically only when the generated event schema is valid and the event is public/indexable.
• Improved the Schema.org validation modal with a working clipboard fallback and direct Schema.org Validator link.

1.2.1

• Fixed Schema.org Event Data visibility when the event noindex checkbox is disabled in the editor.
• Added a resolved Schema.org values preview using existing event fields and assigned city/country taxonomies.

1.2.0

• Added global Schema.org structured data settings after the REST JSON API settings section.
• Added index-aware Schema.org event fields for Event and MusicEvent JSON-LD.
• Added a Schema.org validation preview modal with copyable JSON-LD for editors.
• Added venue address, performer, organizer, ticket offer, attendance mode, and event status fields for richer event markup.
• Normalized comma-based latitude and longitude values before saving and schema output.

1.1.0

• Fixed an incorrect release

1.0.3

• Added a dedicated datetime meta synchronization service for local/UTC/date helper fields.
• Reused the same datetime sync path for classic metabox saves and REST-based editor saves.
• Prepared Pro integrations to call the shared datetime sync service instead of duplicating derived date logic.
• Added tests.

1.0.2

• Improved registered event meta schema for REST, editor, and revision-aware workflows.
• Added REST-save synchronization for derived event datetime fields such as UTC start/end and local start date.
• Marked event editing meta boxes as block-editor compatible while keeping the same field placement for editors.
• Kept Classic Editor fallback behavior without duplicating event meta values.

1.0.1

• Fixed bugs.
• Added a button for finding geolocation coordinates in the Pro version.
• Added a button for auto-detecting time zones in the Pro version.

1.0.0

• Initial release.
• Added Event post type with event metadata.
• Added event taxonomies for type, status, city, state, country, and tour series.
• Added Gutenberg block for displaying event lists.
• Added ticket URL support.
• Added frontend event filters and pagination support.
• Added event poster and global poster settings.
• Added public REST JSON endpoint with caching.
• Added SEO controls for hidden event pages and indexing behavior.