|
ICLE
|
October 9, 2019 at 10:10 am
On a multiple ticket purchase, and an admin enters a good number (greater than 5 or so) of people from the back end, the records sometimes do not save. Sometimes they do. The task can take around an hour. It appears doing fewer at a time tends to work.
I hate the word “sometimes”.
Could this be a timeout error for user engagement on the form?
How would we start to troubleshoot this? What direction can I give the data entry people?
|
|
Josh
|
October 9, 2019 at 10:27 am
Hi,
If they’re taking longer than an hour to fill out the forms, then they’re likely exceeding the session time limit.
Maybe what you could do is give them an extra 30 minutes. You can add 30 minutes (for a total of 90) by adding this code to a site functions plugin:
add_filter(
'FHEE__EE_Session__construct___lifespan',
function() {
return 90 * MINUTE_IN_SECONDS;
}
);
|
|
Tony
|
October 9, 2019 at 10:27 am
The task can take around an hour.
The default session lifespan is 1 hour, so if it is taking longer than an hour the session will be lost when they try to save.
So they are selecting 5 or more tickets in a single group and adding all of the details for each ticket in that group, which takes around an hour, right?
They are not selecting a single ticket, adding the details and the repeating that 5 times, right? (Just confirming I follow how they are entering the details).
If that’s the case you could increase the session lifespan, although that will also mean the session is extended for all users, not just the admin. It will mean that ‘reserved’ tickets will take 2 hours to ‘release’ and abanonded transaction checks that EE does will also take that long.
You can do it using a gist like this:
https://gist.github.com/Pebblo/ee5b686c56fef27dbccb08602821e582
That changes the session to be 2 hours and you can add that to a custom functions plugin on your site, we have some documentation on creating one here:
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
|
|
ICLE
|
October 9, 2019 at 12:50 pm
I did a test in my dev and waited an hour plus a minute to return to the form to finish filling an admin entered (backend) 5 person ticket. I got the following error upon submission:
Fatal Error
Does that look like a timeout error to you guys?
|
|
Josh
|
October 9, 2019 at 12:58 pm
Kind of, because the error indicates no tickets are in the cart, which would happen after the session is expired.
|
|
ICLE
|
October 11, 2019 at 6:50 am
Well, it appears nothing is “releasing” in any event so I will extend the session in my production site.
At least until I do the “time sucking” dev plugin test.
Is there any other way to find the culprit of the “lack of cron?” Possibly an error thrown or something in some WP log someplace? I’m kinda new to this level of debug, so guidance is appreciated.
|
|
Tony
|
October 11, 2019 at 6:54 am
Well, it appears nothing is “releasing” in any event so I will extend the session in my production site.
I’m not sure I follow what you mean here, what is not ‘releasing’?
Is there any other way to find the culprit of the “lack of cron?”
Are you sure there is an issue with WP Crons?
Nothing above indicates an issue with cron so far.
|
|
ICLE
|
October 11, 2019 at 7:09 am
I will make a new ticket on the 4k+ instances of EE_Cron_Tasks::expired_transaction_check()
I am seeing with wp_crontrol
Lots of stuck “ghost” regs so I have simply been upping the max numbers to cancel the frozen reg spots until I can find a fix. New ticket coming.
|
|
Tony
|
October 11, 2019 at 7:28 am
Just to note, Josh posted some details the steps you can take on the above issues in your other thread here:
https://eventespresso.com/topic/where-do-i-remove-these-records-stuck-ticket-counts/#post-300399
|
