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
default payment status | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › default payment status

default payment status

Posted: June 18, 2013 at 8:19 am

Viewing 1 reply thread


Randy Tantlinger

June 18, 2013 at 8:19 am

Can you tell me what the best default payment status should be set to per event?  Should they be set to incomplete?  What is the difference between setting it to incomplete and setting it to “no change”.


Josh

June 18, 2013 at 10:19 am

Hi Randy,

When it’s set to “No Change” it will use the status set in Event Espresso>General Settings. It’s up to you to decide whether it’s best to use Pending or Incomplete. Incomplete will make it so that seats are not reserved until payment is complete. Pending reserves the seat before payment is made.
Viewing 1 reply thread

The support post ‘default payment status’ 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, 7 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server