Same Problem!
I have setup the plugin to not show the checkbox in checkout and to be not activated. Nevertheless, the customer receives a DobbleOptIn Mail after the checkout has been completed.
That breaks the german law!
That’s why I disabled the process by completely removing the hook under “Advanced Checkbox Settings”. As a result, the checkbox is no longer displayed and no more DobbleOptIn Mails sent.
But that can not be the plan …
Further testing shows, that completely removing the hook under “Advanced Checkbox Settings” does not prevent the plugin from sending a DobbleOptIn Mail.
So we don’t have a solution …
what can we do?
Here is a part of the logfile:
2019-01-02T10:41:24+00:00 NOTICE product_submit.success :: addStoreProduct :: #3103
2019-01-02T10:47:08+00:00 NOTICE order_submit.success :: addStoreOrder :: #3624 :: email: werner.muster@msfette.net :: landing site https://xxxxxxx.xxxxxx.com/ :: abandoned cart deleted [b0514f50af0bbb2a8127e997bc68b018]
2019-01-02T10:47:09+00:00 NOTICE double_opt_in :: Updated werner.muster@xxxxxx.net Using Double Opt In – previous status was ‘transactional’ :: Array
(
[FNAME] => Hans
[LNAME] => Muster
)
As you can see, first the user ist correctly set to ‘transactional’ and then, after 6 MINUTES the new event is send, to send the user the Double Opt In Mail.
How can we stop the plugin from doing it …
I am truly amazed at how Mailchimp in its OFFICIAL plugin for the biggest CMS in the world are completely disregarding customer support. You are going to be run over by other companies if you continue like this. Why would I pay for your service when my list gets big enough if my experience with your product and support is so bad??
I can only support the post of @dekadinious. It’s a mystery to me why nobody here answers.
The plugin has been turned off for a month with us.
We really wanted to switch to MailChimp with all our newsletters, but it looks like we’ll have to think again.
The worst support I’ve ever experienced in the WordPress community.
What a Pity!
Hi everyone! Our apologies for the radio silence, we typically handle support requests over in the GitHub repo as for the plugin noted in the forum sticky.
I wanted to jump in and mention that this issue was handled in a previous release. Let us know if you are still having any other problems or need additional functionality out of the plugin.
