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
Overpaid Status Not Reserving Event | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Overpaid Status Not Reserving Event

Overpaid Status Not Reserving Event

Posted: March 2, 2013 at 10:16 am

Viewing 3 reply threads


Peter

March 2, 2013 at 10:16 am

A client overpaid, they did not use the discount code. The transaction went through on PayPal for the full amount and their registration reserved the space. I changed the price charged in the View/Edit Payment and am going to refund the difference, but on changing the price the status went to Overpaid and their places no longer showed as reserved. Surely Overpaid should still show as places reserved.


Dean

  • Support Staff

    •

March 3, 2013 at 11:32 am

Hi Peter,

Agreed, overpaid should be marked as completed/pending to reserve the spot. I’ll get a ticket raised on this, and thank you for bringing it to our attention.


Peter

March 3, 2013 at 2:40 pm

Thanks


Josh

March 4, 2013 at 11:11 am

The ticket has been raised.
Viewing 3 reply threads

The support post ‘Overpaid Status Not Reserving 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 Josh 11 years, 10 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server