Ccross-origin object Erro mailChimp

[jonatasemidio]

I'm not able to receive the response of my subscription (mailship form).
Printed Error:
[Show/hide message details.] SecurityError: Permission denied to access property "host" on cross-origin object

I am running my page on Netlify system, and I have checked that subscription is working, the error seams to be on the callback.

Do you know if I need to do something different?

[thomasvaeth]

Can you paste in the URL you put into the _config.yml?

[jonatasemidio]

Yep:
mailchimp_action: https://overhackingview.us6.list-manage.com/subscribe/post-json?u=0c80b66360862ed72c16dcb96&id=76324a0c67

[thomasvaeth]

Hm that looks right. https://github.com/samesies/barber-jekyll/blob/master/_includes/subscribe-form.html just takes that and adds a callback.

And you have the right mailchimp_input for your form?

[jonatasemidio]

For subcription i've just updated the mailchimp parameters:
mailchimp_action: https://overhackingview.us6.list-manage.com/subscribe/post-json?u=0c80b66360862ed72c16dcb96&id=76324a0c67
mailchimp_input: b_0c80b66360862ed72c16dcb96_76324a0c67

Do I need to do something else?

[thomasvaeth]

That's all I have. Can you try putting in what comes with the theme and running it? See if you're getting the same error. Because mine is still working.

[qwizztest]

Ran into the same issue.. Did you ever resolve? It's something with the callback; the subscription actually goes through. My band-aid was to modify the error message, but now my users won't know if there is an actual problem upon subscribing .

[ucpete]

I had the exact same issue using Mailchimp and Netlify. Like @qwizztest, I was getting an error message each time, but the subscription was going through.

I just figured out the issue – the Mailchimp-provided URL looked like this:
http://prefix.location.list-manage.com/subscribe/post?u=<user>&id=<id>

But it needs to point to post-json, not post - e.g.
http://prefix.location.list-manage.com/subscribe/post-json?u=<user>&id=<id>

Now it works.

[thomasvaeth]

@ucpete The example shows to use post-json, so that's probably why I never got this issue. I will update the README in the next few days. I will also check if replace works in Jekyll.

But the person filing the issue said they were using post-json, so I don't know if it will completely solve this. My only other guess if you have to verify your Mailchimp account or something.