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
Bug Report: Volume Discount Doesn't Adjust for Some Cart Removals | Event Espresso - Staging Server

Support

Home › Forums › Pre-Releases › Bug Report: Volume Discount Doesn't Adjust for Some Cart Removals

Bug Report: Volume Discount Doesn't Adjust for Some Cart Removals

Posted: January 8, 2014 at 12:27 pm

Viewing 6 reply threads


novaopen

January 8, 2014 at 12:27 pm

Volume Discount Doesn’t Adjust for Some Cart Removals. Example if the percent discount totaled $20 and items are removed then it still stays at $20. Further, unless a refresh is done, in some cases when # of items drops below the threshold the discount still remains even at checkout.

Fresh Install of WordPress 3.8, EE core, MER, and volume discount only. No other plugins. 2014 Theme and Base Themeroller. No custom PHP or CSS. Bluehost Shared. 96 MB wp_memory_limit. PHP 5.4.22 FastCGI


novaopen

January 8, 2014 at 12:38 pm

I just checked to see if issue exist with PHP Single rather than PHP FastCGI and I still had the issue. I am setting the discount through meta field option.

Hope this helps. I realize this is a Pre-Release plug-in.


novaopen

January 8, 2014 at 12:42 pm

Any chance that EE 4 will be available in the next two weeks? I have a site launch on 2/1/14 and EE 4’s feature set is more in tune with my needs. I suspect that an automated upgrade from 3 to 4 is going to be problematic.


novaopen

January 8, 2014 at 10:38 pm

Just wanted you to know I just signed up for VIP. Thought I’d try to be an active participant with a few Tips and Bug Reports, I have discovered. Of course Help is always nice when I need it.

Only had EE for a couple days. Took forum advise and switched from GoDaddy to BlueHost, too.


Dean

  • Support Staff

    •

January 9, 2014 at 12:40 am

Hi Michael,

Thanks for pointing that out. I ran some tests but couldn’t replicate this. Is it happening with just specific events or in specific circumstances?

Could you provide your settings for Volume Discount and the event meta field so I can try to replicate your set up more closely?

Regarding EE4, the best answer I can give is, soon! We are working hard to get the first version released, but as with any mammoth project, there are a million working parts that all need to be tested, fixed, and improved.


novaopen

January 9, 2014 at 8:36 am

I’ve uninstalled the VD plugin (now that’s a name for a bug), so this is from my memory:
1. Meta field key – event_bundle
2. Meta value – 1
3. Threshold (I know it is called something else) – 2
4. Categories – I used a couple
5. Events – I used a mix. Nothing special. Some with meta value set to 0, 1 or no Meta key/value (which defaults to 1)

Hope this helps.


Dean

  • Support Staff

    •

January 9, 2014 at 11:50 am

Hi Michael,

We called it VOD for good reason!

Thanks for the information it helped a lot. I have recreated this and will raise a developer ticket to look into it.

Thanks for letting us know about it!
Viewing 6 reply threads

The support post ‘Bug Report: Volume Discount Doesn't Adjust for Some Cart Removals’ 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.

Home to preview versions of next-generation Event Espresso products.

Status: closed

Updated by Dean 11 years ago ago

Topic Tags

Tagged: ,

Notifications

This topic is: resolved
Event Espresso - Staging Server