You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Depending on the settings of Firefox or Brave, i.e. how intense the ad-blocking etc. is, the newsletter signup will throw an error and not allow someone to signup. Right now it will at least communicate this to them with an alert.
I reset my firefox browser to factory settings and was able to sign up okay since all my blocker settings were chilled out but this is definitely unfortunate / something we'll want to address.
One thing I didn't try was embedding the entire mailchimp form in like was mentioned in one of the issues...I wasn't sure how that would play with Gatsby. Would be my first step to looking into this.
The text was updated successfully, but these errors were encountered:
kendallstrautman
changed the title
Error on newsletter signup with tracker-blocking browsers
Newsletter signup: Error with tracker-blocking browsers
Oct 8, 2019
I tried to sign up for the newsletter and received this "Looks like your browser is blocking this. Try to disable any tracker-blocking feature and resubmit.". I have no Ad Block, so that's pretty weird. Got a 404 in the console, and the request Timed out.
Depending on the settings of Firefox or Brave, i.e. how intense the ad-blocking etc. is, the newsletter signup will throw an error and not allow someone to signup. Right now it will at least communicate this to them with an alert.
See benjaminhoffman/gatsby-plugin-mailchimp#45 & benjaminhoffman/gatsby-plugin-mailchimp#34
I reset my firefox browser to factory settings and was able to sign up okay since all my blocker settings were chilled out but this is definitely unfortunate / something we'll want to address.
One thing I didn't try was embedding the entire mailchimp form in like was mentioned in one of the issues...I wasn't sure how that would play with Gatsby. Would be my first step to looking into this.
The text was updated successfully, but these errors were encountered: