|
Patrick
|
May 17, 2015 at 11:40 am
Hello,
I’m wanting a more streamlined registration process for my customers, namely a single page checkout. I know this module exists for EE4, but version four is not mature enough yet and does not include several features I require.
If I wanted to “get under the hood” and try my hand at tweaking the code, what files should I examine.
I fully understand that if I get into modifying the code and something breaks, that I’m on my own as far as support goes. I accept that. I just find the ticketing procedure in EE3 to be less than ideal, and contains steps that don’t need to be there.
|
|
Lorenzo Orlando Caum
|
May 18, 2015 at 12:06 pm
Hi Patrick, could you let us know what you are trying to change?
We’ll then share feedback on if those changes are possible without editing the core plugin.
—
Lorenzo
|
|
Patrick
|
May 19, 2015 at 2:31 am
Hi Lorenzo,
Mostly I want a single page checkout. The purchaser should be able to enter their personal info (name, email address and cell phone) select the quantity of tickets (the name for each of the ticket holders is not necessary,) then enter their credit card info on that same page. Then click PURCHASE and complete the sale.
|
|
Lorenzo Orlando Caum
|
May 19, 2015 at 7:50 am
Thanks for clarifying. That won’t be available in Event Espresso 3 since you collect on one page and then enter payment information on another.
—
Lorenzo
|
|
Patrick
|
May 19, 2015 at 12:35 pm
I understand that this isn’t available by default in EE3. Hence the reason I wanted to try my hand at modifying the files. Again I realize that I’m on my own for support, but I’d really like a starting point for the specific files that communicate with the back end database to process purchases.
|
|
Lorenzo Orlando Caum
|
May 19, 2015 at 1:17 pm
Alright, here is some information to get started.
There are a set of templates in this location:
/wp-content/plugins/event-espresso/templates
event_list_display.php & event_list.php are for the event listing page: example.com/event-registration/
registration_page_display.php & registration_page.php are for the single event pages: example.com/event-registration/?ee=123
An attendee/registrant begins registration on the single event page. After completing that form, they are taken to a page to verify that their information is correct. The template that is used here is the confirmation_display.php file.
If they continue their registration, then their information is recorded to the database once they click on the confirm registration button.
The next page is the payment page and that loads the payment_page.php file. If an onsite payment gateway is used then some of the gateway files are called here (e.g. gateway_display.php).
Once a payment is made, then a confirmation is shown using the payment_overview.php file.
If the multiple events registration add-on is in use then these files are used instead of the registration_ files:
multi_registration_page_display.php
multi_registration_page.php
The shopping_cart.php is also used for selecting the quantities for the tickets / pricing options. Then the registrant/attendee information is collected and then the regular registration checkout takes over so at this time the payment_page.php file would be used and then the payment_overview.php when the registration is finished.
—
Lorenzo
|
|
Patrick
|
May 19, 2015 at 1:19 pm
Thank you so much! 🙂
|
