|
dee guiney
|
January 6, 2016 at 7:29 am
Problem: Each of our events has a stock of 16. When someone adds an event to their cart, we want that event to be reserved for them. From our testing, it appears that if two people try to register at the same time for the last ticket of an event, whomever completes the transaction first will secure the event. We want that event to be reserved for them at the moment that they put the event in the cart.
In addition, we want the event (or the whole cart itself) to expire after X amount of minutes.
Does this exist on your EE4 platform?
Bug: As I mentioned before, if two people put an event with only one ticket into their cart at the same time, whomever finishes the transaction first gets the seat…. however, the person who doesn’t get the ticket will receive a warning that the event is now out of stock… however, if they choose to continue to pay for the product, they are allowed to successfully registered. So, in our event, we have cases of selling 17 out of 16 tickets.
Website: http://greenapplecampus.org/locations/franklin-w-olin-college-of-engineering/
|
|
Josh
|
January 6, 2016 at 3:20 pm
Hi Dee,
It turns out there’s ongoing work to add a ticket reservation system to Event Espresso and the Multi Event Registration add-on in order to address the issues you’ve described here. The branch that has the work done so far can be downloaded from our Github repository:
https://github.com/eventespresso/event-espresso-core/tree/BUG-8698-ticket-sellouts
and the companion to the above core branch for the Multi Event Registration add-on can be downloaded via this link:
https://www.dropbox.com/s/5i2sjw07n5jutnp/ee4-mer-BUG-8698-ticket-sellouts.zip?dl=0
|
|
dee guiney
|
January 7, 2016 at 10:21 am
Thanks for the response, Josh.
However, the issues still remain even when I install that other plugin.
I felt like the best way to help you understand the problem is to make short video showing it to you (scree capture). See here: https://youtu.be/F1tVhElR7Ls
Thanks for your help.
zk
|
|
Josh
|
January 7, 2016 at 1:37 pm
It’s actually two plugins you would need to re-install, not one. Did you switch to the BUG-8698-ticket-sellouts branch for both Event Espresso core and Multi Event Registration?
|
|
dee guiney
|
January 11, 2016 at 12:20 pm
Oh… so, I have to replace the core files with a core update.
When is a stable version of this coming out (public release)?
zk
|
|
Josh
|
January 11, 2016 at 1:00 pm
When it’s finished is when. We’ve been working at this for some time now and what we’ve found is these branches work fine overall. However, there are instances where the event can potentially **undersell** because an event could nearly sell out, but the last one or two tickets cannot be sold for a time, but in reality they should still be able to go through and register.
We need to make sure that this new feature does not create new bugs that prevent sales from occurring when they should occur before we merge these into Event Espresso core and MER.
|
|
dee guiney
|
January 11, 2016 at 2:08 pm
Got it!
If I replace the stable CORE with this version, will I have to update the site manually each time?
What’s standard procedure for using pre-release versions of your software?
Thanks for all of your help! 🙂
|
|
Josh
|
January 11, 2016 at 4:01 pm
If you have SSH access to your server, you can actually keep things up to date by cloning the remote, then you update by running git pull from the command line and it will automatically pull the latest changes. We merge Event Espresso Master into the branch, so you’ll also have all other the fixes that get merged to Master.
The same also applies to the Multi Event Registration add-on, but since that’s currently a private repository, we can set you up with access if you have a github.com account. You can request access to the Multi Event Registration repository by filling out this form:
https://eventespresso.com/developers/request-repo-access/
|
