Posted: June 5, 2017 at 7:02 am
Hi, we’re running 4.9.38. User is saying that 100 ticket batches registered via admin are timing out, resulting in 77 getting processed and charged. Prior versions didn’t trigger error for same case. Batch of 50 seems to work. |
|
Hi there,
What do you mean by ‘charged’? Payment taken? Event Espresso does not process payments for registrations made through the admin so I’m not sure what this refers to. Is there an error shown when this happens? For example, is it a PHP timeout (max_execution_time reached) or database?
Which version were you using before? Have you kept up to date with all of the latest versions? |
|
Thanks. Disregard payment–I don’t use the system myself, just going by user’s report. |
|
Try enabling error logging on the site and retest to see if any errors are thrown, without an error pointing to what is failing we don’t know what causing problems on your server. You can use this snippet: https://gist.github.com/Pebblo/8787f5530ea777c84aaf62f075e55b32 In your wp-config.php file which enables error logging within /wp-content/debug.log and does not display the errors on the site.
It depends on what you’ve changed but we can provide details on the recommend method to use if you provide details. The invoice template would be edited through the admin, unless you customized the invoice template way back when the invoice system was not included in the messages system. Thank you template you can load from within your themes root directory. Single page checkout is not the ticket selector, I may sound nit picky saying that but they are 2 separate sections. Again if you let me know more details we should be able to make some recommendations.
The problem with such a large jump is there have now been many changes since then so we don’t know where to start looking for what may be causing a bottleneck. |
|
1. However, when selected the 100 registrations in Registrations, and applying Bulk Action: Cancel Registrations, I got: I think WPEngine must put a hard-limit on request processing duration, and as updates are slower than inserts, the error occurs on Bulk Edit only. We can work around this by doing edits in smaller batches. 2. |
|
Yes, please open a new thread (you don’t need one for each just a single thread will do), it just helps keep threads specific and is easier to follow in the long run. |
|
The support post ‘reg qty 100 timing out’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.