Eventixa Shortcodes
Eventixa provides shortcodes for displaying event listings, venues, organizers, ticket selection, checkout, booking details, customer accounts, waitlists, and frontend attendee check-in.
Shortcodes are useful when you want to place Eventixa functionality inside a normal WordPress page, post, template, page builder, or another shortcode-compatible content area.
Core Shortcodes: Events, Venues, Organizers, Tickets, Checkout, Booking Details, My Account
Pro Shortcodes: Waitlist and Check-In
Admin Reference: Eventixa → Shortcodes
What Are Eventixa Shortcodes?
A shortcode is a small WordPress code enclosed in square brackets.
For example: [eventixa_events]
When WordPress processes the page, Eventixa replaces the shortcode with the corresponding frontend interface.
This lets you add Eventixa functionality without writing PHP templates.
Where to Find Eventixa Shortcodes
Go to: Eventixa → Shortcodes
The Shortcodes screen provides a reference for Eventixa shortcode usage.
Depending on the shortcode, the admin reference can include:
- Shortcode name
- Description
- Usage example
- Supported parameters
- Parameter details
- Copy action
You can copy a shortcode and paste it into a WordPress page or another shortcode-compatible area.
Available Eventixa Shortcodes
The current Eventixa runtime includes these shortcodes:
| Shortcode | Feature | Availability |
|---|---|---|
[eventixa_events] | Event listings and event views | Core |
[eventixa_venues] | Venue listing | Core |
[eventixa_organizers] | Organizer listing | Core |
[eventixa_tickets] | Event ticket selector | Core |
[eventixa_checkout] | Eventixa checkout | Core |
[eventixa_booking_details] | Customer booking details | Core |
[eventixa_my_account] | Eventixa customer account | Core |
[eventixa_waitlist] | Event waitlist registration | Pro |
[eventixa_checkin] | Frontend attendee check-in | Pro |
Event Listings Shortcode
Use: [eventixa_events] to display Eventixa events.
This is the main Eventixa listing shortcode and supports configurable event views, pagination, filtering, search, sorting, and taxonomy filtering.
A basic example is: [eventixa_events]
A more customized example can specify parameters such as:
[eventixa_events view="list" limit="12" filter="true" pagination="true"]
The Events shortcode is covered in detail in the Events Shortcode documentation.
Event Views
Eventixa Core provides these Events shortcode views:
- List
- Calendar
- Day
Eventixa Pro extends the same Events shortcode with:
- Grid
- Map
Grid and Map are additional views of [eventixa_events]; they are not separate shortcodes.
Events Shortcode Parameters
The current Events shortcode supports:
viewsviewlimitcategoryvenueorganizerfilterpaginationsearch_barsort
These parameters let you create different event-listing pages without duplicating the Eventixa event data itself.
Venues Shortcode
Use:
[eventixa_venues]
to display Eventixa venues.
This is useful when you want a dedicated frontend page where visitors can browse the venues associated with your Eventixa events.
Organizers Shortcode
Use:
[eventixa_organizers]
to display Eventixa organizers.
You can place it on a dedicated Organizers page or another suitable part of your website.
Tickets Shortcode
Use: [eventixa_tickets] to display the standard Eventixa ticket selector for an event.
The shortcode accepts an optional event_id.
For example: [eventixa_tickets event_id="123"]
If event_id is not provided, Eventixa uses the current post ID.
Tickets Shortcode on an Event Page
When used in the context of an Eventixa event, you can normally use: [eventixa_tickets] without manually entering an event ID.
Eventixa resolves the current event automatically.
Tickets Shortcode on Another Page
If you want to show tickets for a specific event somewhere else, provide its event ID: [eventixa_tickets event_id="123"]
Replace 123 with the Eventixa event ID.
Standard Tickets and RSVP
The [eventixa_tickets] shortcode renders Eventixa’s standard commerce ticket selector.
RSVP registration uses Eventixa’s RSVP workflow rather than being rendered as a normal commerce ticket form by this shortcode.
Recurring Event Tickets
When [eventixa_tickets] is used for a recurring event, Eventixa resolves the relevant occurrence from the frontend request.
If an occurrence is not explicitly requested, Eventixa can resolve the next suitable occurrence.
This helps the ticket form remain occurrence-aware on recurring event pages.
Checkout Shortcode
Use: [eventixa_checkout] to render the Eventixa checkout interface.
The shortcode does not require public shortcode parameters.
Eventixa Checkout Page
The Checkout shortcode is normally placed on the Eventixa Checkout page managed by Eventixa.
You generally do not need to create a separate checkout shortcode configuration for every event.
Eventixa sends the active checkout session into the shared Checkout page.
Do Not Add Event IDs to Checkout
The Checkout shortcode does not use an event_id shortcode parameter.
The checkout workflow is determined by the active Eventixa booking/session information rather than by a manually entered event ID.
Booking Details Shortcode
Use: [eventixa_booking_details] to display the customer-facing Eventixa booking details interface.
This shortcode also does not require public shortcode parameters.
Booking Details Page
Eventixa normally uses the Booking Details shortcode on its dedicated booking-details page.
Customers can reach this page after a booking or through supported secure booking/account workflows.
Secure Booking Details
Booking details are not selected by adding a public booking ID directly to the shortcode.
Eventixa uses its normal booking access workflow to determine which booking should be displayed.
This protects customer booking information from being exposed through simple predictable shortcode parameters.
My Account Shortcode
Use: [eventixa_my_account] to display the Eventixa frontend customer account.
The My Account interface includes customer-facing areas such as:
- Dashboard
- Bookings
- Waitlists where available
- Profile Details
- Change Password
Customers can use this account experience to review Eventixa activity without accessing the WordPress admin dashboard.
My Account Requires Authentication
The customer account is designed around the current logged-in WordPress user.
A logged-in customer sees account information associated with that account.
For complete account behavior, see the Eventixa My Account documentation.
Waitlist Shortcode
Eventixa Pro provides: [eventixa_waitlist] when the Waitlist feature is enabled.
The shortcode supports:
event_idticket_idoccurrence_id
This lets the waitlist form target a specific event, ticket, and recurring occurrence.
Basic Waitlist Example
A basic event-context example is: [eventixa_waitlist]
When used on an event-related page, Eventixa can resolve the current event context.
Waitlist for a Specific Event
You can explicitly specify an event: [eventixa_waitlist event_id="123"]
Waitlist for a Specific Ticket
To target a specific event ticket: [eventixa_waitlist event_id="123" ticket_id="456"]
Waitlist for a Recurring Occurrence
For an occurrence-specific waitlist, the shortcode can also receive an occurrence ID.
The waitlist workflow then uses Eventixa’s normal ticket availability and occurrence eligibility rules.
Waitlist Shortcode Availability
The Waitlist shortcode is registered only when the Eventixa Pro Waitlist feature is enabled.
If the feature is disabled, the waitlist shortcode is not available as an active frontend Eventixa feature.
Guest Waitlist Registration
Whether a guest visitor can use the waitlist depends on the global Eventixa Waitlist settings.
If guest waitlist registration is disabled, the visitor must log in before joining.
Check-In Shortcode
Eventixa Pro provides:
[eventixa_checkin]
This renders the frontend Eventixa attendee check-in application.
The shortcode itself does not require public parameters.
Check-In Interface
The Check-In shortcode can provide the complete Eventixa frontend check-in workflow, including supported:
- Camera QR scanning
- USB scanner input
- Manual Ticket ID lookup
Available methods depend on your Eventixa check-in configuration.
Check-In Requires Login
The Check-In interface is not a public attendee page.
The user must be logged in and have permission to use Eventixa frontend check-in.
If the current user does not have permission, Eventixa does not provide unrestricted scanner access.
QR Check-In Must Be Enabled
The Eventixa QR Check-In feature must be enabled for the frontend check-in interface to operate.
Camera Scanning and HTTPS
Browser camera access generally requires HTTPS.
Localhost environments are an exception supported by modern browsers for development/testing.
On a live website, use SSL/HTTPS before relying on camera-based QR scanning.
Manual Ticket Lookup
The Check-In interface can support manual Ticket ID lookup.
If manual lookup has been disabled in Eventixa settings, the manual input and Search action are not available for use.
Shortcode Availability by Plan
Eventixa Core provides the main display and customer workflow shortcodes.
These include:
[eventixa_events]
[eventixa_venues]
[eventixa_organizers]
[eventixa_tickets]
[eventixa_checkout]
[eventixa_booking_details]
[eventixa_my_account]
Eventixa Pro adds:
[eventixa_waitlist]
[eventixa_checkin]
Shortcodes and Gutenberg Blocks
Eventixa also provides Gutenberg blocks for several of the same frontend experiences.
The current Core blocks include:
- Events
- Venues
- Organizers
- Single Event
- Event Tickets
- My Account
Eventixa Pro adds the Check-In block.
Not Every Shortcode Has a Gutenberg Block
Some Eventixa shortcodes currently do not have a dedicated Gutenberg block.
These include:
- Checkout
- Booking Details
- Waitlist
You can still insert them using WordPress’s standard Shortcode block.
Shortcodes and Elementor
When Elementor is installed and active, Eventixa also registers Elementor widgets using the same shared frontend component architecture.
This helps Eventixa keep shortcode, Gutenberg, and Elementor output consistent instead of maintaining separate versions of the same frontend feature.
Shared Event Display Architecture
Eventixa reuses its frontend renderers across supported display methods.
For example, the Events shortcode, Events Gutenberg block, and Events Elementor widget use the same underlying event-listing system.
This means you can choose the integration method that best fits your site without creating a separate set of Eventixa event data.
When to Use a Shortcode
Shortcodes are particularly useful when:
- Using the Classic Editor
- Using a page builder with shortcode support
- Adding Eventixa to a theme template area
- Creating a dedicated Eventixa system page
- Embedding functionality inside existing content
- Using a feature that does not have a dedicated block
When to Use a Gutenberg Block
Use an Eventixa Gutenberg block when you want visual controls inside the WordPress Block Editor.
For example, the Events block lets you configure listing options without manually writing shortcode attributes.
When to Use Elementor
Use the Eventixa Elementor widgets when your site is designed with Elementor and you want Eventixa controls directly inside the Elementor editor.
Do Not Add the Same Feature Twice
Avoid placing a shortcode and its equivalent Eventixa block or Elementor widget on the same page unless you intentionally want the feature rendered twice.
For example, placing both: [eventixa_events] and the Eventixa Events block on the same page creates two event listings.
Page Manager and System Shortcodes
Eventixa manages several important frontend pages that use shortcodes internally.
The standard page system includes pages for:
- Events
- Venues
- Organizers
- My Account
- Checkout
- Booking Details
These pages can be created or repaired through Eventixa’s page-management workflow where applicable.
Do Not Remove System Shortcodes Accidentally
If you edit an Eventixa system page, do not remove its required shortcode unless you intentionally want to replace the page’s Eventixa functionality.
For example, removing [eventixa_checkout] from the configured Checkout page prevents that page from rendering the normal Eventixa checkout interface.
Copy Shortcodes from Eventixa Admin
The Eventixa → Shortcodes screen provides a convenient reference and copy workflow for commonly documented shortcodes.
Use this screen when you need to quickly copy shortcode syntax into WordPress content.
Runtime Shortcodes vs Admin Reference
The actual Eventixa runtime currently includes some shortcodes that may not appear in the Shortcodes admin reference table.
In particular, the current runtime also supports: [eventixa_tickets] and, when Eventixa Pro Waitlist is enabled: [eventixa_waitlist]
These are valid Eventixa shortcodes even if they are not currently shown in the same admin reference list.
Adding a Shortcode with Gutenberg
To add an Eventixa shortcode in the Block Editor:
- Edit the WordPress page.
- Add a Shortcode block.
- Paste the Eventixa shortcode.
- Configure any supported parameters.
- Update or publish the page.
- View the page on the frontend.
Adding a Shortcode with the Classic Editor
Paste the shortcode directly into the page content.
For example: [eventixa_events]
WordPress processes the shortcode when the page is displayed.
Adding a Shortcode with Elementor
Elementor supports WordPress shortcodes through its Shortcode widget.
However, when Eventixa already provides a dedicated Elementor widget for the same feature, using the native Eventixa Elementor widget generally gives you easier visual controls.
Multiple Event Listings
You can use [eventixa_events] more than once across your site with different parameters.
For example, one page can display one category while another page displays another category.
Each shortcode instance can have its own configuration.
Example: Basic Events Page
Use: [eventixa_events] for a normal Eventixa event listing using the configured defaults.
Example: Limited Events Listing
Use: [eventixa_events limit="6"] to limit the Eventixa events displayed per page for that shortcode instance.
Example: List View
Use: [eventixa_events view="list"] to request List as the initial view.
Example: Category-Specific Events
The Events shortcode supports the category parameter for filtering the listing by Eventixa category IDs.
The detailed syntax and combination rules are covered in the Events Shortcode documentation.
Search Bar Parameter Is Broader Than Search
The Events shortcode includes a search_bar parameter.
Despite its name, this setting controls the broader event-listing toolbar rather than only the text search input.
The toolbar can include functionality such as:
- Search
- View switching
- Filters
- Sorting
- Active filter chips
- Result count
This distinction is important when configuring a simplified events listing.
Shortcode Output Looks Different from the Event Page
Some shortcodes intentionally render a specific Eventixa component rather than an entire event page.
For example: [eventixa_tickets] renders the ticket selector, while an Eventixa single-event page contains additional event content and event components.
Shortcode Shows Nothing
If a shortcode produces no visible output, check whether its required data exists.
For example, [eventixa_tickets] requires an event with standard tickets that can be rendered in the current context.
A shortcode returning no form does not necessarily mean WordPress failed to process it.
Shortcode Appears as Plain Text
If visitors see the literal shortcode, such as: [eventixa_events] instead of Eventixa output, check:
- Eventixa is active.
- The shortcode spelling is correct.
- The shortcode was placed in an area that processes WordPress shortcodes.
- A page builder is not escaping shortcode text.
- Site/page cache has been cleared after changes.
Pro Shortcode Does Not Work
For a Pro shortcode, confirm:
- Eventixa Pro is active.
- The required feature is enabled.
- The current user meets any access requirements.
- The shortcode is being rendered in a valid context.
For [eventixa_waitlist], the Waitlist feature must be enabled.
For [eventixa_checkin], the user must be logged in and authorized for check-in.
Checkout Shortcode Shows No Checkout
The Checkout page depends on an active Eventixa checkout workflow.
Opening the page directly without valid checkout/session information may not produce the same result as reaching it through event ticket selection.
Booking Details Shortcode Shows No Booking
The Booking Details page depends on Eventixa’s secure booking-access workflow.
You should not expect a random direct page visit to expose another customer’s booking.
Tickets Shortcode Shows No Tickets
Check:
- Correct
event_id - Standard tickets exist for the event
- Ticket configuration is valid
- Recurring occurrence context is valid where applicable
Remember that the standard Tickets shortcode is not the separate RSVP registration renderer.
My Account Shows No Customer Data
Confirm the visitor is logged into the correct WordPress account and that the account has Eventixa activity associated with it.
Recommended Shortcode Practices
Use the following approach when working with Eventixa shortcodes:
- Use the exact registered shortcode name.
- Add only supported parameters.
- Use event IDs rather than slugs where the parameter expects an ID.
- Keep system shortcodes on their configured Eventixa pages.
- Test the page on the frontend after changing shortcode parameters.
- Test desktop and mobile layouts.
- Verify logged-in behavior for My Account and Check-In.
- Verify recurring occurrence context where relevant.
- Avoid duplicating an equivalent shortcode and block/widget on the same page.
- Clear caching after changing system pages.
Common Questions
What Is the Main Eventixa Events Shortcode?
Use:
[eventixa_events]
What Shortcode Displays Event Tickets?
Use:
[eventixa_tickets]
You can optionally pass an event_id.
What Shortcode Displays Eventixa Checkout?
Use:
[eventixa_checkout]
What Shortcode Displays Booking Details?
Use:
[eventixa_booking_details]
What Shortcode Displays Eventixa My Account?
Use:
[eventixa_my_account]
What Shortcode Displays Venues?
Use:
[eventixa_venues]
What Shortcode Displays Organizers?
Use:
[eventixa_organizers]
Does Eventixa Have a Waitlist Shortcode?
Yes. Eventixa Pro provides:
[eventixa_waitlist]
when Waitlist is enabled.
Does Eventixa Have a Check-In Shortcode?
Yes. Eventixa Pro provides:
[eventixa_checkin]
Can I Use Shortcodes in Gutenberg?
Yes. Use WordPress’s standard Shortcode block, or use a dedicated Eventixa block when one exists.
Can I Use Eventixa Shortcodes with Elementor?
Yes. Elementor’s Shortcode widget can process them. Eventixa also provides dedicated Elementor widgets for several major Eventixa components.
Does Every Shortcode Have a Gutenberg Block?
No. Checkout, Booking Details, and Waitlist currently do not have dedicated Eventixa Gutenberg blocks.
Are Grid and Map Separate Shortcodes?
No. Eventixa Pro adds Grid and Map as views of [eventixa_events].
Can I Use Several Events Shortcodes?
Yes. Different shortcode instances can use different parameters and filters.
Why Is [eventixa_tickets] Not on My Shortcodes Admin Screen?
The current Eventixa runtime registers [eventixa_tickets] even though the admin Shortcodes reference does not currently list it.
Why Is [eventixa_waitlist] Not Always Available?
The shortcode is provided by Eventixa Pro and registered when the Waitlist feature is enabled.
Important Notes
- Eventixa Core provides seven runtime shortcodes: Events, Venues, Organizers, Tickets, Checkout, Booking Details, and My Account.
- Eventixa Pro adds Waitlist and Check-In.
- Waitlist is registered when the Waitlist feature is enabled.
- Check-In requires an authenticated, authorized user.
[eventixa_events]is the primary configurable event-listing shortcode.- Eventixa Pro extends
[eventixa_events]with Grid and Map views. [eventixa_tickets]supports an optionalevent_id.- Checkout and Booking Details do not expose public shortcode parameters.
[eventixa_waitlist]supports event, ticket, and occurrence targeting.[eventixa_checkin]renders the complete frontend check-in workflow.- Shortcodes, Gutenberg blocks, and Elementor widgets reuse Eventixa frontend rendering wherever possible.
- Some valid runtime shortcodes are not currently listed on the Eventixa Shortcodes admin reference page.
