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.35.P - change log details | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › 3.1.35.P – change log details

3.1.35.P – change log details

Posted: September 11, 2013 at 6:43 am

Viewing 2 reply threads


Cristi Constantin

September 11, 2013 at 6:43 am

Hi, I would like to know, as part of 3.1.35.P change log, what do you mean by “Removed the “Completed” payment status”?


Josh

September 11, 2013 at 7:27 am

Hi Christ,

What it means is that the default Payment status cannot be set to Completed. The system default is “Incomplete” which gets set to “Complete” automatically by a payment notification; In cases of offline payments the payment status can be set to completed manually be the admin.

The Pending default payment status can be used in cases where you want the registration to count toward the total limit of registrations for an event.

The trouble with the Completed default payment status was it did the same thing as Pending but added the unintended consequence of not sending out notification emails after someone registered and paid, since the change from not complete > complete is what triggers the email notifications.


Cristi Constantin

September 11, 2013 at 7:31 am

All clear now, thanks.
Viewing 2 reply threads

The support post ‘3.1.35.P – change log details’ 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 Cristi Constantin 11 years, 5 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server