ryanhungate

@apostnikov Sorry you’re having trouble, but these things are typically solved with a few back and forth troubleshooting ideas. Also, could you please tell us exactly where you’re getting stuck? Are there any clues at all in the interface or in your fatal logs that could helps us diagnose further?

If you are having trouble getting past the “authentication” screen, that could be 2 different possibilities.

1. Your web host might be blocked by the Mailchimp API gateway. This happens when folks use shared hosts sometimes, so we have some documentation on how to override the outbound IP address being used by the plugin. Most times, this is all you would need to do to fix the issue.
2. You might have a problem with the Mailchimp Login service, in which the support team could check into that to try and clear any bad auth tokens that might be getting stuck. This is kind of a one off problem we’ve seen pop up in the past, but it does happen from time to time. Please ask support to check into that with your account.

I would start with item 1, just because it’s a very easy way to see if it was the outbound IP address having trouble.

Be glad to help you get things squared up. Also just to clarify, Mailchimp support might have told you on accident that they didn’t develop the plugin, but this specific plugin was. There’s just others that the community has built and they’re used to saying that sometimes, so I apologize for the confusion. 🙂

@rohitrt23 this is not something our plugin does at all. It must be something else on your server doing this. We’ll be glad to help of course but this is a confirmation that it’s not anything we are doing 🙂

@tallsam out of curiosity here from the way your post was worded… if are you seeing additional boxes of “how you would like to hear from us”, the indicates that you have the GDPR fields turned on for this list.

If that was done on accident you’ll just need to turn that off on your list settings and the plugin will catch on within 15 minutes or so to remove that from your checkout form.

If you need them to be used, that’s kind of outside the scope of what we can do right this minute.

Can you please elaborate a little more on what you’re trying to do specifically?

@websavers in an effort to help speed this debugging session up, I would actually recommend that we make a slight change to your plugin manually to see if we can spot the issue. Basically the fix is going to be to add some additional logging into that specific function so we can see the request, and the response. Are you comfortable making a couple very small PHP changes to a function or two while we try to diagnose this? We could of course add this into the next version of the plugin which will make it easier, but depending on how fast you would like to get this resolved, we might need to do something manually first. Let us know if you would rather wait, or if you want to try this first 🙂

@zimios This is showing that you have GDPR fields enabled on your Mailchimp audience. The plugin then knows to insert that on your website because when GDPR fields are enabled, that typically means you need them for getting the consent from customers.

Once you disable those fields, they will go away on the site after the cache expires, or if you go in and save a setting in your Mailchimp plugin, it will recheck quicker.

Let us know if you have any other questions about that.

@mediaformat yes that does make sense. Out of curiosity, how exactly do you see this being built out? Would you just simply want to “turn off all syncing”? Is it that when you migrate to staging, it is pushing new test items into your Mailchimp account? Any explanation would be beneficial as we come up with a solution.

@elvagabundo this is kind of a new one. Since this can easily be resolved with a “cast to a string”, we can include this in our next release no problem. We will get that handled and report back here when it’s complete. If you feel comfortable editing php files temporarily we can give you a quick patch in the meantime to resolve things quicker.

On that last line of the function – you can simply cast both arguments to a string:

On line 801 of:

mailchimp-for-woocommerce/includes/class-mailchimp-woocommerce-service.php

Simply change this line so it casts strings into this function.

return strpos( (string) $current_url['path'] ?? '/', (string) $rest_url['path'], 0 ) === 0;

If you would rather wait for the plugin update that’s perfectly fine, but we know sometimes that timing is critical so this would allow you to fix that particular error without waiting for an update. Please only do this if you’re comfortable editing php files.

@imillenium thanks for reaching out. We don’t change statuses of orders, it’s just the system telling the Mailchimp plugin that there was an update, so we then send that data off to Mailchimp to be used for any sort of automations you have set up. This log simply shows that the plugin “was listening for order updates” and then processed that into Mailchimp.

If you have any other questions please feel free to ask.