Replies for tickets on suppota
Hello,
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.
As Artem mentioned, the block based checkout page is not supported with tickets addon. Woocommerce has not finalize the block based method and they are still going back and forth on the code for it.
Kindly use shortcode based cart and checkout pages for now.
Please try the latest update to Tickets 2.3.1 and PDFer addon 0.8. And make sure to clear cache after updates to ensure new version codes are loaded on to the page.
please update the latest version of PDFer addon 0.8 and tickets 2.3.1 should resolve this.
please try the latest ticket update 2.3.1 and QR code update 2.0.3 should resolve the QR code not generating. Also PDFer new version 0.8.
Kindly update to the latest version of QR code 2.0.3 and tickets 2.3.1
Hello Helen, when you said, it looks wrong, what exactly are you referring to?
In the most recent version we will add the option to auto complete orders. Also please make sure these are not selected.
We have not tested. I will see if Artem can run some tests on your staging site.
Thank you for your messages, I am going to assign this ticket to Ashan and he will be able to take it from here and find you a solution. Please allow some time for him to get back to you, we greatly appreciate your patience and thank you for being a eventon customer!
I have now tested this is your demo
https://dev.myeventon.com
dev.myeventon.com/testing/
It is the same result
you can’t add a new event if it is including tickets. This is a security update from WooCommerce that becomes a conflict.
the page is only loading and no summation is done. In the admin area you can see the event with missing information about price, Sru and so on.
Shortcode used is [add_evo_submission_form msub=”yes”]
Of cause that’s why I am addressing the conflict with the update of WooCommerce. You can’t use action user properly any more.