|
Jeff
|
May 8, 2021 at 7:59 am
we have an event here https://mikelemoncasting.com/acting-classes/ Preparing for a career in Voiceover that has a 12 ticket limit but ONLY 11 have been sold but it is showing sold out on our page. here are the event details – how do we fix this so it allows 12 paid tickets instead of only 11?
Back end screen shots:
https://www.dropbox.com/s/wzc30gyno47ps5i/sold%20out.jpg?dl=0
https://www.dropbox.com/s/4axs0jgszh6j2zy/tickets.jpg?dl=0
I even went in and raised the ticket limit to 18 and it still shows sold out – This is a very bad BUG in your system!
|
|
Tony
|
May 11, 2021 at 2:16 am
Hi there,
Did it only show sold out on the front end? When logged in or out?
The screenshots show your event status as upcoming (top right) and ticket on that event as active (status bar to the left of each individual ticket) so as far as EE is concerned that event is active.
Looking at the first link you provided if I view the source code I see this comment:
<!-- WP Fastest Cache file was created in 0.78134894371033 seconds, on 10-05-21 18:39:55 -->
I’m guessing the pages (the event list and single event pages are set to cache) were cached when the event was set to sold out and user then saw the stale cache and it’s now been regenerated on the above date/time so shows correctly. I’d recommend you exclude any EE pages from caching and we have some details on this here:
https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/
The above looks like a page in which you are using [ESPRESSO_EVENTS] to list the event, so that would also need to be added to the exclude list.
There is a reservation system in EE to prevent overselling, so if someone selects the last ticket on an event the status will switch to sold out for the duration of the users session. If they don’t complete the purchase it will then ‘release’ that ticket again which will switch the event status back. That won’t show up on the front end if users are getting a cached version of the output.
|
