Archives: Replies

Hello,

Could you try creating a new page with simple EventON shortcode and check?

If the issue continues, please follow the instructions in this documentation to activate debug in your site to see any PHP errors recorded that can provide insight on to whats going on. Please reply with a link to debug.log file. If you are not able to do this please send us FTP access to your site so we can do this for you.

Also could you copy all the info from the browser console and send here?

Hello,

You can add it to Event Details the same way you add it to Post or Page using the default functionality of WordPress itself.

If you need a separate field, please take a look at Custom Meta fields:

https://docs.myeventon.com/documentations/setup-use-custom-meta-fields-events/

Ah sorry, I thought you wanted to add the birthday field to the export attendees list only. Unfortunately, the guide only allows you to change the .csv file you can download from Edit Event. Changing the list itself cannot be done without changing the code.

Thank you so much,

I will try to implement that. Will this reflect on the attendees list?

Best

Carmen

only problem then is that i have to manually change the status and of cours you would rather not.

Thanks for coming back fast. In fact you would not need the login, as it does actually happen on your own test page. It did not even appear after 8x refresh. With Safari there is no such issue. 

Latest version are used on lalelu.de, yes.

Hello Artem,

thank you for your message. You can find the new screen video here:

https://www.frankfiess.de/wp-content/uploads/2025/06/Bildschirmaufnahme-2025-06-16-um-18.08.56.mov

Best regards

Benedikt

Okay, trying to reproduce. When I unchecked the option in tickets->checkout-> autocomplete the error is not appearing and the behaviour is correct. So I assume it is in the option for autocomplete…

This is the debug error message:

[16-Jun-2025 13:28:19 UTC] get_billing_first_name was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), wp, WP->main, WP->parse_request, do_action_ref_array(‘parse_request’), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, WP_REST_Server->respond_to_request, AutomatticWooCommerceStoreApiRoutesV1Checkout->get_response, AutomatticWooCommerceStoreApiRoutesV1AbstractRoute->get_response_by_request_method, AutomatticWooCommerceStoreApiRoutesV1Checkout->get_route_post_response, do_action(‘woocommerce_store_api_checkout_order_processed’), WP_Hook->do_action, WP_Hook->apply_filters, EVOTX_WC->create_evo_tickets_for_store_api, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_completed’), WP_Hook->do_action, WP_Hook->apply_filters, EVOTX_WC->send_ticket_email, evotx_email->send_ticket_email, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.

[16-Jun-2025 13:28:19 UTC] get_billing_last_name was called incorrectly. Order properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), wp, WP->main, WP->parse_request, do_action_ref_array(‘parse_request’), WP_Hook->do_action, WP_Hook->apply_filters, rest_api_loaded, WP_REST_Server->serve_request, WP_REST_Server->dispatch, WP_REST_Server->respond_to_request, AutomatticWooCommerceStoreApiRoutesV1Checkout->get_response, AutomatticWooCommerceStoreApiRoutesV1AbstractRoute->get_response_by_request_method, AutomatticWooCommerceStoreApiRoutesV1Checkout->get_route_post_response, do_action(‘woocommerce_store_api_checkout_order_processed’), WP_Hook->do_action, WP_Hook->apply_filters, EVOTX_WC->create_evo_tickets_for_store_api, WC_Order->update_status, WC_Order->save, WC_Order->status_transition, do_action(‘woocommerce_order_status_completed’), WP_Hook->do_action, WP_Hook->apply_filters, EVOTX_WC->send_ticket_email, evotx_email->send_ticket_email, WC_Abstract_Legacy_Order->__get, wc_doing_it_wrong. This message was added in version 3.0.