Caz Event Manager Pro is built on WordPress and WooCommerce, so most issues can be traced to one of four areas:

1. WordPress or plugin configuration
2. WooCommerce products and orders
3. Caz Event Manager event data
4. Server, browser or JavaScript issues

This guide provides a practical process for diagnosing common problems.

Before Troubleshooting

Before making changes, check the following:

• WordPress is running normally.
• WooCommerce is active.
• Caz Event Manager Pro is active.
• The site is using a supported PHP version.
• The affected event is still a WooCommerce product.
• The affected product is correctly configured as a Caz Event.
• The user has the required permissions.
• The problem can be reproduced.

If possible, make a backup before changing plugin files, WordPress settings or server configuration.

1. Events Are Not Appearing

If an event does not appear in the public event directory, check the following.

Check the shortcode

The public event directory uses:

[caz_events]

Confirm that the shortcode has been entered correctly.

The shortcode should contain:

[caz_events]

with no additional characters.

Check that the plugin is active

Go to:

WordPress → Plugins

Confirm that:

Caz Event Manager Pro

is active.

Check the event product

Caz Event Manager uses WooCommerce products as events.

Open the relevant WooCommerce product and confirm that it has been configured as an event.

The event marker is:

_caz_is_event = yes

If the product is not identified as an event, it will not be treated as a Caz Event.

Check the product status

Confirm that the event product is available for public display.

If the product is still a draft or otherwise unavailable, it may not appear in the public event directory.

2. The Event Directory Is Blank

If the page containing [caz_events] loads but no events are displayed:

1. Confirm Caz Event Manager is active.
2. Confirm WooCommerce is active.
3. Confirm at least one event product exists.
4. Confirm the product is marked as a Caz Event.
5. Confirm the event product is published.
6. Clear any WordPress/cache plugin cache.
7. Test the page while logged out.

If other WordPress content displays normally but the event directory does not, the problem is likely related to the shortcode or event-product configuration.

3. Event Information Is Missing

If an event appears but information such as date, venue or capacity is missing, check the event product.

The main event fields are stored as product metadata:

_caz_event_date

_caz_event_venue

_caz_event_capacity

Open the event product and confirm the relevant fields have been entered and saved.

Also check that the values are valid.

4. Capacity Is Incorrect

If the capacity displayed for an event is incorrect, check the event’s capacity setting.

The event capacity is stored in:

_caz_event_capacity

Confirm that the configured capacity matches the intended number of places.

For example:

Capacity: 20

means the event can accept up to 20 booked places.

Capacity should not be confused with the number of attendees already checked in.

5. Booked Number Is Incorrect

Caz Event Manager calculates event bookings from WooCommerce orders.

Check the following:

• The correct WooCommerce product is being used.
• The booking order contains the correct event product.
• The order has a qualifying status.
• The order quantity is correct.

Processing and completed orders form the basis of the active booking calculation.

Remember that:

1 WooCommerce order ≠ necessarily 1 booking place

A customer may purchase multiple places in a single order.

For example:

Order quantity: 4

represents four booked places.

6. Remaining Places Are Incorrect

The basic calculation is:

Remaining = Capacity − Booked

If the remaining figure is incorrect, first check:

1. Capacity
2. WooCommerce orders
3. Order quantities
4. Order statuses
5. Event product ID

Do not manually alter the remaining figure.

It is calculated from the underlying event and booking information.

7. Customers Cannot Book an Event

If a customer can see an event but cannot complete a booking, test the WooCommerce product directly.

Check:

• Product is published.
• Product is purchasable.
• Product price is configured.
• WooCommerce is operating correctly.
• Cart is functioning.
• Checkout is functioning.
• Payment gateway is functioning.

Caz Event Manager uses WooCommerce for the transaction.

Therefore, a checkout or payment problem may be a WooCommerce or payment-gateway problem rather than an event-management problem.

8. Booking Is Successful but Attendee Is Missing

If the customer has successfully purchased an event but does not appear in the Attendees section, check the WooCommerce order.

Confirm:

• The order contains the correct event product.
• The order has reached a qualifying status.
• The quantity is greater than zero.
• The event product is still identified as a Caz Event.

Also confirm that the Attendees page is displaying the correct event.

9. Attendee Information Is Incorrect

Attendee information is derived from the associated WooCommerce order.

If a customer’s name, email or phone number is incorrect, check the underlying order/customer information.

Do not manually modify the attendee information when the source information is incorrect in WooCommerce.

Correct the appropriate WooCommerce customer or order information first.

10. QR Code Will Not Scan

If a customer’s QR ticket cannot be scanned, check the following:

Customer’s screen

Ask the customer to:

• Increase screen brightness.
• Display the complete QR code.
• Remove anything covering the QR code.
• Hold the phone steady.

Scanner device

Check:

• Camera permission.
• Camera operation.
• Browser permission.
• Internet connection.
• Correct event.
• Scanner page.

If the QR code still cannot be scanned, use the attendee list and manually locate the customer’s booking.

11. QR Code Is Valid but Check-In Fails

