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 Smart Single Page Checkout is not working for my free events | Event Espresso - Staging Server
For free events Step 2 will still be shown but is skipped, for paid events a payment method must be selected.
The use ‘Attendee #1’s information for ALL attendees’ is shown within your registration form at the end of the primary attendee’s information – http://take.ms/NEKUh
I ran a test registration (TonyEETest2 is you wish to delete it) and no payment methods were displayed, step 2 simply stated ‘This is a free event, so no billing will occur.’
Is this not the same when you run a test registration?
Oh, I see. I thought if the event was free the button label on step 1 would change to say finalise registration instead of proceed to payment (which would be confusing for registrants).
A registrant/attendee for an event can register for paid tickets and free tickets. If the order contains only free tickets, then they will immediately see a message like this:
I get that. I guess my point is the button on step 1 should be renamed to “Next” instead of “Proceed to Payment” as that doesn’t cover all scenarios. But I will hack the templates to achieve that.
Viewing 4 reply threads
The support post ‘Smart Single Page Checkout is not working for my free events’ 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.