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
Is it safe to change Early Registration discount amount/dates? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Is it safe to change Early Registration discount amount/dates?

Is it safe to change Early Registration discount amount/dates?

Posted: July 3, 2013 at 2:23 pm

Viewing 2 reply threads


Rob Mougey

July 3, 2013 at 2:23 pm

Only one date range and discount amount is allowed for Early Registration, but we want to have more than one. E.g. Jan $80, Feb $90, Mar-Sep $100. Is it better to:

a) Set up one event with the initial cutoff date and dicount amount, and when that date arrives, change it to the next cutoff date and discount amount, or

b) Set up multiple event copies with different prices and different availability dates (would prefer not to), or

c) Something else I have not thought of?

Thanks!


Jonathan Wilson

  • Support Staff

    •

July 3, 2013 at 2:29 pm

Hi Rob,

I personally think that option A is best. I’ve done this successfully on personal projects because we don’t have the cutoff functionality like you want built in.


Rob Mougey

July 3, 2013 at 2:43 pm

Thanks for the quick reply. Just wanted to make sure it would not cause any confusion when looking back at past purchases or anything.
Viewing 2 reply threads

The support post ‘Is it safe to change Early Registration discount amount/dates?’ 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 Rob Mougey 11 years, 6 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server