Posted: March 28, 2014 at 1:05 pm
|
|
I have set up a clone site with all existing Espresso Event registrations and transactions. We are having multiple issues with event statistics and payments. I can provide login information in a private message. Please, let me know to whom and where. ISSUE 1 (which I brought up on the forum, but not solution yet): If you open event “Holding The Man” and look at available tickets. The $35 tickets stats shows that 16 tickets are sold but only 1 registration. ISSUE 2 Payments & Registration. This is where it gets very confusing Check out event “The Book of Mormon” * Question: what’s the point of default registration status? Shouldn’t it be done automatically? That is, if payment goes through -> approved. If payment doesn’t go through ->pending or declined. No? If it’s pending, user should get an email that he can still try to pay for his pending registration? * This is what’s happening. One user has already registered 3 times without being able to make a payment. Look at all transactions by Jeff Cohen or Jeffrey Cohen for this event. (He also paid for another event and it went through ok, so disregard that transaction) Please, advise. We need to set this event to be still NOT sold out. How can we do that? |
|
Hi, I’ll do my best to answer your questions or shed some light on the subject. I do have some questions though: – I want ensure there has not been any data compromised among your work to “clone” a site, so can you shed some light on how you created this clone site? Issue 1 – How many tickets did that one registration purchase at once? Someone can purchase x number of tickets in the same registration. Registrations are not the same as tickets. As long as the names of the registrants are less than the number of tickets then it’s possible that the number of ticket sales will not equal the number of registrations. Issue 2 Different registration status’ are used for different registration processes. They are important and used for different use-cases, not everyone wants their registration system to function as you described (and for good reason). The following statuses are available: Approved, Cancelled, Declined, Not Approved, Pending Payment. – Approved: An approved registration allows payments and may have a completed or incomplete transaction status. The registration is marked as active and a space is reserved for the registrant. So a question or two: – What is the default registration status of “The Book of Mormon” event? If the default registration status is Approved, then it will disregard any need for payment. I hope that helps a little. Maybe more questions than answers right now but I hope those help too. |
|
|
|
Hi Garth, Thanks for getting back to me about this post. No data has been compromised. It was a direct clone using BackBuddy plugin, backup and restore. The issues are on the live site, I cloned the site because this is a website with lots of sensitive private information (HIV+ social group) and I need you guys to look into the backend. ON the clone site I will remove all the users except the ones in question. I will activate a license when you have a stable release. Update from 4.1.8 to 4.1.9 wreaked havoc on the look and layout of the events page and single event page, which I very carefully crafted – I will never do this again without testing. I don’t want my client update the plugin by accident, which they have done before, and destroy all the tweaks I did. But thank you for recommendation. Issue 1 Issue 2 No I haven’t replicated the issue because I would have to make a payment. Poor Jeff Cohen attempted to purchase the tickets several times, he says he’s not able to for some reason. For another event – he did register fine, but with this event. He tried to pay after the payment reminder, and is getting a BLANK Registration Checkout page. |
|
|
Can I give you login information, for you to see for yourself? It would be faster to understand? |
|
Hi, If you send log-in details via https://eventespresso.com/send-login-details/ we can take a look.
Without going into too much detail without confirming on the site, this is likely the root cause of your issues. With EE4 Registrations are independent of Transactions, approved registrations count towards ticket sales even if the transaction has not been complete. ‘Pending Payment’ does not mean you need to update the status for each attendee, it means the Registration does not apply (become ‘Approved’) until payment has been made. This could be from the attendee or the Admin applying the payment. If I understand correctly you want the default registration status to be ‘Pending Payment’ as apposed to Approved. |
|
|
I logged in and looked further into this. ‘Approved registrations’ are not the issue here, although I do believe your default Registration status should be ‘Pending Payment’, defaulting to Approved means they will apply to the attendee limit even if they do not continue with the payment. Pending Payment prevents this. I looked at the event in question and noticed the issue you mentioned, at first I checked the registrations, they seem correct. Then I purged the cache for that event, altered the Datetime limit by 1 (53) and updated the event, the event then became active. I altered the limit back to 52 and updated once more and the event remains active. I couldn’t find any reason for this to happen other than Caching, I notice you have database caching enabled, which I am assuming is the cause although I do not know for sure. If do the same on your live event (try purging the cache and just updating event, if not then alter the limits as I did) you should then have the correct limit numbers. You may want to disable the Database caching and clear the caches, it will likely cause more issues the more you cache, especially when using Event Espresso as there is a LOT of dynamic content. I would recommend only using Page caching and even then adding all of Event Espresso critical pages (Event Espresso -> General Settings -> Critical Pages) to the do not cache list. |
|
The support post ‘EE4: Registrations without payment, ticket stats are not correct’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
