|
Chris
|
February 6, 2013 at 10:13 am
We have noticed that if someone registers for an event then goes back and registers a different person for the same event the previous person is deleted. It sounds like the same thing you just patched today for the backend is happening on the front end as well.
Your help is appreciated.
|
|
Dean
|
February 7, 2013 at 1:41 am
Hi Ed,
This should only occur if the person does not complete the first registration. In effect their session is still opening so they are not registering a new person but editing their details.
Once registration process is completed (by paying or getting to the thankyou screen) the details are added to the database so going back will create an new attendee.
|
|
Chris
|
February 7, 2013 at 7:11 am
We can get to the point where they can either click the invoice button or the paypal button. I assume that’s where most people would stop especially if they were using the invoice. Then if we go back and add another the deletion happens.
Upon further testing clicking the invoice button to download the invoice resolves this. However, this is unexpected behavior because on the previous page we have clicked “confirm registration” and the attendee has at that point been added to the database. Any action that unintentionally delete’s these attendees after the confirm registration button is clicked seems to be a bug to me and totally freaked out my client.
Rolling back a few versions also stopped this problem from happening.
Thanks for your response.
|
|
Seth Shoultes
|
February 7, 2013 at 8:53 am
Hi Ed,
If the event is not free, and the payment is not completed, then the registration isn’t recognized as completed in the system. It helps to prevents that person from going back and registering numerous false registrations.
If you want to allow this type of behavior, you can set the default payment status to pending globally or on a per event basis.
I hope that helps to clarify this a bit?
|
|
Chris
|
February 7, 2013 at 10:08 am
Hi Seth,
Thanks for your reply. I have tried setting the default payment status for the event to pending and the problem still occurs. The previous attendee actually gets overwritten before the second attendee even clicks the confirm registration button.
I still feel that this isn’t appropriate behavior because it didn’t do this in previous versions. Again it is my beleif that if a attendee gets written to the database I don’t feel that anything should unintentionally delete them.
I do appreciate your help and hope I haven’t been rude. I feel your tech support pain. It’s just I am getting reprimanded for choosing your software. I guess all I’m looking for is an acknowledgment that this is a bug and planned to be fixed or possibly a workaround to make my client happy. I was very hopeful the changing the default payment status to pending would work.
Thanks Again for you and Dean’s responses
|
|
Seth Shoultes
|
February 7, 2013 at 10:35 am
Okay. Then this a bug if the pending is not working correctly. I will look into this asap.
|
|
Seth Shoultes
|
February 7, 2013 at 10:59 am
Okay, I found the problem. I commented out a flag and forgot to un-comment it before releasing this 3.1.30.4. I will try to release hotfix later today or tomorrow, but I will show the fix for it here.
Open this file:
/event-espresso/includes/process-registration/add_attendees_to_db.php
Find these lines and un-comment them (remove the “//”):
http://www.screencast.com/t/GgWOuK27pbUl
|
|
Seth Shoultes
|
February 7, 2013 at 11:06 am
@Ed very sorry for the trouble and misunderstanding the situation. I think this fix will work for you. I have tested it and verified the attendee record is not deleted if the payment is marked as pending.
If you would like to continue using version 3.1.30.4, but are uncomfortable changing the PHP, I can make the change for you, or send you the updated file. Please send WordPress admin level log in credentials via this form:
https://eventespresso.com/send-login-details/
Thanks!
|
|
Chris
|
February 7, 2013 at 1:04 pm
Nah I am a front end guy so I am familiar enough with php to do this. I really appreciate your help and you have been very courteous and patient throughout this process.
I have uncommented those lines and it is working properly now.
Thanks again Seth
|
