Hi @thedetoureffect,
I went to your website to test the subscription form, but I could not go to the next step (CAPTCHA page) due to this error:
Sorry, but we couldn’t connect to the MailPoet server. Please refresh the web page and try again.
This is likely to happen if you have a caching plugin installed, and I believe this may also have affected the CAPTCHA for the issue you mentioned.
Are you using any caching plugin, such as W3 Total Cache, Rocket, etc? If so, please try to exclude the homepage and any other pages where the form is placed from their settings and let us know if it works.
Hi Bruna,
On Saturday I disabled the captcha entirely since it wasn’t working. I’ll clear the cache now. Are you wanting me to enable the broken captcha function again for your testing?
I see that someone else was able to sign up for my newsletter yesterday, Sunday.
Hi @thedetoureffect,
I’m still getting the same error when trying to test subscribing via your form. If you can replicate the issue, please refer to this article: https://kb.mailpoet.com/article/271-error-messages-when-subscribing
Regarding the CAPTCHA, have you tried using the Google reCAPTCHA option instead of the build-in?
I don’t want to exclude every page with the newsletter form from cache because the newsletter form is on every single page across my entire site.
I did try to do Google Recaptcha but it either wasn’t working or I was doing it wrong.
This has never happened before, I’ve always had StackCache and MailPoet. There have been recent theme and plugin auto-updates so it has to be a new conflict from those I would assume. Maybe the recent MailPoet update or Kadence update. I could contact the support people for my theme, unless it’s the MailPoet update that messed it up.
Hi @thedetoureffect,
If you believe this could be a conflict (and I think it’s very possible), please try switching your theme to a default one (Twenty Twenty) and disable all plugins aside from MailPoet, and see if that resolves the issue.
If it does, then enable your theme and all your other plugins one after the other until the issue returns. This will allow you to narrow down what is causing the conflict.
You can refer to this article for more information: How to Test for Theme or Plugins Conflict
Hi Bruna,
Disabling plugins hasn’t helped. However I noticed the following if I choose the default built-in captcha option:
I did a test where I used the audio instead of the visual in order to write the captcha. The audio did not give the same letters that the visual did. If I put what the audio says, I get it right. If I put what the visual says, I get it wrong.
If I listen to the audio, it doesn’t match, and then I hit “refresh” so it will give me a new group of letters, NOW the visual finally matches what the previous audio said. But now the audio will be different. The audio is always one grouping ahead of the visual.
Claire
Hi Bruna,
MailPoet still doesn’t work, people haven’t been able to sign up for my newsletter for over a week. Are the developers aware of this problem?
Hi @thedetoureffect,
Yes, the devs kept investigating this issue and it turns out it seems to be related to a JS conflict with another plugin. They were able to replicate it with SG Speed Optimizer and Async Javascript plugin with a custom configuration.
A ticket has been created already and the fix will probably be released next week. Thank you for your patience!
I’m experiencing the same issue on a fresh install of the latest versions – any workarounds?
This problem is now recurring again. Is it something to do with the last update?
Hi again,
This problem is now recurring again. Is it something to do with the last update?
I haven’t seen other reports of the same issue recently. Can you please do a conflict test as explained here: How to Test for Theme and Plugin Conflicts
You could run this sort of testing on a staging site. If your host doesn’t offer that option, we recommend WP Staging (https://ww.wp.xz.cn/plugins/wp-staging/) for quickly spinning up a new test site.
Looking forward to hearing back from you!
I decided to just get rid of MailPoet altogether. I’ll mark the topic resolved.
Hi again,
I decided to just get rid of MailPoet altogether. I’ll mark the topic resolved.
OK, thanks anyway for keeping us updated.
Cheers
