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
3.1.28 Edit Payment BIG Bug! | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › 3.1.28 Edit Payment BIG Bug!

3.1.28 Edit Payment BIG Bug!

Posted: October 25, 2012 at 7:44 am

Viewing 3 reply threads


James Mojonnier

October 25, 2012 at 7:44 am

I changed the payment information of one registrant from Pending to Completed, and it switched ALL the registrants of that event to Completed. Now I have NO idea who is and is not actually a paid registrant. Can this be undone?? I just reverted to 3.1.27.1, but the attendee list is the same! ACK! PLEASE HELP!


Seth Shoultes

  • Support Staff

    •

October 25, 2012 at 8:09 am

James,

Very sorry for the trouble. We just found out about this bug ourselves and are working to fix it ASAP. It happened because of a one letter difference in one of the database queries.

We can try to help you get this fixed. Can you contact your host and request the latest server backup? Hopefully that will contain a backup of the database, that way we can try to restore what was there previously.


James Mojonnier

October 25, 2012 at 10:05 am

Ok, I have the DB backup file. What’s next?


Seth Shoultes

  • Support Staff

    •

October 25, 2012 at 10:25 am

I’ll send you an email so we can send files back an d forth etc.
Viewing 3 reply threads

The support post ‘3.1.28 Edit Payment BIG 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.

The original Forum description...

Status: closed

Updated by Seth Shoultes 12 years, 4 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: resolved
Event Espresso - Staging Server