Igor S.

Hi there,

Since you were able to reproduce this in Troubleshooting Mode with only Tickera active and a default theme, it does point quite strongly to something within Tickera affecting the REST API response.
A few things you can try/check on your end:
First, enable WordPress debugging and check for any hidden errors. You can do this by adding the following to your wp-config.php:

define( ‘WP_DEBUG’, true );
define( ‘WP_DEBUG_LOG’, true );
define( ‘WP_DEBUG_DISPLAY’, true );

Then revisit /wp-json/wp/v2/types and /wp-json/
If anything is being output before or instead of JSON (warnings, notices, or fatal errors), that would explain the “black” response.

Second, this can sometimes happen if something outputs content too early (for example, unexpected echo, BOM characters, or PHP notices), which breaks REST responses. Since Tickera registers multiple custom post types, the /wp-json/wp/v2/types endpoint is particularly sensitive to that.

If possible, could you also let us know:
What exactly you see when you say the endpoint “goes black” (completely empty response, 500 error, or something else)?
Whether there are any errors in your server/PHP error logs at the moment you hit that endpoint?

Thanks.

Since your issues are not related to the free version of Tickera given that you’re referring to WooCommerce which requires Bridge for WooCommerce and Seating Charts add-on both of which are premium plugins, I’d have to ask you to submit a support ticket via our contact form found here.

Thanks.

You can create a custom template for the event page and modify the way it is being displayed. More about this can be found in our documentation here.

I’m glad to learn you were able to figure it out and thank you for letting us know.

For future reference, if you experience any similar issues (which I hope you won’t but still), you should first navigate to Tickera Settings -> System and check if any of the listed items are “red” which may give you a clue what might be the culprit of the issue. In this particular case, when one of Tickera pages does not exist or does not contain required shortcode, it will be clearly visible there.

Cheers!

WP_DEBUG should not be used on live/production site for several reasons. For example, if it is enabled and some warnings, notices or errors appear, the debug message may reveal file paths, plugin names or database related messages which, as you may imagine, is not very good practice. On top of this, if enabled, debugging can potentially impact the performance of your website as it will log more data and may write large log files over time.

So, you should make sure to turn off debugging on live/production website.

Hope this helps a bit.

Tickera is an online event ticketing system intended for selling tickets on your website and delivering them via email directly to the customer so they can print their tickets themselves.

So, the only way for the ticket to get generated is to add it to the cart and successfully finish the checkout process. Now, if you need to do this manually, you can create a 100% discount code that will be known only to you and use it on the checkout to avoid an actual payment but the rest of the checkout process is the same as when the customer is purchasing their tickets.

As for the question about saving buyer data, the answer is quite simple: if the customer make a purchase as registered and logged in user, their data will be saved and pre-filled as buyer details when making all the subsequent orders. Attendee data, however, needs to be filled each time.

Hope this helps a bit.

The allow_url_fopen should not have any effect on the checkout itself as it is used only when rendering tickets to PDF files.

As for the issue with the Terms and Conditions, can you please point us to the exact URL on your website where this occurs so we could try and replicate the issue and try figuring out why is this happening?

Thanks.

Can you please let us know which payment method have enabled and configured and what is the order total that is failing to process?

Thanks.