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
Promo Code Properties Request | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Promo Code Properties Request

Promo Code Properties Request

Posted: October 6, 2012 at 8:49 am

Viewing 6 reply threads


isavage

October 6, 2012 at 8:49 am

I’d like to make a feature request for the Promotional Code aspect of EE:

Limit # of uses per code & set an expiration date per code

Can you tell me if there’s a way to patch this in till a future update includes these features?

Thanks!

IS


Josh

October 6, 2012 at 1:57 pm

Hi there,

Event Espresso 3.2 has these features and can be downloaded here:

http://staging.eventespresso.com/support/event-espresso-3-2-pre-release/


isavage

October 6, 2012 at 2:07 pm

But it says that I cannot update my existing version with this one… What do you suggest I do with the Alpha, exactly? I like the idea of trying it out. But, if I can’t use it on my website, then…?


Josh

October 6, 2012 at 2:23 pm

Here’s what I can suggest:

You can download it, install it on to a test server and test out the new coupon code features. If you like how it works you have all the code in front of you to patch into 3.1 if you so desire. We don’t have the development resources to add these new features to 3.1 at this time.


isavage

October 6, 2012 at 2:38 pm

Alright. Fair enough. I don’t know enough about code to know how to implement a patch like this. But, I’m good at following directions ;-)

Could you tell me what those steps would be?


Josh

October 9, 2012 at 6:59 am

In a nutshell, the functions that would be modified are all in /includes/admin-files/coupon-management. There’s quite a bit of code there so I would recommend having a developer take a look at it.

I can track this as a feature request for now and if we have the resources it may be possible to backport the feature into 3.1. At this time, we have to finish up some needed refactoring of 3.1’s registration process as well as the development of 3.2 so we have very limited development resources to add new features to the 3.1 branch.


isavage

October 9, 2012 at 7:05 am

Understood. Thanks.

Viewing 6 reply threads

The support post ‘Promo Code Properties Request’ 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.

Event Espresso - Staging Server