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
Additional Attendees Payment BUG | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Additional Attendees Payment BUG

Additional Attendees Payment BUG

Posted: July 11, 2012 at 7:28 am

Viewing 1 reply thread


mwilkinson

July 11, 2012 at 7:28 am

Hi,

There is a bug in Event Espresso when dealing with additional attendees and invoice payment.

In the pricing.php file from includes/functions/ directory on line 347:

$ice_row = $wpdb->get_row($wpdb->prepare(“select * from “.EVENTS_ATTENDEE_COST_TABLE.” inner join “.EVENTS_ATTENDEE_TABLE.” where registration_id = ‘%s'”,$registration_id));

there is a bug because the SQL doesn’t have the ON for INNER JOIN.

To fix it change it to this:

$ice_row = $wpdb->get_row($wpdb->prepare(“select * from “.EVENTS_ATTENDEE_COST_TABLE.” inner join “.EVENTS_ATTENDEE_TABLE.” on wp_events_attendee_cost.attendee_id = wp_events_attendee.id where registration_id = ‘%s'”,$registration_id));

  • This topic was modified 12 years, 6 months ago by mwilkinson.


Seth Shoultes

  • Support Staff

July 11, 2012 at 7:33 am

Thanks for telling us about this. Just to make sure. Is this in Event Espresso v3.1.24.1.P?

Viewing 1 reply thread

The support post ‘Additional Attendees Payment BUG’ 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