|
Sala Hiroshima
|
November 6, 2015 at 4:18 am
Hi there!
We have some problems with the quantity of sold tickets not matching the number of registrations/transactions for a specific event (see this image: http://pasteboard.co/1VRWfSA1.png). For example: there are 29 registrants (24 marked as “approved” and 4 marked as “pending payment”). So, we have only sold 24 tickets for this event. But the “sold” field for this ticket shows “44” out of 107. How can this be possible? What are we doing wrong? This is a problem that we need to fix because wrongly we reach the “sold out” status even if there are still tickets available for the event.
Apart from this, we are a theater venue and we would like to be counted as “registered” only for users who have really paid for a ticket (we would like to avoid the “pending payment” registrants to be counted as part of the audience). In summary, if we have a ticket limit of 100, for example, we would like to reach the “sold out” status only when 100 tickets have been paid. How can we do this?
Thanks in advanced!
|
|
Tony
|
November 6, 2015 at 4:57 am
Hi there,
In summary, if we have a ticket limit of 100, for example, we would like to reach the “sold out” status only when 100 tickets have been paid. How can we do this?
That should be the default behavior.
Within your event what is the default registration status set to?
Do you only have a single ticket for that event?
Which payment method are you using?
Are you running any caching plugins on the site or does your host run server side caching?
|
|
Sala Hiroshima
|
November 6, 2015 at 5:19 am
Hi, Tony!
Thanks for your quick answer.
1.The default registration status for the events is “Pending payment”. But even changing this to “Approved” made no difference.
2. Yes, we only have a single ticket for the event.
3. We are using credit card payment method.
4. No, we don’t use any caching plugin. No idea about the server side caching. I will ask.
|
|
Tony
|
November 6, 2015 at 5:23 am
1.The default registration status for the events is “Pending payment”. But even changing this to “Approved” made no difference.
You do not want the default status to be Approved. Approved registrations apply to the sold values by default, Pending Payment registrations do not. So setting that to Approved is the opposite of what you need 🙂
3. We are using credit card payment method.
The payment method you are using on your site is not one I recognize, have you had a custom payment method created?
|
|
Sala Hiroshima
|
November 6, 2015 at 5:29 am
Hi again!
Thanks.
Yes, the payment method we are using is custom created.
|
|
Tony
|
November 9, 2015 at 3:48 am
It sounds like the payment method you are using is triggering multiple updates to the sold values.
If you make a test payment for a single ticket, then pay using your payment method, how much is the sold value incremented by?
If you make a payment using a test account with another payment method, for example Stripe (very quick and easy to create a test account with them) how much is the sold value incremented with that?
|
|
Sala Hiroshima
|
November 9, 2015 at 7:44 am
Hi, Tony!
Yes, it looks like the problem is caused by the custom created payment method. When paying for a single ticket using our custom created payment method the sold value number is incremented by 2 (instead of 1). The strange thing is that it seems that not always is triggering multiple updates to the sold values because the number of sold tickets it’s not the double of the number of registrations… And, even more, the sold value in the “Event Tickets & Datetimes” window is wrong but the number of approved registrations (payed tickets) for the event is correct (when both numbers should be identical). I suppose that the “SOLD OUT” status for the event is activated when the “sold” value reaches the ticket limit and not when the “approved registrations” reaches this limit, right?
Anyway, I will write to our developer to ask if he can fix the custom created payment method.
|
|
Lorenzo Orlando Caum
|
November 9, 2015 at 8:07 am
Hi Sala,
If your developer has any questions, then please ask him to create an issue on our core project on GitHub:
https://github.com/eventespresso/event-espresso-core/issues/new
—
Lorenzo
|
