MacMacken

You missed the GDPR deadline. Your plugin cannot be used without violating the GDPR.

Only confirmed subscribers (the Subscribed filter in MailPoet), will be counted.

https://docs.mailpoet.com/article/45-2000-limit

So you treat free users better than paying user?

Anyway, let’s forget about this topic. I would suggest, however, that you make automatic deletion of unconfirmed / inactive subscribers a feature.

For your subscriptions, you count all subscribers and not only active subscribers.

The plugin is probably no longer under active development.

(Sending confirmation mails to invalid mails does not help either.)

Has anyone created its own MailPoet subscription form with Google reCAPTCHA?

Anyway, what’s the hook for third-party CAPTCHA integration into MailPoet?

@mailpoet: Bot-friendliness by design is a really strange decision, so be honest!

Thank you!

BTW, MailChimp uses reCAPTCHA on the double opt-in confirmation page, i.e., it is not always sufficient to click the confirmation link in the double opt-in mail but (some) subscribers also have to solve a reCAPTCHA on an additional confirmation page. That seems to work pretty well!

OK, I got –?even if a little bit late …?the MailPoet developers suggest to use this plugin to add a CAPTCHA to MailPoet subscription forms, however, this plugins is not really made for this purpose (together with Contact Form 7’s CAPTCHA support). So if you want to use Contact Form 7 only as a MailPoet subscription form, you have to use hidden text fields and you have to send a message to somewhere …

Sorry for inadvertently hijacking this support forum, Jesse!

@jesse: Is the your-name mandatory? (I have not used a name field so far since the mail address is sufficient.)

In any case, Contact Form 7 always reports that the mail could not be sent. Is it correct to use the default ‘submit’ button?

[email* your-email placeholder akismet:author_email "E-Mail-Adresse"]

[mailpoetsignup* mailpoetsignup-56 mailpoet_list_5 default:on "Newsletter"]

<div style="margin-bottom:30px;">[recaptcha]</div>

<p>[submit "Subscribe"]</p>

Sergej, wie viel würde es kosten Dich dafür zu bezahlen, dass Antispam Bee-Plugin zu reparieren, damit es wieder so wie Version 3.2 funktioniert anstatt Kommentare zu verunm?glichen?

Leider besteht das Problem auch in WordPress 3.4 und mit der neusten Antispam-Bee-Version weiterhin. Schade!

The problem is still reproducible with WordPress 3.4 and the latest Antispam-Bee version. Bummer!

I don’t use post thumbnails. Why should I enable I feature I don’t use?

I would expect that your plugin checks whether post thumbnails are in use or not. That shouldn’t be that difficult. Anyway, I switched to a competitor’s plugin that doesn’t crash if post thumbnails are not used.