--- title: Troubleshooting Overview description: The Eventixa Troubleshooting section helps you identify and resolve common issues across the event registration workflow. Use this guide as the starting point when something in Eventixa is not behaving as expected. It covers the first checks to perform, explains… url: "https://eventixawp.com/docs/troubleshooting-overview/" updated: "2026-09-26" category: Troubleshooting --- # Troubleshooting Overview The Eventixa Troubleshooting section helps you identify and resolve common issues across the event registration workflow. Use this guide as the starting point when something in Eventixa is not behaving as expected. It covers the first checks to perform, explains where different problems usually originate, and directs you to the detailed troubleshooting article for the affected feature. The current Eventixa Documentation V2 troubleshooting set focuses on real operational areas: - Ticket availability - Checkout - Payments - Email delivery - Zoom and Google Meet - QR tickets and check-in For migration-specific problems, use the separate Migration Warnings & Troubleshooting documentation. ## Before You Begin Before troubleshooting a specific Eventixa feature, confirm the basic environment first. 1. Make sure Eventixa Core is installed and active. 2. If the affected feature requires Eventixa Pro, confirm Eventixa Pro is active. 3. Confirm WordPress, Eventixa Core, Eventixa Pro, and required integrations are up to date. 4. Save any unsaved Eventixa settings or event changes. 5. Clear relevant page, object, CDN, and browser caches. 6. Reproduce the issue using a fresh browser session when practical. 7. Note the exact event, ticket, booking, attendee, payment, occurrence, or integration involved. 8. Record any error message exactly as shown. When testing checkout, payment, email, or integration issues, use a controlled test event or staging environment where practical. ## Start with the Affected Workflow Eventixa features are connected. A problem visible at one step may originate earlier in the workflow. A simplified Eventixa flow is: **Event → Ticket / RSVP → Checkout → Booking → Payment → Attendee → Email / Ticket → Check-In → Reports** For virtual events, the flow can also include: **Event → Virtual Provider → Meeting → Attendee Access** Start troubleshooting at the earliest step where the result becomes incorrect. ## Quick Troubleshooting Map | Problem | First Area to Check | Detailed Guide | | --- | --- | --- | | Ticket shows sold out unexpectedly | Ticket capacity, booking state, active checkout sessions | Ticket Availability Problems | | Ticket does not appear | Sale schedule, availability, event/occurrence context | Ticket Availability Problems | | Checkout does not open or complete | Ticket configuration, Guest Checkout, checkout session, required attendee data | Checkout Problems | | Payment method is missing | Eventixa → Settings → Payments | Payment Problems | | Booking exists but payment looks wrong | Booking status and payment status | Payment Problems | | Customer did not receive an email | Eventixa → Settings → Emails and WordPress mail delivery | Email Delivery Problems | | Zoom or Google Meet is unavailable | Eventixa → Settings → Integrations | Virtual Event Integration Problems | | Meeting access is wrong for a recurring event | Event provider and recurring meeting mode | Virtual Event Integration Problems | | QR ticket cannot be scanned | Ticket validity, attendee status, QR/Check-In settings | QR Ticket & Check-In Problems | | Attendee cannot be checked in | Event/occurrence selection, attendee state, Check-In configuration | QR Ticket & Check-In Problems | | Migration reports warnings or skipped data | Migration report and source compatibility | Migration Warnings & Troubleshooting | ## Check Event Configuration First If an issue affects only one event, start by editing that event. Go to: **Eventixa → Events → Edit Event** Review the configuration related to the problem. Depending on the issue, check: - Event date and time - Event timezone - Recurring-event configuration - Ticket or RSVP configuration - Ticket capacity - Ticket sale schedule - Minimum and maximum quantity rules - Attendee collection settings - Virtual or Hybrid event settings - Meeting provider - Event integrations - Waitlist settings - Coupons If the same problem affects many events, review the corresponding global setting next. ## Check Global Eventixa Settings Global Eventixa settings are available from: **Eventixa → Settings** Important areas include: - General - Display - Tickets - Payments - Emails - Integrations - Advanced - License when Eventixa Pro is active A global setting can affect many events at once. For example: - Guest Checkout is controlled globally under Ticket settings. - Currency and payment gateways are controlled under Payments. - Email sender, templates, and styling are controlled under Emails. - Google Maps, MailPoet, Mailchimp, Zoom, Google Meet, and Webhooks use Integration settings where applicable. ## Check Core vs Pro Availability Some Eventixa features are available in Core, while others require Eventixa Pro. If an expected option is missing, confirm the feature availability before treating it as an error. Examples of Pro functionality include advanced modules such as native Stripe integration, managed Zoom/Google Meet workflows, advanced reporting, QR/PDF ticket features, Check-In, Waitlist, and other premium features. The exact availability should always be confirmed from the documentation for the feature you are using. ## Check Plugin Dependencies Some Eventixa integrations depend on another WordPress plugin or an external service. Examples include: - MailPoet - WooCommerce - Zoom - Google Meet - Mailchimp If the required plugin or service is unavailable, Eventixa can disable or hide related controls. Before troubleshooting the Eventixa side, confirm the dependency itself is active and working. ## Ticket Problems Ticket issues commonly involve one or more of these areas: - Ticket capacity - Ticket sale start and end dates - Booking status - Checkout reservations - Recurring occurrence availability - Quantity rules - Event date - Waitlist state Do not treat ticket capacity as only the number of completed payments. Eventixa ticket availability can also be affected by booking state and temporary checkout capacity handling. For detailed diagnosis, see **Ticket Availability Problems**. ## Checkout Problems If checkout does not start, does not progress, or does not complete, check: - Ticket availability - Guest Checkout setting - Purchaser information - Required attendee fields - Checkout session state - Payment method configuration - Page assignment - Browser JavaScript errors - Caching or optimization interference Eventixa checkout uses a temporary session to protect limited ticket capacity while a customer completes registration. Reloading checkout does not create a new session indefinitely. For detailed diagnosis, see **Checkout Problems**. ## Payment Problems A booking and a successful payment are not the same thing. When troubleshooting payments, check both: - Booking Status - Payment Status Also confirm: - Currency - Gateway activation - Gateway credentials - Test vs live configuration - WooCommerce configuration when WooCommerce Checkout is used - PayPal or Stripe response - Offline payment state where applicable For detailed diagnosis, see **Payment Problems**. ## Email Delivery Problems If Eventixa creates the expected booking but no email arrives, separate the problem into two parts: **Eventixa email generation** and **WordPress email delivery** Review: **Eventixa → Settings → Emails** Check: - Sender settings - Email template - Trigger state - Subject and content - Recipient address Then check the WordPress mail environment, such as SMTP or transactional email configuration. For detailed diagnosis, see **Email Delivery Problems**. ## Virtual Event Integration Problems For Zoom or Google Meet problems, first determine whether the issue is global or event-specific. Global checks: **Eventixa → Settings → Integrations** Event-level checks: **Eventixa → Events → Edit Event → Event Settings → Integrations / Virtual Event settings** Review: - Provider connection - Authorization state - Event mode - Selected meeting provider - Meeting creation - Recurring meeting mode - Provider switching - Attendee join access For recurring events, confirm whether the event uses the same meeting for all occurrences or separate meetings per occurrence. For detailed diagnosis, see **Virtual Event Integration Problems**. ## QR Ticket and Check-In Problems QR and Check-In problems can involve: - Ticket generation - Booking or attendee state - Event/occurrence selection - QR validation - Check-In permissions - Camera access - HTTPS - Manual check-in availability For camera-based scanning, browser permissions and HTTPS can matter. For recurring events, always confirm the correct occurrence before checking in an attendee. For detailed diagnosis, see **QR Ticket & Check-In Problems**. ## Recurring Event Problems When an issue affects a recurring event, always verify the occurrence context. A recurring parent event and one individual occurrence are not always the same reporting, ticketing, virtual-meeting, or attendance context. Check: - Selected occurrence - Ticket assignment - Occurrence date/time - Recurring agenda mode - Virtual meeting mode - Check-In occurrence - Report occurrence filters If a value looks correct at the parent-event level but wrong on one date, inspect the specific occurrence. ## Booking and Attendee Problems Bookings and attendees are different Eventixa records. One booking can contain multiple attendees. If counts or statuses appear inconsistent, review: **Eventixa → Bookings** and **Eventixa → Attendees** Check the relevant booking details before assuming data is missing. ## Cache and Optimization Conflicts Aggressive caching and optimization can interfere with dynamic Eventixa workflows. When troubleshooting frontend issues, temporarily test without: - Full-page cache on checkout/account pages - JavaScript delay or defer rules affecting Eventixa scripts - HTML minification that changes form markup - CDN cache for dynamic pages After changing settings, clear: - WordPress cache - Server cache - CDN cache - Browser cache Then test again in a private/incognito window. ## Theme or Plugin Conflict Test If the issue cannot be reproduced on another site, test for a conflict. On a staging site where possible: 1. Temporarily disable unrelated plugins. 2. Test Eventixa again. 3. Re-enable plugins one at a time. 4. If needed, temporarily switch to a standard WordPress theme. 5. Re-test the same Eventixa workflow. Do not perform disruptive conflict testing on a live production site without planning for the impact. ## Check Browser and Server Errors For frontend problems, browser developer tools can reveal: - JavaScript errors - Failed AJAX/REST requests - Blocked resources - HTTP errors For server-side problems, review the WordPress/PHP error log where available. Record: - Exact error text - Request URL - HTTP status - Event or booking ID - Time of the error Do not share passwords, API secrets, license keys, private join links, or customer personal information in public support channels. ## Reproduce the Problem Clearly A useful troubleshooting report should include: - Eventixa Core version - Eventixa Pro version, if active - WordPress version - WooCommerce or integration version when relevant - Exact Eventixa screen - Exact steps to reproduce - Expected result - Actual result - Error message - Whether the issue affects one event or all events - Whether the issue also occurs on staging For recurring events, also include the affected occurrence. ## Example Troubleshooting Workflow Suppose a customer says a paid ticket cannot be purchased. A practical troubleshooting process is: 1. Open the event and verify the ticket is enabled. 2. Confirm the sale schedule is active. 3. Confirm capacity remains. 4. Check whether the problem affects one occurrence or the whole event. 5. Test checkout yourself. 6. Confirm Guest Checkout behavior if testing while logged out. 7. Confirm the required payment gateway is active. 8. Review the resulting booking and payment status. 9. Clear cache and test again. 10. If the problem continues, follow the dedicated Checkout or Payment troubleshooting guide. This approach starts with the earliest possible failure point instead of changing unrelated settings. ## Important Notes - Troubleshoot the earliest incorrect step in the Eventixa workflow. - Check event-specific settings before global settings when only one event is affected. - Check global Eventixa settings when the problem affects many events. - Bookings, payments, attendees, and check-ins represent different states and records. - Recurring events should be diagnosed in the correct occurrence context. - Core and Pro feature availability should be confirmed before troubleshooting a missing control. - External integrations may require third-party services, credentials, or plugins. - Dynamic checkout and account pages should not be aggressively cached. - Never expose API keys, license keys, payment credentials, private meeting links, or customer data when sharing diagnostic information. ## Related Documentation - [Ticket Availability Problems](https://eventixawp.com/docs/ticket-availability-problems/) - [Checkout Problems](https://eventixawp.com/docs/checkout-problems/) - [Payment Problems](https://eventixawp.com/docs/payment-problems/) - [Email Delivery Problems](https://eventixawp.com/docs/email-delivery-problems/) - [Virtual Event Integration Problems](https://eventixawp.com/docs/virtual-event-integration-problems/) - [QR Ticket & Check-In Problems](https://eventixawp.com/docs/qr-ticket-check-in-problems/) - [Migration Warnings & Troubleshooting](https://eventixawp.com/docs/migration-warnings-troubleshooting/) ## Frequently Asked Questions ### Where should I start when Eventixa is not working as expected? Start with the earliest point in the Eventixa workflow where the result becomes incorrect. Check the affected event first, then the related global Eventixa settings. ### Should I clear cache before troubleshooting Eventixa? Yes. Caching can preserve outdated settings or interfere with dynamic frontend workflows. Clear relevant WordPress, server, CDN, and browser caches before retesting. ### Why do booking, attendee, and payment numbers not always match? They represent different records and states. One booking can contain multiple attendees, and a booking can exist without a completed payment. ### What should I check first for a recurring event issue? Confirm the specific occurrence. Parent-event data and occurrence-specific data can represent different ticket, meeting, attendance, and reporting contexts. ### What information should I include when asking for support? Include your Eventixa versions, WordPress version, exact steps, expected result, actual result, error message, and the affected event or occurrence. Remove or blur all confidential information.