Support

March 22, 2022 at 6:12 am

Hi there,

Now, if someone selects 2 from ticket selector and go to registration page, the status for that ticket become sold out even if user has not completed the registration.

That’s expected, the tickets go into reserve for the duration of the user’s session (which is 1 hour by default), after that time the tickets should ‘release’ again if the registration was not complete.

We do the above to prevent overselling and users losing tickets whilst they are in the process of registration.

User A selects the 2 tickets and starts the registration, it takes them a little time to add their details and load the payment options…

In the meantime User B comes along and selects those same 2 tickets, uses autofill in their browser and completes the attendee into step, they either hit the payment step before User A or at the same time.

Now, who should be able to purchase those tickets? EE can either refuse User A, Use B, both, or allow both? The reservation system we use means the tickets are reserved when User A selected them and User B can’t slide in at the last second.

Anther issue is, if by mistake user hits the back button of browsers, he/she doesn’t have any option to complete the registration.

If they go back to the checkout page they should be able to continue with the registration.

March 22, 2022 at 10:10 am

The UTS value in the URL is a cache busting method, it’s a timestamp (Unix TimeStamp) and has no other meaning other than try to stop the browser/server from caching the response.

If you are getting a blank page when going to /registration-checkout/

But then getting results when you go to /registration-checkout/?uts=12345

There’s likely caching enabled on your site/server.

Can you link me to an event I can take a look at?

March 24, 2022 at 7:25 am

Yeah, that’s some kind of cached response.

When you go to the checkout page:

https://cecgolfdev.wpengine.com/registration-checkout/

The shortcode isn’t even processed on that request as it should show ‘Nothing in your Event Queue’ if nothing has been added to the current session.

You can see that if you go to a URL with the uts value set:

https://cecgolfdev.wpengine.com/registration-checkout/?uts=111

UTS=111 is not ‘valid’, it is not something that would ever be used by EE itself but you can see the error shown there.

Somewhere the registration checkout page has been cached. Try adding some text below the [ESPRESSO_CHECKOUT] shortcode to see if that shows up on the page that isn’t working.

March 25, 2022 at 10:15 am

The only one used by Event Espresso is a PHP session, so on your site PHPSESSID

It’s possible this is also something from using Elementor for the checkout page, they also cache the output iirc (I don’t use Elementor).

Does the same happen if you add the shortcode to that page outside of Elementor?