If the scanner reads the QR code but the attendee is not checked in, check:

• The ticket belongs to the current event.
• The booking still exists.
• The associated WooCommerce order is valid.
• The attendee has not already been checked in.
• The staff account has the required access.

If necessary, locate the attendee manually in:

Caz Events → Attendees

and use the manual check-in function.

12. Attendee Appears to Be Already Checked In

If a customer presents a ticket that has already been processed, check the attendee record.

The check-in status is stored against the booking for the specific event.

If the previous check-in was accidental, use:

Undo

to remove the check-in status.

Do not create another booking simply because a ticket has been presented twice.

13. Check-In Number Is Incorrect

If the event’s checked-in total is incorrect, review the attendee list.

Look for:

• Incorrect check-ins
• Duplicate handling
• Attendees who should not have been checked in
• Missing check-ins

Use Undo to correct accidental check-ins.

Remember that:

Booked

and:

Checked In

are different figures.

A fully booked event does not necessarily mean every customer has arrived.

14. No-Show Information Is Incorrect

Review the affected attendee.

A no-show should only be recorded when the attendee had a valid booking but did not attend.

Do not mark an attendee as a no-show while the event is still actively receiving customers unless the organiser has a specific reason to do so.

15. Mobile Dashboard Is Not Working

If the Mobile Dashboard does not display correctly:

1. Confirm the user is logged in.
2. Confirm the user has the required Caz Event Manager access.
3. Confirm the event exists.
4. Confirm the browser is up to date.
5. Clear browser cache.
6. Test another browser.
7. Test another device.
8. Check the desktop administration interface.

If the desktop event information works but the mobile dashboard does not, the problem may be isolated to the mobile interface, browser or JavaScript.

16. Staff Member Cannot Access the Event Tools

Check the user’s WordPress account.

Confirm that the user has the appropriate:

CEM Staff

role or other required permissions.

Also check that the account is active and can log into WordPress.

Avoid giving Administrator privileges simply to work around a staff-access problem.

The correct approach is to determine which permission is missing.

17. Shortcode Does Not Work

The main public shortcode is:

[caz_events]

If it does not work:

• Confirm the shortcode is typed correctly.
• Confirm Caz Event Manager is active.
• Confirm WooCommerce is active.
• Test the page using a standard WordPress editor.
• Temporarily test without other page-builder elements.
• Clear caching.
• Test the page while logged out.

If the shortcode displays correctly in a basic WordPress page but not inside a particular page-builder layout, the issue may be related to the page builder or theme.

18. Event Cloning Problems

If event cloning does not behave as expected, check the original event first.

Confirm that:

• The original product is a Caz Event.
• The original product can be edited.
• The user has the required permissions.

After cloning, confirm that the new event:

• Has its own product ID.
• Is created as a separate product.
• Does not contain the original booking records.
• Has the appropriate event settings.
• Has a new event date configured before publishing.

A cloned event should not inherit the original event’s attendee bookings.

19. Event Date Is Incorrect

Check the event’s date and time settings.

Also check the WordPress site’s timezone:

WordPress → Settings → General

Confirm:

Timezone

is configured correctly.

Date and time problems can sometimes appear to be plugin problems when the underlying WordPress timezone is incorrect.

20. Venue Is Incorrect

Open the event product and check the venue field.

The event venue is stored as:

_caz_event_venue

Save the product again after correcting the venue.

Then clear any site/page cache before testing the public event page.

21. Event Changes Are Not Appearing on the Website

If an event has been changed but the public page still shows old information, check caching.

Possible caching layers include:

• WordPress caching plugins
• Server cache
• LiteSpeed cache
• CDN cache
• Browser cache

Clear the relevant cache and reload the page.

Also test the page in a private/incognito browser window.

22. JavaScript Errors

Some event-management functions rely on JavaScript.

If a function such as the scanner or mobile interface does not respond correctly, check the browser developer console.

In Chrome or Edge:

Right-click → Inspect → Console

Look for JavaScript errors.

A JavaScript error generated by another plugin or theme can prevent an otherwise working Caz Event Manager interface from operating correctly.

23. Plugin Conflict

If Caz Event Manager worked previously and stops working after another plugin is installed or updated, a plugin conflict is possible.

A controlled test can help identify the cause.

Before doing this on a production website:

• Take a backup.
• Ideally test on a staging site.
• Disable non-essential plugins one at a time.
• Test the affected function after each change.

Pay particular attention to plugins that modify:

• WooCommerce products
• WooCommerce checkout
• Product fields
• JavaScript
• AJAX
• User permissions
• Caching
• Security
• REST/API behaviour

Do not leave required security or production plugins disabled after testing.

24. Theme Conflict

A theme or child theme can also interfere with event functionality.

If an event directory or front-end event display is broken:

1. Test the shortcode on a basic page.
2. Test using a standard WordPress theme on staging.
3. Compare the result.

If the functionality works correctly with the standard theme, investigate the active theme or child theme.

25. WooCommerce Problems

Because Caz Event Manager uses WooCommerce, check WooCommerce independently when diagnosing booking problems.

Test:

• Product creation
• Product purchase
• Cart
• Checkout
• Order creation
• Order status
• Customer information

If normal WooCommerce products also have problems, fix the WooCommerce issue before troubleshooting Caz Event Manager.

26. PHP Errors or Fatal Errors

A blank page, critical error or WordPress error may indicate a PHP problem.

Check:

WordPress → Tools → Site Health

and the relevant PHP/server error log.

When reporting a PHP error, record the complete error message.

Important information includes:

• Error type
• File name
• Line number
• Function/class mentioned
• Full error message

Do not guess which plugin file is responsible simply because it appears in the error message.

A plugin can be the location where another dependency or incompatible value causes the error.

27. Enable WordPress Debugging

For development or staging environments, WordPress debugging can help identify PHP problems.

Typical development settings include:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

This records errors in the WordPress debug log without displaying technical errors to normal website visitors.

Do not expose PHP errors publicly on a production website.

After troubleshooting, return debugging settings to the site’s normal production configuration.

28. Check the Server Environment

If the plugin behaves differently between sites, compare the server environments.

Useful information includes:

• PHP version
• WordPress version
• WooCommerce version
• Memory limit
• Maximum execution time
• Maximum input variables
• Web server
• Object cache
• Page cache

Server-level differences can cause apparently identical WordPress installations to behave differently.

29. Caching Problems

Caching can make it appear that an event has not changed.

If you change:

• Event date
• Venue
• Capacity
• Event availability
• Event content

and the public page does not update, clear the relevant caches.

When troubleshooting, test using:

• A logged-in administrator session
• A private browser window
• A different device

This helps distinguish cached output from actual plugin behaviour.

30. Troubleshooting Workflow

When a problem occurs, use this order:

1. Identify the exact function that is failing

↓

2. Confirm WordPress is working

↓

3. Confirm WooCommerce is working

↓

4. Confirm Caz Event Manager is active

↓

5. Check the affected event product

↓

6. Check the relevant order/attendee

↓

7. Check permissions

↓

8. Check browser JavaScript

↓

9. Check caching

↓

10. Check PHP/server logs

↓

11. Test for plugin/theme conflicts

This approach avoids changing multiple things at once and makes the actual cause easier to identify.

Reporting a Problem

When reporting a Caz Event Manager problem, provide as much of the following information as possible:

Plugin

• Caz Event Manager Pro version

WordPress

• WordPress version

WooCommerce

• WooCommerce version

PHP

• PHP version

Event

• Event name
• Event/product ID if available

User

• Administrator or CEM Staff

Problem

Describe exactly what happens.

For example:

“The event appears in [caz_events], but clicking Book Now produces a blank page.”

This is much more useful than:

“Events are broken.”

Error Information

If an error is displayed, provide the complete error message.

If possible, also provide:

• Screenshot
• Browser console error
• PHP error log
• Relevant WooCommerce order number

Do not include customer passwords, payment information or other sensitive information.

Developer Troubleshooting

Developers investigating a problem should first establish whether it is:

Data

Incorrect event/order/attendee information.

Permission

User cannot access a function.

PHP

Server-side error.

JavaScript

Browser-side error.

WooCommerce

Product/order/checkout problem.

Theme

Front-end display conflict.

Plugin Conflict

Another plugin changes the expected behaviour.

Caching

Old content is being displayed.

Identifying the category before changing code makes troubleshooting considerably faster.

Troubleshooting Checklist

Event

• Event product exists.
• Product is published.
• Product is marked as a Caz Event.
• Date is correct.
• Venue is correct.
• Capacity is correct.

Booking

• WooCommerce checkout works.
• Order exists.
• Correct event product is in the order.
• Quantity is correct.
• Order status is qualifying.

Attendees

• Correct event selected.
• Attendee appears.
• Customer information is correct.
• Booking quantity is correct.

Check-In

• QR scanner opens.
• Camera permission is enabled.
• QR code can be read.
• Correct event is selected.
• Attendee can be checked in.
• Undo works if required.

Mobile

• User can log in.
• User has appropriate staff access.
• Mobile dashboard loads.
• Browser is current.
• JavaScript is functioning.

Website

• WordPress is functioning.
• WooCommerce is functioning.
• Caz Event Manager is active.
• No plugin conflict.
• No theme conflict.
• Cache has been cleared.

Summary

Most Caz Event Manager Pro problems can be diagnosed by following the relationship between:

WordPress

→ WooCommerce

→ Event Product

→ Booking

→ Attendee

→ QR Ticket

→ Check-In

When troubleshooting, start with the specific function that is failing and then work backwards through that chain.

Caz Event Manager Pro is built on WooCommerce rather than replacing WooCommerce, so problems involving products, orders, checkout or payments should also be tested independently of the event-management layer.

For technical problems, the most useful information is the exact error, affected event, affected order or attendee, user role, WordPress/WooCommerce/PHP versions and relevant logs.

A structured diagnosis is considerably safer than modifying plugin files or server settings without first identifying the cause.