Viewing 8 replies - 1 through 8 (of 8 total)
  • Getting the same thing!

    Same here! It looks like attempts eventually started to go through, but I’m not sure why this request was being made in the first place. Eager to hear more info on what went wrong. :/

    I don’t get the “Oops” message, but I am getting that same error log. Which I suspect is why I am having the problems listed in my other thread here:

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hello,

    MailChimp.com has changed some rules at their end due to which, if you have double opt-in enabled, and if the user does not confirm their email but submits the form again then MailChimp returns the 405 error that you can see in our logs. This applies to MailChimp.com hosted forms too.

    We will discuss with MailChimp about a possible solution.

    Thread Starter DoggHousePro

    (@dogghousepro)

    thanks for the reply. the form definitely worked properly the first time i filled it out, so that makes some sense. would like to keep the double optin functionality box ticked on though and not receive errors in the future (especially when testing), hopefully a future update can work around this. if not, i appreciate your response, the plugin functionality & integration is really great.

    Would this error show up if the user is trying to sign-up for the very first time and double opt-in is enabled too?

    I’m getting this error any time I try to add a user from my WooCommerce checkout form, whether they are new or existing, and the only thing that you’ve said that seems to affect that, is if double opt-in is turned on.

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hello,

    We are still looking into this. This is also affecting the forms hosted by MailChimp.com so we will discuss with them about some solution and also add a custom message that you can show to the user. Please allow us a few days to get back to you.

    Plugin Contributor Harish Chouhan

    (@hchouhan)

    Hello,

    We have released an update to our plugin that resolves this issue. Please update the plugin and test again.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Oops. Something went wrong.’ is closed to new replies.