Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
How do we merge registration page and payment page? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium How do we merge registration page and payment page?

How do we merge registration page and payment page?

Posted: July 23, 2012 at 10:48 am

Viewing 3 reply threads


shunter

July 23, 2012 at 10:48 am

How do I merge the registration form and the payment section.

Currently, our attendees have to:

1-Complete registration information
2-Confirm registration information
3- Then submit payment

How can we merge the pages so that our attendees do not have to leave the first page of for registration?

Also there is a auto-populate feature, that fills out the credit card information on the payment section. How do we get rid of this function?


Josh

July 23, 2012 at 11:31 am

The registration process would need to be re-written, which is exactly what has been done in Event Espresso 3.2. This work has taken months to do, so I will recommend updating to the new version when it’s available.

With the autofilling, which gateway are you using?


Maggie Xu

July 23, 2012 at 1:20 pm

When are you planning on release 3.2? Thanks!


Josh

July 24, 2012 at 7:34 am

Please see this topic for information about the release plans for Event Espresso 3.2: http://staging.eventespresso.com/topic/event-espresso-3-2-screenshots/

Viewing 3 reply threads

The support post ‘How do we merge registration page and payment page?’ 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.

Event Espresso - Staging Server