• Resolved webbyfoot

    (@webbyfoot)


    Hi I’m sorry if I’ve missed this in the documentation. When testing a new installation as a prospective customer I took a seta purchase as far as PayPal but didn’t complete the purchase, but the seats I selected are still showing not available hours later. Is this a fault or have I missed where I can reduce the reservation time? 5 minutes would be the max I’d want to allow.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter webbyfoot

    (@webbyfoot)

    Ok the seats are available now, but it took over an hour – maybe a caching issue?

    This is an option in the stageshow PHP file held within wp-content/uploads/stageshow.

    The PHP file is well documented. Have a read in that. You can change the timeout option there.

    Chris

    Thread Starter webbyfoot

    (@webbyfoot)

    Ok sorry found it’s called timeout and where it’s set – advanced settings – think I may have noticed before but imagined it was in seconds, not minutes

    There are further options available in the PHP file. If it’s in stageshow settings in the admin panel then great! It’s been a while since I’ve been behind stageshow, however I know there are substantially more options held within the PHP file.

    Thread Starter webbyfoot

    (@webbyfoot)

    Ok I realised what happened I did set it ages ago in the settings, but that reverts to 60 every time they’re saved – so I’ve gone to edited the php file (thanks to @weazel91) but can only find stageshow-wp-config.php – which is empty, and timeout doesn’t appear in the main php plugin files – maybe I can set it in the config file, but what would the syntax be?

    • This reply was modified 1 year, 9 months ago by webbyfoot.
    • This reply was modified 1 year, 9 months ago by webbyfoot.

    I’m not near a stageshow install but there will be an example PHP file where you can copy pieces over from.

    Thread Starter webbyfoot

    (@webbyfoot)

    Thanks @weazel91 – found one in the samples folder.

    Just as a heads up, don’t set it too low. We have seen a fair few people try to pay and get stuck and try again with a card etc later. If there is no database record of tickets when the payment comes in then you’ll end up with tons of emails stating a payment has been made with no matching sales record. I’d keep it a minimum of at least a day.

    Thread Starter webbyfoot

    (@webbyfoot)

    Thanks – I set them short to test
    define(‘STAGESHOWLIB_TROLLEYTIMEOUT’, 300);
    define(‘STAGESHOWLIB_GATEWAYAPI_ABANDON_TIMEOUT’, 10);
    but this didn’t seem to do what I wanted, I think what I was looking for was Checkout Timeout, set at a minimum of 60 (minutes) in the settings. I’ve found where that is in the database and changed that to 10 – that seems to have done the trick!
    We’d like to stop tickets being blocked and preventing last minute sales – we’ll try it with short reservations but if we get your problems, we can’t say you didn’t warn us!

    • This reply was modified 1 year, 9 months ago by webbyfoot.
Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Failed purchase still shows seats reserved’ is closed to new replies.