Posted: February 2, 2017 at 11:52 am
|
Dear, THanks |
Hi, What is the problem exactly? We’re you expecting them to fill out the payment form before filling out the registration form? |
|
|
i would expect that the registration is only inserted in the database when clicking the ‘finalise payment’ button as third step in the registration process ? a lot of people just check out the order forms without proceeding to payment.. |
|
plus the email confirmations are not sent at this first step so people don’t know they already registered by clicking the first ‘register’ button? |
The registration form information is inserted into the database when the form is submitted. This allows for paying later (e.g. some sites use the pay by invoice option). Technically though, their registration is not complete. The registration process has been started, but their registration isn’t holding any tickets or spaces available for that event. So even if they come back later and start another registration, they’ll only have access to the tickets they actually pay for. |
|
|
To clarify, I’m talking about ordering tickets and my set up does not require registering as a user. I just checked and what I explained happens when I’m logged in as admin. So then from the moment I click ‘Register’ I’m in the database, which is still strange (?). When logged out, it does not happen when clicking the ‘register’ button on the tickets page. However, when looking at some orders, there are some with no email confirmations when I look at th related messages. Is this normal ? I have a lot of double orders … how prevent this ? |
The registration form captures the registration information. So when they click on the submit button at the end of the registration form, it adds the registration info to the transaction. Taking one step back, the transaction actually starts when they submit the ticket selector. But if they abandon the process and don’t go on to fill out the registration form, those transactions get cleaned up later. You’ll need to find out why people are coming back to register again later to find out how to prevent it from happening. For example, is the registration form lengthly, so they come back at a later time when they have more time to fill out the form? There may be other reasons, and you can follow up with them to find out. |
|
|
After some inquiries, it seems that a lot of people trying to book a ticket receive an error message at some point. They don’t receive email confirmations and so they restart their booking. In the back end though they are registered from the first try but I don’t see related email communication. Around 10% of the bookings seem doubles. What could cause the error messages ? Maybe clicking too soon on the finalise booking button when the selection of the payment method is still in progress ? |
Can you find out the exact error message? If we know the error message we can make a better guess on how to fix the condition that causes the error message. |
|
|
Hi, one of the problems (I don’t knoz if it’s the only one) is that the process hangs when selecting the payment method. The wheel keeps turning and nothing happens. I had this customer click the cancel link then and then came the message that the registration was cancelled, although that in the back end the data was still there (though without related messaging so no confirmation email has gone out). |
There may be some fatal errors on the server happening at that point when the wheel keeps turning. One possible cause is the WP memory limit was hit. You can increase the amount of memory available for WordPress by following this guide: |
|
|
i set the encode session to yes. for now no error messages. |
That’s actually expected behavior. The data should not get deleted if they cancel a registration. |
|
The support post ‘Registration already at selecting payment method and before 'proceed to payment'’ 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.