|
tfkcc
|
November 4, 2020 at 1:42 pm
I’m using this snippet I found in another forum post to change the reserved time for tickets to be 15 minutes before they become available again. Is this the correct snippet to use?
function tw_ee_change_session_lifespan() {
return 30 * 900;
}
add_filter( 'FHEE__EE_Session__construct___lifespan', 'tw_ee_change_session_lifespan');
Is there a way to view and manage reserved tickets for an event?
One of our events shows 2 tickets in the “Rsrvd” column, but we can’t figure out why they’re reserved.
|
|
Tony
|
November 4, 2020 at 2:19 pm
Hi,
The value you return on that filter is what EE will use and its expecting a value in seconds.
So 30 * 900 = 27,000 seconds.
27,000 = 7.5 Hours.
So the correct snippet to use for 15 minutes would be this one:
https://gist.github.com/Pebblo/b6e20b03c57efe693bd86ebcf1b00ce9
Is there a way to view and manage reserved tickets for an event?
No, we don’t have any UI for managing ticket reservations.
One of our events shows 2 tickets in the “Rsrvd” column, but we can’t figure out why they’re reserved.
Tickets are reserved as soon as the ticket selector is submitted with a selection of those tickets so if there has been any ticket selection submission (even if they stopped at the attendee_information step) the tickets will have been reserved. There’s a WP_Cron event scheduled to clean them up after their session expires (default 1 hour) so if they aren’t ‘clearing’ again you may have an issue with WP_Cron.
|
|
tfkcc
|
November 4, 2020 at 2:51 pm
Oh, so the correct value is just 900 seconds which is 15 minutes. I didn’t realize that MINUTE_IN_SECONDS is a constant. I thought it meant set the number of minutes in seconds here you want.
|
|
Tony
|
November 4, 2020 at 3:20 pm
Ahh yeah, I see.
That’s a WP constant used to make it easier to see at a glance, see:
https://codex.wordpress.org/Easier_Expression_of_Time_Constants
|
