EDD Tickets stock limits

[rpphotography]

I’m having a few problems with the EDD Tickets add-on.

When a ticket has a certain number of stock available, it should prevent more than that being added to the cart in one go, but it doesn’t. For example, if only two tickets are available, the customer can still add 3 or any other number of tickets and successfully checkout.

Another issue is after clicking add to cart and being redirected, if the page is then refreshed, the same quantity of items that had just been added to the cart are added to the cart again, and each time that page is refreshed.

Finally, is it also possible to have separate add to cart buttons for each “ticket” and is it also possible to have this work via ajax?

[Barry]

When a ticket has a certain number of stock available, it should prevent more than that being added to the cart in one go, but it doesn’t. For example, if only two tickets are available, the customer can still add 3 or any other number of tickets and successfully checkout.

Unfortunately you are hitting a bug in the system. A check is made to determine if stock is available, but it doesn’t actual check how much is available. This is clearly a pretty big oversight and we’ll do our best to fix it as quickly as we can.

Another issue is after clicking add to cart and being redirected, if the page is then refreshed, the same quantity of items that had just been added to the cart are added to the cart again, and each time that page is refreshed.

Again, I’m very sorry, but you are hitting a bug. We’ve had to deviate from the normal add-to-cart mechanism EDD uses to facilitate ticket purchases and unfortunately this is a further oversight on that level.

Finally, is it also possible to have separate add to cart buttons for each “ticket” and is it also possible to have this work via ajax?

Definitely possible and that could bring it closer into line with our other ticketing solutions. However we do also need to some extent go with the flow of the underlying ecommerce engine (EDD in this instance) so I’m not sure if we would implement this as a future feature or not,  but please do post a feature request and we’ll certainly consider it.

With regards to the bugs, we’ll certainly get to work on those and will endeavour to update this thread as progress is made.

Thanks for your support and once again please accept our apologies.

[rpphotography]

I can’t use the add-on as it is, so I’m hoping these two bugs can be resolved soonish?

Is there any sort of time frame when we can expect the two bugs to be resolved?

Look forward to your reply.

[Barry]

Hi @rpphotography,

We’re investigating right now and will prioritize a fix for the inventory control issue – as of the two issues that would seem to be of the most importance: I don’t want to offer up a timeframe at this point but we’re certainly aiming to get a fix in place as quickly as we can.

For the issue with duplicate cart submissions, I think realistically that will probably be rolled into the monthly maintenance cycle – unless you are finding it’s a problem lots of your customers are facing and can provide a bit more background on that front?

Thanks!

[Barry]

Hi again: we have just released EDD Tickets 3.4.1 and it is available on the downloads page. Can you try updating and see if this resolves the primary issue (of customers being able to purchase more tickets than should be available)?

Thanks!

[rpphotography]

Hi, thanks for your help with this. Unfortunately the issue i still not resolved…

The warning shows up on the checkout page but it doesn’t prevent the “tickets” being added to the cart. The warning also appears to be only for the last product row when it would make more sense to have a warning appear for each row that has an error. So, if there are only 4 available of one ticket and 10 available of another and a customer tries to buy 20 of each, then it should display a separate error for both and indicate specifically which ones, too.

In my opinion it should show the error on the product/event page rather than redirect them to the cart, but then again this would become more complicated when there are multiple tickets and two of them have not enough stock and the other has plenty (error, error, success)…

The function that checks stock should be a precursor to the adding to cart and the adding to cart should handle each product row independently so the correct errors can be produced and any “add to carts” that should be successful will still be successful.

[Barry]

No, it doesn’t prevent the tickets from being added to the cart. However, what you should find is that it prevents a customer from actually purchasing more stock than is currently available – which was in our eyes the most critical part of this (though please let me know if you find the contrary and customers can actually check out with more stock than is available).

Your other points are completely valid:

• We’ll make a change to ensure additional error messages show up for each relevant line item
• Preventing the user from advancing to the cart page is an interesting idea, but I’d be keen to hear the thoughts of other users (I’m not too sure there is a great advantage to keeping them on the product page when they can make the same adjustment on the cart page) and would recommend posting this item as a feature request on UserVoice

Thanks!

[Barry]

Hi! We’ve now completed some work that ought to address this issue (re multiple errors for each line item where necessary) in our very next upcoming release. Thanks for your patience and if you do hit any further problems with this once you’ve updated please don’t hesitate to let us know in a new thread – thanks!

[Barry]

With regards to a page refresh causing duplicate cart submissions, unfortunately we weren’t able to squeeze this one into our next upcoming release (3.5) but I wanted to drop a note in here to let you know it’s still on our radar and we will try hard to fit it in to the next release instead. Thanks for your support and patience in the meantime!

[Leah]

Hi there,

I just wanted to drop in and update you on the status of this issue. We are working on the upcoming 3.7 release and are happy to say that a fix for this issue will be included. Please keep an eye on your Updates and Plugins pages for an update prompt. If you have any trouble or continue to see this issue after updating, please start a new thread and we can assist you from there. Thank you for your patience while we worked on this issue.

Best,
Leah

[Author]

Posts