|
Miyar
|
May 3, 2016 at 3:42 pm
Hello EE team!
We have come to a point where we require some checkout process upgrades. I’m adding a list of what we want to do below:
First change – Ticket Selector Qty Validation
One of the things that bothers us the most is the validation you have for the select input field. The plugin is forcing the page (where the ticket selector is) to reload and then a modal box is loaded at the top of the page. This is very annoying considering the ticket selectors in our website are in the middle of the page. You can take a look here.
Question: is there any way this validation process can be simplified, or at least have the modal box load in that same area where the ticket selector is?
Second change – Number of steps on checkout
We would like to reduce the number of clicks the user has to go through by merging both checkout steps (attendee info + trip info and payment options), into a single unified step where all the info is presented in one area without the need to click on the “proceed to payment options” button to move on.
Question:Is there any way to do that?
Third Change – Billing Address on Braintree
We have braintree (EE addon) installed for CC payment and we are wondering if it’s possible for the address added on the Attendee information to be carried over to this section, and add a selection tick where the user can choose to use the same information as on the first step as billing address, or add a different billing address.
Question: Is there any way to do that?
Please note that we do have in-house developers at hand with experience in WP and PHP theming, so we can tackle the more complex changes, but we need some guidance to understand in which direction to lead them.
Thank you in advance.
–Jess
|
|
Josh
|
May 4, 2016 at 11:54 am
Hi Jess,
It turns out there’s an open ticket in our bug tracker to fix issue #1. I’ll update this thread when the work is ready to be tested.
To answer your question about combining checkout steps, the steps in the Single Page Checkout are modular and there is a filter that allows steps to be added (for example the WP User Integration add-on adds a step that adds a log in form when the event registration requires logging in first) and it allows steps to be removed (an example that shows how to remove the payment options step can be found in this code snippet from our library). If your developer team can build a new step that combines the existing two separate steps, they can use the same hook to remove the existing steps and add the new step.
For issue #3, normally the address field values from the registration form should automatically populate the Braintree billing form. It looks like on your site though, the Address fields are actually custom fields instead of the built-in Address fields that are created when Event Espresso 4 is first activated. You can make it so the Address field values automatically copy over to the billing form by using the standard Address questions that are included in the Address Question group.
|
|
Miyar
|
May 5, 2016 at 8:07 am
Hi Josh, many thanks for your reply!
For issue one, I’ll keep a lookout for your update. Do you guys have an estimated due date on delivery?
For issue 2, I think our dev team can tackle it. However, I know you guys don’t offer customization but if they encounter any issues can we approach you guys via forum?
For issue 3, I think we can do this easily enough. However, I wanted to ask if it’s possible to add a checkbox mark that asks the user to select if they want to use the information added before, or add a new one for billing? Something similar to what you guys do for when a purchase has more than one Attendees.
Thanks for your help!
|
|
Josh
|
May 5, 2016 at 8:20 am
Hi there,
In general if you encounter issues with Event Espresso 4 code it’s recommended to open an issue on the Github repository, the exception being you need a new hook somewhere, then it’s best to do a pull request there.
https://github.com/eventespresso/event-espresso-core/
For issue 3, I get what you’re asking but the gateway billing form doesn’t access the answers to custom question fields. The solution is to use the built in address fields and it will just work.
|
|
Miyar
|
May 5, 2016 at 8:41 am
Hey Josh, thanks for your help, we’ll proceed as instructed.
|
|
Josh
|
May 5, 2016 at 10:13 am
You’re welcome.
|
|
Miyar
|
May 16, 2016 at 10:36 am
Hi Josh, I just wanted to report that your suggestions on using the Default form have worked perfectly. We are currently undergoing the registration steps merging I hope it turns out with no issues.
I wanted to extend my thanks and also ask if there is any further news on issue one of the list on top. Let me know. Thanks!
|
|
Josh
|
May 16, 2016 at 12:09 pm
We’ll update this thread when there is any further news about issue #1 (fixing the redirect after not submitting a quantity to the ticket selector).
|
|
Josh
|
September 28, 2016 at 3:17 pm
Update: The the redirect after not submitting a quantity to the ticket selector was fixed in 4.9.13.p. It will scroll to the Ticket Selector now.
|
