Scott DeLuzio

Thank @scalen and I apologize for the issue there. I just released version 1.5.1 with that code removed. Once you update it should be resolved.

Thanks for the great review @drigis3

Thanks for noticing this @drigis3. I have an update I’ll be releasing shortly that will address this issue. Short answer is the expiry_date meta is incorrect in the plugin and instead needs to be date_expires. Additionally, the date_expires meta is looking for a timestamp (such as 1602547200) and the $expDate in your example would produce a human readable date (such as 2020-10-13).
Regardless, I’ll have a fix released that will allow you to set the number of days before the coupon code should expire. In your example, you could set 60 days and the code would automatically expire 60 days from the date it is created. The update should be available in a few hours.

Great, I’m glad you got it working, and thanks for that feedback. If you have any code suggestions, you can submit a pull request to the plugin here: https://github.com/AmplifyPlugins/subscriber-discounts-for-woocommerce

Hi @3bsstudio
Does your Mailchimp list have double opt-in enabled? If so the email may not have been subscribed to the list, and therefore the webhook wasn’t triggered.

Also, double check that the Mailchimp key in the plugin settings matches the key used in the webhook URL.

1. Go to WooCommerce > Subscriber Discounts.
2. In the Mailchimp Key, enter a random string of letters and numbers.
3. Copy this string to use later.
4. Login to your Mailchimp account.
5. Click Audience > Audience Dashboard.
6. Click View Contacts button (towards the right).
7. Click Settings > Webhooks.
8. Click Edit next to the webhook you set up, or if you haven’t set one up click the Create New button.
9. In the Webhook URL field, enter https://yourdomain.com/?trigger-special-discount=true&discount-key=xxxxxxxxxxxx Change yourdomain.com to your actual domain name, and change xxxxxxxxxxxx to the random string you entered in the plugin’s settings in step #2
10. Under the “What type of updates should we send?” section, only check subscribes.
11. Under the “Only send updates when a change is made…” section, check all three boxes (by a subscriber, by an account admin, via the API). This might have been where your problem was, if your signup form uses the API and you didn’t have that checked for example.
12. Click Update

It should work after going through those steps.

Also, another thing to look out for is that the email address you are attempting to subscribe to the list may already be subscribed, so Mailchimp won’t trigger the webhook. In testing, you will want to confirm that the email address you are attempting to subscribe to the list isn’t already subscribed before testing, then confirm that it is subscribed after testing.

If that doesn’t work, let me know and I’ll see if I can help troubleshoot further.

Hi @tsunamski thanks for the suggestion! Update to version 1.4.0, and it should give you that option in the settings.

It really doesn’t matter whether or not you’re using a multisite. The issue is that Mailchimp sends out to all of your webhooks anytime someone subscribes to your list. The data that the plugin receives doesn’t really tell it which site the subscriber is coming from so the plugin isn’t able to conditionally create the coupon code.

The best option in your case would be to split your Mailchimp list into several accounts with one webhook per account. Otherwise it will continue to create multiple coupon codes for each subscriber.

@dhruvsompura are the three webhooks all in the same Mailchimp account? If so, I think they will all be triggered, no matter which store the subscriber comes from. If so, that is why you’re seeing three emails being sent. The best option would be to have three separate accounts, one for each store so that the webhooks only are triggered when a subscriber comes from that store.
Alternatively, if you don’t want to use three accounts you can use a third party service like Zapier that can receive the subscriber information from Mailchimp, then fire off a specific webhook if the subscriber came from a certain store. So you would have Zapier check the Mailchimp subscriber information to see where they subscribed from (maybe from a tag or some other field), then send the webhook only if the subscriber’s source matches that store. Note: I haven’t tried this method before, so I don’t know how well it will work.

At the moment we don’t have this feature built in, but we will add it to the feature request list for possible future implementation.

Hi @spamis yes, the pro version of the plugin can do this. It is not available in this free version, but the pro version is capable of handling this. If you need assistance with the pro version, please use our pro support form for a faster response.

Thanks for the great review @markxkr

Hi @crindima no, that is not possible with this plugin.

Hi @deathbydisco yes, this plugin and the pro version are both still supported.

The most recent update to this plugin was a few weeks ago, and the pro version had an update a few days ago.

Both are actively supported through our email support at https://fullscreenbackgroundimages.com/support/.

Did you have any questions about either plugin?

I’ve actually updated the plugin (v1.0.5) that will display a notice if no shipping methods are available. This should resolve the issue for you. If not, please let me know.

Thanks!!

Hi @isaumya thanks for the question!

This plugin is somewhat limited in that it only allows you to add one conditional field to the checkout page based on the product in the cart.

We have a pro version that is exactly what you’re looking for though. You can have as many fields display for as many products as is necessary on your checkout page.

You can check that out at https://conditionalcheckoutfields.com/downloads/conditional-woo-checkout-field-pro/