Olaf Lederer

Hi,
Thanks for reporting this. I guess you didn’t entered the API key first? Or maybe it’s just a different server/hosting version which produces this error.
Anyway the test inside this function is necessary and is added in the latest version I’ve uploaded a few minutes ago.
Let me know if you have any other issues.

I checked the CF API for this function in the meantime.
It’s not so complex to make such a call, but the problem is the limit for the blocking rules (50K). They advice to use custom rules instead:
https://developers.cloudflare.com/waf/tools/ip-access-rules/

50.000 rules looks a lot, but my account has more than 250 domains, this is only 200 rules each.
For smaller accounts it might be interesting. Maybe you like to create some kind of SaaS solution where create some kind of database with all the bad guys (IP addresses).

??

Hi Dinesh,

if a bot’s IP submits?X?number of spam submissions, we have a?Block IP?option that can prevent that IP from accessing the site.

How about this feature:
Make a connection with Cloudflare and add the IP address on the CF blocklist.
This would be an amazing feature for the paid version!

I understand your concerns, while I don’t think that beginners will use them.
Maybe you can add 2 checkboxes? One for the domain and one for the site name?
I don’t like that website owners decide how the tags looks like in the Maileroo dashboard.

EDIT: The beginner doesn’t use SMTP plugins for WordPress websites, they just use the default mail function and complain about bad deliverability ??

• This reply was modified 3 months ago by Olaf Lederer.

Or just a regular input field where you can enter multiple tags, separated by commas?

Like on this page

That would work in my case, but it’s not very flexible.

Please use the value from the option “siteurl” and use parse_url() to get the host name.
This would be the fastest and flexible way to get the website’s (sub)domain name.

Right Jay, you’ve replied 15 minutes before your post here and it took only 7 days

I can confirm that the problem is fixed in version 4.7.1.
When will the stable version be available for download?

Thanks David, I’m glad that I was able to help.

Based on this idea I will check the code for other contact form plugins as well. Most of them have similar action hooks.

I’m glad it’s working now!

Actually you brought something to my attention which is related to the new EmailOctopus API version.
I will check if this version difference might bring up any problems. I didn’t use the new version because they change one thing I don’t like.

The popup form is setup using emailoctopus where as the checkboxes are through your plugin and it has a different api number. I thought there might be an issue with the api so created a new one and linked it and now everything seems to be working.

The popup is from the “regular” EO plugin. The API for this function isn’t used for the other plugin.

Hi,
I found the problem in your footer contact form, the name for the checkbox is not just “newsletter”.

<input type="checkbox" name="newsletter[]" value="Please send me your newsletter">

The square brackets makes it something different. Please check your CF7 form.

For the WooCommerce checkout. This form looks good, it possible to share your settings using a screenshot (mask the API code). The API connection works if you see your EO lists inside the select menu’s on the settings page(s).
Settings > EO4WP or
WooCommerce > Settings > Integrations > EmailOctopus

HI David,

It’s important that you add the API Key and choose a list on the plugin settings screen.
Do you tried the EO4WP shortcode? Does a subscription work flawless while using that one?
If yes, then it is likely that the names of your form fields do not match the variables in the PHP code snippet.
Try also a new Contact Form 7 form with the fields from my comment I posted on the Gist/Github page.

If it’s still not working, please send me a link to your form that can take a look.

• This reply was modified 3 months, 2 weeks ago by Olaf Lederer.

Hi Dave,
right now there is no integration to other form plugins, but since the CF7 plugin has a lot of action hooks, it’s possible to add a subscriber to EmailOctopus using some PHP code in your functions.php file.
I wrote an example snippet and added also an example form into the comments:
https://gist.github.com/finalwebsites/a5f36bd0fc6af000b7c731d5e892c85d

Most important is that you use a checkbox with the name “newsletter” and the “name” and “email” field names need to match also.

Let me know if your have further questions.

Hi,

Thanks for reporting this, I will fix it in the next version.
For now, just click on the update settings button and the warning should be gone.