Gutenberg Blocks
Eventixa provides native Gutenberg blocks for adding event listings, venues, organizers, single-event layouts, ticket forms, customer accounts, and frontend check-in directly from the WordPress Block Editor.
The Eventixa block system reuses the same frontend rendering architecture used by Eventixa shortcodes and Elementor widgets, so the displayed output remains consistent across supported display methods.
Core Blocks: Events, Venues, Organizers, Single Event, Event Tickets, My Account
Pro Block: Check-In
Block Category: Eventixa
What Are Eventixa Gutenberg Blocks?
Eventixa Gutenberg blocks are visual WordPress editor components that let you insert Eventixa functionality without manually writing shortcodes.
Instead of adding: [eventixa_events]
you can insert the Events block and configure its options directly from the Block Editor.
This is especially useful for users who prefer visual controls over shortcode parameters.
Where to Find Eventixa Blocks
Open a WordPress page or post in the Block Editor.
Click the block inserter and search for: Eventixa
The Eventixa block category contains the available Eventixa blocks for the current installation.
Available Eventixa Gutenberg Blocks
Eventixa Core currently provides six blocks:
- Events
- Venues
- Organizers
- Single Event
- Event Tickets
- My Account
Eventixa Pro adds:
- Check-In
Core vs Pro Blocks
The main display blocks are available in Eventixa Core.
Eventixa Pro extends the block system by adding the Check-In block and by adding extra event-listing views to the existing Events block.
The Pro Grid and Map views are not separate Gutenberg blocks.
They are additional view options inside the Events block.
Events Block
The Events block displays an Eventixa event listing.
It is the Gutenberg equivalent of the [eventixa_events] shortcode.
The block provides visual controls for configuring the listing directly in the editor.
Events Block Controls
The current Events block supports controls for:
- Default View
- Available Views
- Events per page
- Categories
- Venues
- Organizers
- Sort
- Show filters
- Show search
- Show pagination
These controls correspond to the same shared event-listing options used by Eventixa’s shortcode and Elementor implementations.
Default View
Use Default View to choose which event view opens first.
Eventixa Core supports:
- List
- Calendar
- Day
Eventixa Pro adds:
- Grid
- Map
Available Views
The Available Views control determines which view-switching options visitors can use on the frontend.
For example, you could make only:
- List
- Calendar
available even if other views exist on the site.
Core Event Views
Eventixa Core provides:
List — displays events in a traditional event-list layout.
Calendar — displays events in a calendar-based interface.
Day — focuses the listing around a selected day.
Eventixa Pro Event Views
Eventixa Pro extends the same Events block with:
Grid — displays events in a card-based grid.
Map — displays events using the Eventixa map-based listing experience.
These appear dynamically when the required Pro functionality is available.
Grid and Map Are Not Separate Blocks
You do not need to search for an Event Grid block or Event Map block.
Insert the normal Events block, then select Grid or Map from the available view controls when Eventixa Pro is active.
Events Per Page
Use Events per page to control how many events are displayed in one listing page.
This block-level value overrides the normal Events Per Page setting for that specific block instance.
Category Filtering
The Events block lets you restrict the listing to selected Eventixa categories.
This is useful for creating pages such as:
- Conferences
- Workshops
- Webinars
- Community Events
without creating separate event databases.
Venue Filtering
You can limit the block to events associated with selected Eventixa venues.
For example, a venue-specific landing page can display only events happening at that location.
Organizer Filtering
The block can also filter events by Eventixa organizers.
This is useful for organizer profile pages or partner-specific event pages.
Sort
The Events block includes a Sort control.
The shared Eventixa event-listing system supports sort choices such as:
- Upcoming
- Newest
- Oldest
- Title
The selected option determines the initial listing order.
Show Filters
Enable Show filters when you want visitors to use Eventixa’s interactive listing filters.
Disable it when you want a simpler fixed listing.
Show Search
Enable Show search to provide event search within the listing interface.
This is separate from the Block Editor’s own WordPress search functionality.
Show Pagination
Enable Show pagination when the event count can exceed the configured Events per page value.
Disable it for a fixed single-page listing.
Events Block Toolbar
The Events block uses Eventixa’s shared listing toolbar architecture.
Depending on the enabled options and views, the frontend can include:
- Search
- View switching
- Filters
- Sorting
- Active filter chips
- Result count
- Pagination
Events Block and Shortcode Consistency
The Events block and [eventixa_events] shortcode use the same Eventixa frontend rendering layer.
This means they are different configuration methods for the same event-listing system rather than unrelated implementations.
Venues Block
The Venues block displays the Eventixa venue directory.
It is the Gutenberg equivalent of:
[eventixa_venues]
Venues Block Controls
The current Venues block supports:
- Show search
- Items per page
- Show pagination
Show Venue Search
Enable Show search when visitors should be able to search the venue directory.
Venue Items per Page
Use Items per page to control how many venues appear before pagination.
Venue Pagination
Enable Show pagination when the venue directory contains more results than the configured items-per-page value.
Organizers Block
The Organizers block displays the Eventixa organizer directory.
It corresponds to:
[eventixa_organizers]
Organizers Block Controls
The Organizers block supports:
- Show search
- Items per page
- Show pagination
Its behavior intentionally mirrors the Venues block.
Organizer Search
Enable search when visitors should be able to find organizers directly from the frontend directory.
Single Event Block
The Single Event block displays the Eventixa single-event experience for a selected event.
This is useful when you want to embed one Eventixa event inside another WordPress page.
Select an Event
The Single Event block includes an Event selector.
Choose the Eventixa event you want the block to display.
The selected event is then rendered using Eventixa’s existing single-event frontend components.
Single Event Uses the Real Eventixa Layout
The block does not maintain a completely separate Gutenberg-only event template.
It reuses the Eventixa frontend single-event renderer.
This helps keep the embedded event consistent with Eventixa’s normal frontend event experience.
Single Event Block Use Cases
The Single Event block is useful when:
- Building a custom event landing page
- Embedding an event in a marketing page
- Featuring one event on a homepage
- Creating a custom page-builder-style layout with Gutenberg
No Event Selected
If no event is selected, the block cannot render a complete Eventixa event.
Choose an event from the block settings before publishing the page.
Event Tickets Block
The Event Tickets block displays Eventixa’s standard ticket selector for a selected event.
It corresponds to the runtime functionality of: [eventixa_tickets]
Select the Ticket Event
The block includes an Event selector.
Choose the Eventixa event whose tickets should be displayed.
Standard Tickets
The Event Tickets block renders the standard Eventixa commerce ticket selector.
RSVP uses Eventixa’s RSVP workflow rather than being treated as a normal standard ticket selector.
No Tickets Available
If the selected event does not contain renderable standard tickets, the Event Tickets block may not display a ticket form on the frontend.
Check the event’s ticket configuration if the block appears empty.
Recurring Event Tickets
For recurring events, Eventixa’s ticket-rendering layer resolves the appropriate occurrence context.
The block therefore uses the same underlying recurring-ticket behavior as the Eventixa ticket shortcode/frontend renderer.
My Account Block
The My Account block renders the Eventixa frontend customer account.
It corresponds to: [eventixa_my_account]
My Account Block Controls
The current My Account block does not require content-specific configuration controls.
Insert the block and Eventixa renders the customer account experience for the current user.
Customer Account Experience
The My Account block can provide access to areas such as:
- Dashboard
- Bookings
- Waitlists where available
- Profile Details
- Change Password
- Logout
The exact account content depends on the customer’s Eventixa data and enabled features.
My Account Requires the User Context
The My Account interface is designed for the current WordPress customer account.
It does not display one fixed account preview that applies to every visitor.
Check-In Block
Eventixa Pro provides the Check-In Gutenberg block.
This block renders Eventixa’s frontend attendee check-in interface.
It corresponds to: [eventixa_checkin]
Check-In Block Availability
The Check-In block requires Eventixa Pro.
The QR Check-In feature must also be enabled for the live frontend workflow.
Check-In Block Controls
The current Check-In block does not expose separate content controls.
It renders the shared Eventixa check-in application.
Check-In Methods
Depending on Eventixa settings, the frontend check-in application can support:
- Camera QR scanning
- USB scanner input
- Manual Ticket ID lookup
Check-In Requires Authentication
The Check-In block should not be treated as a public event-attendee block.
The current user must be logged in and have permission to use Eventixa frontend check-in.
Manual Lookup
Manual Ticket ID lookup depends on the corresponding Eventixa check-in setting.
If manual lookup is disabled, the manual input and search controls are unavailable.
Camera QR Scanning
Camera access normally requires HTTPS on production websites.
Localhost is generally permitted for development.
Use SSL on live sites before relying on browser camera scanning.
Blocks Not Currently Available
The current Eventixa source does not provide dedicated Gutenberg blocks for:
- Checkout
- Booking Details
- Waitlist
This is intentional to document accurately: these features should not be described as native Eventixa blocks when they are not registered as such.
Add Checkout with a Shortcode Block
To place Eventixa Checkout inside Gutenberg, use WordPress’s standard Shortcode block and insert:
[eventixa_checkout]
Add Booking Details with a Shortcode Block
Use a normal WordPress Shortcode block with: [eventixa_booking_details]
The booking-details page should use Eventixa’s secure booking-access workflow.
Add Waitlist with a Shortcode Block
When Eventixa Pro Waitlist is enabled, insert: [eventixa_waitlist]
inside WordPress’s standard Shortcode block.
The Waitlist shortcode can target an event, ticket, and recurring occurrence.
Eventixa Block Category
Eventixa registers its Gutenberg blocks under the Eventixa category.
This helps keep Eventixa blocks grouped together in the WordPress block inserter.
Search for Eventixa Blocks
If you cannot immediately see the Eventixa category, search the Block Inserter for terms such as:
- Eventixa
- Events
- Venues
- Organizers
- Event Tickets
- My Account
- Check-In
Server-Rendered Blocks
Eventixa blocks use server-side rendering for their actual Eventixa output.
This means the block’s frontend data is generated using Eventixa’s PHP/frontend rendering system rather than duplicating the full application inside Gutenberg.
Why Eventixa Uses Shared Rendering
Shared rendering provides several benefits:
- Shortcodes and blocks behave consistently.
- Frontend fixes apply across supported display methods.
- Eventixa does not maintain duplicate event-listing logic.
- Pro can extend existing components instead of replacing them.
- Gutenberg remains a configuration adapter over the core frontend system.
Editor Preview
Eventixa loads the required frontend styles inside the Block Editor for supported server-rendered previews.
This helps the Gutenberg preview resemble the actual Eventixa frontend output more closely.
Editor Preview vs Frontend
The Block Editor preview is useful for layout configuration, but always check the published frontend page before launch.
Frontend behavior can also depend on:
- Current user
- URL context
- Event occurrence
- Ticket availability
- Search/filter state
- Check-in permissions
- Theme CSS
Adding an Eventixa Block
To insert an Eventixa block:
- Edit a WordPress page or post.
- Click the + Block Inserter.
- Search for Eventixa.
- Select the required block.
- Configure its options in the block settings.
- Preview the page.
- Publish or update it.
- Verify the frontend output.
Example: Add an Events Block
To create a normal event-listing page:
- Insert Eventixa → Events.
- Choose the Default View.
- Select the Available Views.
- Set Events per page.
- Choose any category, venue, or organizer restrictions.
- Select the initial Sort.
- Enable or disable filters.
- Enable or disable search.
- Enable or disable pagination.
- Publish and test the page.
Example: Create a Grid Events Page
With Eventixa Pro active:
- Insert the Events block.
- Enable Grid in Available Views.
- Select Grid as the Default View.
- Configure the event filters and pagination.
- Publish the page.
You do not need a separate Grid block.
Example: Create a Calendar Page
Insert the Events block and choose:
Calendar
as the Default View.
You can also limit the available view options if you want the page to behave as a dedicated calendar.
Example: Category Landing Page
To create a page for one event category:
- Insert the Events block.
- Select the desired Category.
- Choose the appropriate Default View.
- Configure Events per page.
- Publish the page.
The block still reads from the central Eventixa event database.
Example: Venue Directory
Insert the Venues block and configure:
- Show search
- Items per page
- Show pagination
This creates a dedicated frontend venue directory.
Example: Organizer Directory
Insert the Organizers block and configure the same directory controls.
Example: Embed One Event
Insert Single Event, choose the required event, and publish the page.
This is useful when a page needs the complete Eventixa single-event presentation inside a custom Gutenberg layout.
Example: Add Ticket Selection to a Landing Page
Insert the Event Tickets block.
Select the event whose ticket selector should appear.
Use this when you want ticket selection in a custom Gutenberg page without embedding the complete Single Event block.
Example: Add My Account
Insert the My Account block into a customer account page.
Make sure the page is not publicly cached in a way that could expose authenticated customer information.
Example: Add Frontend Check-In
With Eventixa Pro:
- Insert the Check-In block.
- Publish the page.
- Log in with an authorized user.
- Open the page over HTTPS.
- Test QR scanning.
- Test USB scanner input where applicable.
- Test manual lookup if enabled.
Gutenberg Blocks vs Shortcodes
Both methods can display Eventixa functionality.
Use Gutenberg blocks when you prefer visual controls in the Block Editor.
Use shortcodes when:
- No dedicated block exists
- You use the Classic Editor
- A third-party builder accepts shortcodes
- You need direct shortcode parameters
- You are working inside a shortcode-compatible template area
Gutenberg Blocks vs Elementor
Eventixa uses the same shared widget registry architecture for Gutenberg and Elementor.
The available Eventixa Core components are intentionally similar across both systems.
This reduces differences between editor integrations.
Core Gutenberg Blocks
Eventixa Core provides:
- Events
- Venues
- Organizers
- Single Event
- Event Tickets
- My Account
Pro Gutenberg Extension
Eventixa Pro adds:
- Check-In
Eventixa Pro also extends the Events block with:
- Grid
- Map
Why There Is No Separate Grid Block
Grid is a presentation mode of the Eventixa Events component.
Keeping it inside the same Events block means changing the event view does not require replacing the block.
Why There Is No Separate Map Block
Map follows the same design.
It is another available Event view rather than an unrelated event data source or block.
Do Not Add Duplicate Components
Avoid adding both an Eventixa block and the equivalent shortcode to the same page unless you intentionally want duplicate output.
For example, do not place both: Events block and [eventixa_events] unless two separate listings are actually required.
Multiple Events Blocks on One Page
You can use multiple Events blocks when you intentionally want separate listings.
For example:
- Upcoming Conferences
- Local Workshops
- Online Events
Configure each block with different categories, venues, organizers, views, or result limits.
Theme Styling
Eventixa blocks use Eventixa frontend styles, but your WordPress theme can still influence surrounding typography, widths, spacing, and layout.
If the frontend looks significantly different from the editor preview, inspect theme CSS and container widths.
Block Does Not Appear in the Inserter
Check:
- Eventixa Core is active.
- You are using the WordPress Block Editor.
- The Eventixa block assets loaded successfully.
- A plugin is not disabling custom blocks.
- Browser/admin caches have been cleared.
For Check-In, also verify Eventixa Pro is active.
Grid or Map Is Missing
Grid and Map require Eventixa Pro.
They extend the existing Events block dynamically.
If Pro is inactive, Core correctly exposes only:
- List
- Calendar
- Day
Events Block Shows No Events
Check:
- Published Eventixa events exist.
- Selected category filters contain events.
- Selected venue filters contain events.
- Selected organizer filters contain events.
- The event date/status makes it eligible for the listing.
- Events per page is not configured incorrectly.
Single Event Block Shows Nothing Useful
Confirm an Event was selected in the block settings.
Event Tickets Block Shows No Form
Check:
- An Event was selected.
- The event has standard tickets.
- The ticket sale/availability configuration is valid.
- The recurring occurrence context is valid where applicable.
Remember that RSVP uses the RSVP registration workflow rather than the standard commerce ticket selector.
My Account Looks Empty
Confirm the current customer is logged in and has Eventixa data associated with the account.
Check-In Block Denies Access
Confirm:
- Eventixa Pro is active.
- QR Check-In is enabled.
- The user is logged in.
- The user has the required check-in permission.
Camera Scanner Does Not Start
Use HTTPS on live sites and confirm the browser has camera permission.
Manual Check-In Search Is Disabled
The Eventixa manual lookup option may be disabled in check-in settings.
This is expected behavior when administrators intentionally disable manual Ticket ID lookup.
Block Preview Looks Different
Always compare with the frontend.
The Block Editor preview is not a substitute for testing:
- Search
- Filters
- Pagination
- Event links
- Ticket interactions
- My Account authentication
- QR camera permissions
Recommended Gutenberg Testing
Before launching an Eventixa block page:
- Test desktop layout.
- Test tablet layout.
- Test mobile layout.
- Test event filters.
- Test event search.
- Test pagination.
- Test available event views.
- Test Pro Grid/Map if enabled.
- Test ticket availability.
- Test logged-in My Account behavior.
- Test Check-In with an authorized user.
- Test the published frontend rather than relying only on editor preview.
Common Questions
How Many Eventixa Gutenberg Blocks Are Available?
Eventixa Core currently provides six blocks. Eventixa Pro adds the Check-In block.
What Blocks Are Included in Core?
Events, Venues, Organizers, Single Event, Event Tickets, and My Account.
What Block Does Eventixa Pro Add?
Eventixa Pro adds Check-In.
Are Grid and Map Gutenberg Blocks?
No. They are Pro views inside the existing Events block.
Does the Events Block Support Calendar View?
Yes. Calendar is available in Eventixa Core.
Can I Filter the Events Block by Category?
Yes. The block supports category, venue, and organizer restrictions.
Does the Events Block Support Search?
Yes. Show Search can be enabled or disabled.
Does the Events Block Support Pagination?
Yes.
Is There a Checkout Gutenberg Block?
No. Use WordPress’s standard Shortcode block with [eventixa_checkout].
Is There a Booking Details Block?
No. Use [eventixa_booking_details] inside a WordPress Shortcode block.
Is There a Waitlist Block?
No dedicated Eventixa Waitlist block exists in the current source. Use [eventixa_waitlist] when Eventixa Pro Waitlist is enabled.
Is There a Tickets Block?
Yes. Eventixa Core includes Event Tickets.
Is There a My Account Block?
Yes. Eventixa Core includes My Account.
Can Gutenberg Display One Specific Event?
Yes. Use Single Event and choose the event.
Does Check-In Work Without Login?
No. The current check-in frontend requires an authenticated user with appropriate access.
Do Gutenberg Blocks Use Different Event Templates from Shortcodes?
No. Eventixa reuses its shared frontend rendering architecture where applicable.
Important Notes
- Eventixa registers its blocks under the Eventixa Gutenberg category.
- Eventixa Core provides six blocks.
- Eventixa Pro adds the Check-In block.
- Eventixa Pro extends the Events block with Grid and Map views.
- Grid and Map are not separate blocks.
- Events supports Default View, Available Views, Events per page, category, venue, organizer, sort, filters, search, and pagination.
- Venues and Organizers support search, items per page, and pagination.
- Single Event requires an event selection.
- Event Tickets requires an event selection and renders standard Eventixa tickets.
- My Account has no content-specific block controls.
- Check-In uses the shared Eventixa QR/manual check-in workflow.
- Checkout, Booking Details, and Waitlist do not currently have dedicated Eventixa Gutenberg blocks.
- Unsupported block features can still be inserted using WordPress’s standard Shortcode block.
- Eventixa Gutenberg blocks reuse the shared frontend rendering architecture used by other Eventixa integrations.
