Plugin Author
Soft79
(@josk79)
You can restrict by email, or do you want to restrict to the user(id) that is logged in?
Thanks for the quick reply. I only see an option for “Email Restrictions”, however this is noted to be a list of approved email addresses only, not disapproved. After testing, these emails are allowed the wholesale pricing and are still able to receive the coupon discount.
It would be great to have the ability to limit the user that is logged in. Being able to restrict or disallow by email address would be effective at this point, as wholesale accounts are manually set up/registered by the admin.
Instead of having “email restrictions”, having two separate rules/fields:
“Allow by email”
and
“Disallow by email”
would work nicely.
Cheers
Plugin Author
Soft79
(@josk79)
I will look into this. If I add a restriction to the logged in user and/or role, would that be sufficient?
Plugin Author
Soft79
(@josk79)
Jasshapiro, I’ve just released version 2.1.0-b3 (beta), it has two new features:
– Customer / customer role restriction
– Minimum quantity of matching products
Can you please try it out?
Hmm, last week I updated to version 2.4.? and it actually broke my site. I had to FTP delete WC and install previous version 2.3.13. The error message was something like “Line 17…WC Table Rates…” if I remember right. I just attempted to update to 2.4.4, and went through the same issue. I did spend hours reconfiguring variable pricing. If you go to sky-usa.com, you will see that variable info and pricing is no longer visible on many of the paragliders.
I can sort this out, but would like to be able to update to the newest version safely. Is there a known solution for this? Sorry for the complications, I’d like to get the new extension tested.
Just restored from backup, so errors are gone for now. I’d still like to safely upgrade version though 🙂
Plugin Author
Soft79
(@josk79)
You’re using a Table Rate Shipping plugin that seems to conflict with the new WC version. Try disabling that plugin before updating. Better: disable all plugins and enable one by one to see which is the problem. Check the forum of the faulty plugin to see if more people have issues since the WC update.
I see the extension seems to work with v. 2.3.13. It appears as though there are two ways to ‘allow’ the use of the coupon? Leaving either field blank allows all users and roles, adding specific users and roles allows only the mentioned users and roles? Is there a way to ‘disallow’ a particular role or user? Basically, allow ‘all roles/users except these ______’?
Also, deactivated the table rates plugin, upgraded to latest version, still lost many of my variable products’ info. The good news is it didn’t actually break my site this time :). Is there a way to safely retain all of my variable product info and install latest upgrade? I’ve been reading that others lost variable info if the product was created prior to a certain date??
Plugin Author
Soft79
(@josk79)
No, I wasn’t sure if that would be a useful addition, and don’t want to have too many features in my plugin that might make it too bulky. Do you have that many roles? You could just add the roles you want the discount to apply to, and leave out the others. Can you tell me why you would want to exclude certain roles? Convince me and I might add it 😉
Plugin Author
Soft79
(@josk79)
About the variations, please check the WooCommerce support. I can’t help you with that.
Thanks for the opportunity to convince you 🙂
Yes, very important for me, as I am offering discounted pricing to my dealers. Right now, I can’t prevent them from using their dealer discount (they are logged in as a special wholesale role I created for them) and then having these users add a coupon for an additional discount. I’m currently offering a 10% promotional discount to the general public and do plan on offering more coupons in the future. And if that’s not reason enough, I was planning on making a small donation anyway :). Your timely help has been appreciated!
Plugin Author
Soft79
(@josk79)
Adding only a customer role exclusion restriction would be sufficient?
Exactly. Simply being able to exclude a specific role would be perfect.
