|
Amy Swift
|
July 9, 2012 at 7:46 pm
As extensive as this plugin is, it seems there is some basic options that are either missing or not so clear on how to implement.
I have scanned the documentation and could not find how to set up an event where you cannot Register before paying. The event I’ve set up has several prices and there is no clear place where to choose one when registering.
What I am trying to create is an event which when displayed on the site, shows the member and non member pricing, offers to log in if a member, and that when they click register/buy tickets it takes them to a payment process which once they pay they are registered to the event.
I do not understand the way it is currently set up.
What am I missing?
Please advise.
Thanks
|
|
Josh
|
July 10, 2012 at 8:48 am
The system will accept all registrations, however it will not complete them unless they are paid. This means that unpaid registrations do not reserve a space/count toward the max limit of attendees for the event. The default payment status can be set to pending or even completed if you wanted to override this.
Please see these guides in the documentation for more info on:
creating events
member pricing
setting up a payment gateway
|
|
Amy Swift
|
July 10, 2012 at 11:40 am
I have read the docs and I still don’t understand. so there is no way to set it up so that purchasing the tickets IS the registration? will it always be register first and pay after?
|
|
Peter
|
July 10, 2012 at 11:59 am
Amy,
I think it does what you want. In General settings set the default payment status as “incomplete” and “Send registration confirmation emails before payment is received? to “No”. Now anyone registering will not receive any notification of registration until they pay and the slots will not be allocated until they pay also. Effectively they register and pay, If they don’t pay they are not registered, but you do get contact information which could be useful.
|
|
Amy Swift
|
July 18, 2012 at 5:55 pm
Hi Peter,
These are already the settings. The problem is not whether or not they receive an email before payment, it is that registering and payment are 2 separate processes, and not only that, they are separated by a middle step, who’s button is called “complete registration”.
This does not make sense at all. filling out your name and email should be on the same page and in the same process with paying. and even in the case of an external payment system like paypal, it doesn’t make sense to have a 3 page registration process (including paypal) in which the second stage indicates as if that step completes the registration.
if this is just the way it’s built well, maybe I need to change the the words Complete Registration to Continue to Payment. but otherwise this is just confusing. this would likely cause many, none complete registrations.
|
|
Josh
|
July 18, 2012 at 6:31 pm
Hi Amy,
We’ve put a lot of work into Event Espresso to make it flexible enough to fit a wide variety of use cases. Some events are free, so they don’t go to a payment page. And some set up payments for at the door and use Event Espresso for the registration only.
Based on feedback similar to what you wrote above, we’ve completely refactored Event Espresso 3.2’s registration process to handle the payments and confirmation differently. The online payments have been moved forward with the confirmation after. See this screenshot:
More screenshot comparisons between Event Espresso 3.1 and 3.2 can be found here:
https://eventespresso.com/topic/event-espresso-3-2-screenshots/
If you want to change the button text on the confirmation page, open up confirmation_page.php and change the text strings on lines 132 & 134 where it says ‘Confirm Registration’.
|
|
Amy Swift
|
July 18, 2012 at 6:58 pm
Yes! this makes so much more sense, and looks a lot better.
ok but this version is not out yet correct? is there an eta? (i don’t want to customize a lot only for it to be fixed by itself in the next version)
thanks
|
|
Josh
|
July 18, 2012 at 7:09 pm
It’s not out yet and we do not have an ETA as there is much work left to be done. I would suggest going with the necessary customizations while keeping the new version in mind so you don’t put a ton of customization into something that will end up being replaced within a few months or so.
We’ll be releasing an early alpha preview release for those who would like to start making customizations to 3.2, so keep an eye out on the blog for when that’s ready. Or sign up for our newsletter.
|
|
Amy Swift
|
July 18, 2012 at 7:11 pm
ok thanks
|
