DeveloperWil

I’ve realesed an update 1.0.2 that should fix this.

It works on PHP 8.2 – I’ll update the metadata for the plugin to reflect that. Not tested it with 8.3 because WP core isn’t 100% compatible with 8.3 yet.

@iammobii which email or domains are you filtering out?

Ensure there are no spaces between domains if you have multiple. e.g.
Wrong: @yandex.com, @xyz.com, @abc.com
Correct: @yandex.com,@xyz.com,@abc.com

The 1.0.1 version should correct that however.

This is a bit strange because the Hubspot plugin doesn’t send any information until the form is submitted and the validation from my plugin stops that process by adding an error object to the form.

Can you send me a loom video of an example email going through the form and ending up in Hubspot please?

DM me on Slack or get in touch directly via my website if you don’t want to post that publicly.

Thx, Wil.

Hi @iammobii

Thanks for the feedback.

This is server-side validation. Your Hubspot plugin may be using a lower priority value and firing before this plugin has a chance to validate the form fields.

If you can link to the Hubspot plugin you are using I can check.

This plugin uses the default priority of 10.

You can try to override this plugin’s priority by adding the following two lines to your active theme’s functions.php file or using a code snippet plugin.

remove_action( 'elementor_pro/forms/validation/email', 'elementor_forms_blacklist_validation', 10, 3 );

add_action( 'elementor_pro/forms/validation/email', 'elementor_forms_blacklist_validation', 5, 3 );

I haven’t tested this as I don’t have an active Hubspot subscription.

Let me know if the fix works for you.

Wil.

Thanks @emiliovaldes88 for spotting that. The text domain for translations was incorrect. I’ve pushed version 1.0.1 using the text domain ‘elementor-forms-blacklist‘ and added a new ‘languages’ folder.

Let me know if that solved the translation issue.

Wil.

In the email blocklist, ensure that you don’t have spaces in between the comma-separated list.
e.g.
Wrong: @mail.ru, @yandex.ru, @ru
Correct: @mail.ru,@yandex.ru,@ru

I’ve put a note in to parse spaces programmatically but for now, try removing the spaces and that should work. BTW Elementor forms will automatically reject @ru because it’s not a properly formatted email address. Email addresses require the TLD and another subdomain after the @.

See the recording: https://www.loom.com/share/a29e4c774f3f48608b31be7f2346bd94?sid=8ba0fdc6-cfde-462e-80dd-785898ff22cd

WordPress 6.5.2, Elementor 3.20.4, Elementor Pro 3.20.3, Email Blacklist for Elementor Forms 1.0.0

Let me know if this resolved your issue.

Wil.

@ckadenge I just created a ticket – thanks.

Thanks for getting back to me. There is no staging site. You can see the IP address and URL in the Stripe logs are from the production server.

I have the Advanced Google reCAPTCHA plugin on the checkout, but this made no difference as the checkout is seemingly being bypassed – no WooCommerce Orders were stored in the database.

Currently I have my products in draft mode to prevent this from happening.

I also tried to ban several IP addresses that were appearing in the Stripe logs but that’s a pretty futile approach.

I don’t have a woocommerce.com account so happy to proceed here.

My main concern is that payments seem to be made directly through the gateway bypassing the checkout process.

Thanks for your response.

Here’s the WC System Status:
https://gist.github.com/DeveloperWil/7ca21814c5d843419aea13f497b798d0

Here’s a sample successful Stripe transaction from the logs:
https://gist.github.com/DeveloperWil/3ff0fd43ee94a9def9d288134f16e838

The price $36 is the correct price of one of my products but as you can see from the log, no product meta is transferred to the Stripe transaction and no saved WooCommerce order in the database.

There were over 10,000 transactions over 5 days with just over 200 successful ones which I’ve had to painfully refund.

I have 2FA Google Authenticator on my Stripe account for many years and Stripe also have not detected any strange dashbaord logins – they have advised my API secret has not been compromised.

Let me know if you need any additional information. You can reach out to me directly – my details are on my website at https://zeropointdevelopment.com

Thanks,

Wil.

• This reply was modified 10 months, 3 weeks ago by DeveloperWil.

Updated the link on my website – thanks.

I tested your form but it seems to accept yandex.com emails so I can’t see the error. The plugin works fine on my test account.

View post on imgur.com

Ensure that your CSS is not hiding the error output underneath each Elementor Pro form field.

Are the authors a custom role or the default WordPress author roles?

If a custom role, the new user role must have the same capabilities as a WordPress Author role, specifically:

• edit_posts
• edit_published_posts.

https://www.ads-software.com/documentation/article/roles-and-capabilities/#author

Otherwise they will not appear in the author selection list.

Let me know.
Wil.

I’ve just tested it, and it is compatible with PHP 8.0.22 – the lowest I can go with LocalWP.

The error you’re getting doesn’t mean that the PHP version you are running on your server is out of date. It means the PHP version the plugin expects and has been tested with is PHP 8.1.

You can install it manually using a zip, and it *should* work on 8.0.5. If it doesn’t, and you can’t yet update to PHP 8.1, then perhaps you can bump up to 8.0.22.

The reason I’m leaving it at PHP 8.1 is that there are a few general quirks and edge cases with running WordPress on 8.0, plus the end of life for PHP 8.0 is Nov 26, 2023 (i.e. in 23 days from now).

https://www.php.net/supported-versions.php#:~:text=11%20months%20ago-,26%20Nov%202023,-in%2022%20days

Hope that helps.

• This reply was modified 1 year ago by DeveloperWil.

I don’t understand the request. The plugin blocks email addresses and domains from being sent. It’s part of the validation rules that stops the form from sending. I can’t say “Sent Successfully” when the form hasn’t been submitted. That’s bad UX.

in that case it will just block that single email address “[email protected]”.

If you want to block a whole domain enter “@sample.com”.

Hope that helps.

Wil.