Dnesscarkey

Dear Kingyyyy,

Thank you for pointing this out.

I will work on this issue and send a new update by Monday.

Thanks!

Dear bigdog044,

Thank you for your wonderful review! We’re glad to hear that you found easy to use and enjoyable. Your feedback means a lot to us!

Dear Mrkoetje,

Thank you for the update! We’re glad to hear that the issue has been resolved.

Best regards,

Dear Onionmn,

Unfortunately, our plugin does not have a feature to redirect blocked visitors to a specific URL. We’re sorry for any inconvenience this may cause.

Best regards,

Hi Chris,

Thank you for reaching out and for your suggestion.

We will check the Bitform plugin, and if the necessary hooks and actions are available for integration, we will try to add support in the next release.

We appreciate your input and will keep you updated on any progress.

Best regards,

Hi,

That’s definitely unusual behavior. Do you have any caching plugins that serve cached pages as static HTML? These types of plugins can sometimes cause issues by displaying admin-only content to non-logged-in users.

Could you try disabling your caching plugin temporarily and see if the issue goes away? Let me know the results, and I’ll be happy to assist further.

Best regards,

Hi,

Thank you for reaching out.

If you’re using the Extended version of WP Armour, please ensure that the Lite version is also active, as the Extended version relies on the core functionality of the Lite version.

Additionally, if you’re using any caching plugins, please clear the cache to make sure the latest JavaScript files are being served correctly.

Let me know if the issue persists, and I’d be happy to assist further.

Best regards,

Hi @mrkoetje

It looks like our CSS files are not being loaded properly. We have included CSS to hide the extra form field, but old cached CSS files from caching plugins might still be served.

Please try clearing your website’s cache and doing a hard refresh (Ctrl + Shift + R). This should load the latest version of the CSS.

Let us know if the issue persists.

Best,

Hi,

We have fixed this this in version 1.37. Please update to 1.37.

Thanks

Hi Anjoid,

I can see that the form has our honeypot fields and they are being checked during submission. Could you try regenerating the honeypot field name from our general settings and see if that helps?

Also, how frequent is the spam? Our plugin can’t block submissions if they are done manually. Our works for submission initited by Spam Bots.

Best,

Hi

I checked the console on your website and found the following errors:

1. Uncaught ReferenceError: wp is not defined
2. Uncaught TypeError: Cannot read properties of undefined (reading ‘i18n’)

These errors indicate that some essential WordPress scripts might not be loading correctly. This could be due to Autoptimize or another optimization plugin, which might be blocking necessary scripts.

To troubleshoot, please try temporarily disabling Autoptimize and see if the issue persists. Let me know what you find, and we can proceed from there.

Best regards,

Hi,

Thank you for reaching out.

Could you please share the URL of the page where QuForm is being used? I will check it and let you know.

Best regards,

Hi,

I checked your form at https://www.bplusc.com/contact/ and see that you’re using Contact Form 7. Our plugin fully supports Contact Form 7, so the issue is likely due to caching.

It seems you are using a cache or optimization plugin, such as Autoptimize, which may still be serving old cached JavaScript files. Please try flushing the cache, and this should allow our plugin’s latest JS files to load properly, resolving the issue.

Let me know if you need further assistance!

Best regards,

Hi Amauri,

Thank you for bringing this to our attention! That’s a blunder on our end, and we should have thought about it. We’ll add a fix to ignore 127.0.0.1 by default in the next release to prevent this issue moving forward.

Thanks

Hi Daniel,

Thank you for reaching out and bringing this to our attention.

Regarding the warning from AIOSEO Pro, we haven’t included a minified version of the wpa.js file due to the use of optimization plugins like JS/CSS minifiers or cache plugins, which should handle this task on their own.

However, we’ll definitely look into adding the minified version in our next release to resolve the issue. Thank you for your patience, and feel free to reach out if you have any further questions!

Best regards,
Dinesh