Timeout when adding ticket type
Thanks for reaching out to us!
That seems a strange issue you are having. Let me try to help you with it.
Does the issue happen when editing an existing event or also when creating a new event from scratch?
After that, try reproducing the issue a few times, so that in case there is an error, it will be saved into the debug.log file. Please share that log file with us so we can see if any problem from there.
I can see you are using an older version of WordPress 4.8.4. While I’m not sure about it, it could be worth trying to update, so please try updating WordPress to the latest version and see if any difference.
If there’s no difference, then you I’d recommend you go through our testing for conflicts guide to see if we can narrow down the problem to a theme or plugin conflict > https://theeventscalendar.com/knowledgebase/testing-for-conflicts/
Let me know how that goes.
Thanks for the assistance.
I’ve enabled the debug log, there’s only one error, but this seems to be thrown on every page load, not just when updating an event, so I believe it’s unrelated.
The problem does not happen when creating an event, a new event saves OK. The issue seems to happen when adding a new ticket type to an existing Event.
I’m able to create a new event with multiple ticket types, but adding a new ticket type to an existing event seems to cause the issue.
I am going to check with our external content provider on being able to update WordPress, once I get that confirmation, I’ll upgrade and try testing again.
I’m sorry I confused your name before.
Thanks for following up with this.
I have tried reproducing the issue using WordPress version 4.8.4 but couldn’t, so it seems unlikely the WordPress version is the source of the problem. That said, we always encourage to use the latest versions of WordPress available.
Before diving into the tests I mentioned, have you tried using a different browser or device to see if any difference? I have researched the ERR_EMPTY_RESPONSE error you are getting and it seems many times the problem resides in the browser and/or could also be related to a problem on the server side.
I’d suggest you also get in touch with the hosting provider to see if they can offer some insight about the issue.
Let us know how that goes.