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 Adding additional attendees from EE admin registration miscalculated | Event Espresso - Staging Server
Event Espresso – 3.1.32.2.P
First Data payment gateway
When adding additional attendees via the “add attendee” button on the admin side of EE we get a very buggy experience.
1. The initial registration details for primary and additional attendee are recorded just fine with pending payment status.
2. Paying through the generated invoice link with First Data shows buggy results. With 2 attendees registered we only receive payment for primary attendee via FD even though EE shows both attendees are confirmed paid.
3. Should note: Front-end registration from logged-out and logged-in visitors through FD gateway is perfect. No issues.
After you add the attendees into the system the ticket prices need to be added as well (there isn’t currently a way to add a non-paid amount in the same step as adding the attendees via the admin).
How that works is after they’ve been entered you can follow these steps:
1) Click the primary attendee name in the attendee overview to edit the record.
2) In the right column you can enter the amount for one ticket then click Update Price.
3) Step 2 can be done to the additional attendee record by clicking the link below where it says “Additional Attendees” on the Primary Attendee Record screen.
This will ensure that the correct amount is set via the invoice.
to review some of the changes that affect that area of the admin.
Viewing 5 reply threads
The support post ‘Adding additional attendees from EE admin registration miscalculated’ 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.