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
Attendee Report error / Payments applied to incorrect event | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Attendee Report error / Payments applied to incorrect event

Attendee Report error / Payments applied to incorrect event

Posted: February 28, 2013 at 6:56 pm

Viewing 3 reply threads


Jon Burns

February 28, 2013 at 6:56 pm

I have an event “golf” with 2 registrations, one is w/ a check (not paid) and the other is by CC (authorize.net – paid). The report shows 2 attendees but no $ collected and the “conference” report shows the $60 which should be applied to the “golf” event.

Golf is $60, members only.
Conference $350 w/ $50 early bird discount = $300

more info:
I click the attendee list for “golf”, then click the attendee who paid by CC… it brings up their “attendee data” for the “conference” not “golf” and I can’t find any way to view her gold attendee data.


Dean

  • Support Staff

    •

February 28, 2013 at 11:57 pm

Hi,

I am unable to recreate this.

Is it possible to get your login details in order to look into this?

If so, please send them via http://staging.eventespresso.com/send-login-details/

NOTE: login details need to be Admin level.


Jon Burns

March 11, 2013 at 3:47 pm

I replied to your email and didn’t hear back, any update?


Dean

  • Support Staff

    •

March 12, 2013 at 12:11 am

HI Jon,

I am really sorry, not sure what happened here, your email did come through but did not get actioned.

The report issue seems to be a bug, I will get it raised with the developers but with the imminent release of 3.2 it may be a while before we can resolve this as we need to prioritise workloads.

The other issue, seems to be a result of Multiple Event Registration add on. As the events were bought together it is taking the earlier ID numbered event and using that. It isn’t affecting anything in the database though. I’ll get a ticket raised for it as it is certainly confusing to users.
Viewing 3 reply threads

The support post ‘Attendee Report error / Payments applied to incorrect event’ 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.

The original Forum description...

Status: closed

Updated by Dean 12 years ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server