Posted: May 27, 2019 at 8:09 am
The first step should be a simple registration with name surname email password this allow us to put the user into a mailchimp list “checkout start”.the mail and allow us as well to let the user be “logged in”, meaning that if he abandon and then restart the process, all the information added already are stored. About the UI you can use exactly what you can find there https://acquista.webmarketingfestival.it/ with our design of course, we don’t have just the module REGIONE and “acquisto biglietti” anything else is the same so people can register and proceed with the buying, click on terms and condition or login if already registered (login is mail), the login should serve also to bring to the affiliation in case they choose to activate it.
Second step is like secondstep.png so on left part we have the list of soldout + current purchase option, the price and the possibility to add a coupon. In the right part we have the invoicing part exactly the same as secondstep.jpg. in terms of fields. From this page people should be able to do the first checkout with paypal or wire. Clicking on paypal button customer will be redirect to paypal payment and once done to the VIP offer (on/off) while clicking on wire, people should land on a page like bandwire.jpg. If the payment on paypal is suspended we need to have a suspendedpaypalpurchase.png likely page.
Third step is the VIP offer page, we can keep the second step UI but instead of fields we will have some photos/content to be decided.People can decide to pay with the same method or to skip.
Four step is the Thank you page. Here we should show the ticket bought in case of paypal with the VIP status in case they have bought the VIP. In case of bank wire we should tell them they need to wait our confirmation of payment. On the same page we need to have the survay itself and not requesting if they would like to do the survay. And the text “Invita i tuoi amici e vinci un pacchetto VIP” clicking on it, the landing for the affiliation program will appear, consider that anyone registered is already on the affiliation account so we don’t need to require them again if they would like to join
Pretty much all of the above requires custom development as your completely changing how Event Espresso currently works. This isn’t simply a case of moving some fields around or displaying sections a specific way but completely changing the checkout steps and registration flow, which is possible, but not something we can walk you through under support.
I’d recommend you contact a developer familiar with Event Espresso to build this for you, we recommend the folks at codeable for custom development.
Actually you have there:
1\no registration/login required
While i want:
So in the end what i want is to put step 2-3-4 of the given use case together into 1 step, or at least step 3-4 together in one step.
Are you sure it will require much customization work?
You missing some vital steps in your rundown of EE’s default behaviour and assuming that combined data can be easily separated, that makes all the difference.
So lets break down your lists, you put:
This is outside of Event Espresso, if you want to force all of your users to log into the site you’ll need to do that with another plugin.
However, if you want to force users to log into the before registering onto an event, you can do that with the WP User integration add-on. If a different kind of setup though, more on this later.
This would be done on the Ticket Selector which is essentially the starting point for Event Espresso, you MUST select tickets and then submit the form to start the checkout process.
The important part here is when you submit the ticket selection, EE constructs the registrations forms based on the number of tickets and the question group settings for the event.
So, in other words, you select tickets, then submit those tickets and EE generates the forms based on the ticket selection (and other settings) to then display to the attendee.
By default the ‘Primary Attendee’ is the ‘purchaser’ for a group, the invoice will use their details as they are combined, there are work arounds for this using custom questions on the reg form, then using those values in the invoice, but that still does not separate the ‘attendee’ from the ‘purchaser’.
Note that payment options use ‘line items’ built from the registrations and display your options, the promotions apply to the line items of a transaction (again which is constructed from the registrations).
these are only generated once you have the ticket selections, otherwise how does EE know what it’s charging for? It’s a payment step with nothing to pay for if they haven’t submitted a ticket selection.
All registrations must eventually end up at the thank you page, it finalizes the registration(s) and ties everything together.
Now that we know how the above steps work, let’s move onto what you want to do:
Breaking those down:
Site registration rather than event registration right? As mentioned above if you want to lock down your site for members only, you’ll need another plugin to do that.
But… you can use the WP user integration add-on to force users to register/login into the site just before they can register onto an event. It’s a different workflow as the users can view the event etc and must register/login only to actually register onto the event.
So depending on how exactly you want that to work, the above add-on could work for this step, but….
You’re missing the fact that the user submits each of those steps and the next step is constructed from the previous one, and that’s an important point here.
‘number of tickets choice’, ok, you could include that using the ticket selector on a single page, but…
‘attendee details and invoicing details’ as mentioned above, the registration form is constructed from the ticket selection submission which in your case, you haven’t done yet, meaning no EE_Registrations have been created and EE can’t construct the forms without knowing the ticket selection. It’s a chicken and egg situation as your displaying forms before they’ve actually been constructed, so which comes first?
Could you use your own form and then pass that info to EE somehow, sure, but again that’s a lot of custom work.
‘Invoicing details’ could be done, but the primary registrant is still used as the ‘purchaser’, you could use custom questions to replace the values but that ties in with your custom form again.
Now we have ‘payment and discount code’ again all on the same page above, but as mentioned above, those are constructed from the EE_Registrations line items, which haven’t been created yet in your example so EE can’t construct the payment options, or discount codes as there’s nothing yet to build them from.
Knowing the above, I’m pretty sure this will need a lot of customization.
It is possible? Sure! But it is very different from how EE works currently, so will definitely need customizations, pretty much constructing your own checkout process rather than using EE’s single page checkout (SPCO for short) that it currently has.
The support post ‘How to create one page checkout?Event registration, listing, and payment in one?’ 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.