Muhammad Usama Azad
Forum Replies Created
-
Hi @shahmanish877 ,
I hope you are doing well,
Thank you for taking the time to share your concerns. We completely understand the impact this issue has had on production websites and appreciate your candid feedback.
I just wanted to let you know that our QA team is actively working on validating the fix. Since CF7 Apps is used on a large number of websites, we are treating this as a high-priority issue. While a fix has already been implemented, we want to ensure it is thoroughly tested across different environments and configurations before releasing it to the WordPress repository.
Our goal is to provide the most stable and reliable solution possible and avoid introducing any additional regressions that could affect users.
We sincerely appreciate your patience and understanding throughout this process. We are working to complete the QA process as quickly as possible and expect to release the stable version very soon.
Thank you again for your feedback and continued support.
Hi @bmove ,
You’re very welcome! 😊
We’re glad to hear that you’re happy with our support and the plugin.
If you have a moment, we would greatly appreciate it if you could leave us a quick review on ww.wp.xz.cn. Your feedback helps other users discover the plugin and motivates our team to continue improving it.
https://ww.wp.xz.cn/support/plugin/contact-form-7-honeypot/reviews/#new-post
Thank you for your support, and please don’t hesitate to reach out if you need any further assistance.
Hi @flx0 ,
I hope you are doing Well,
Thank you for taking the time to share your feedback, and I’m sorry for the frustration you experienced.
We recently identified and addressed some issues related to the honeypot and time-check validation logic. As part of this work, we have made several improvements in our latest beta version that may resolve the behavior you described.
Download the latest beta version
Could you please install the beta version, set the Time Check value to 10 seconds, and test your forms again?
Before testing, please make sure to clear all caches, including:
- Plugin cache
- Server-side cache
- CDN cache (if applicable)
- Browser cache
If the issue still occurs after testing the beta version, please let us know the results and share any relevant details from your setup. We will be happy to investigate further.
We look forward to your feedback.
Hi @bmove ,
I hope you all are doing well.
I would like to inform you that we have fixed the issue in our beta version. Currently, the fix is undergoing QA testing to verify multiple use cases and ensure everything is working as expected.
Once we receive confirmation from our QA team, we will proceed with releasing the fixed version publicly.
Thank you for your patience and cooperation throughout this process.
Hi @doffine ,
I hope you are doing well,
Thank you very much for the detailed feedback and for testing the beta version over the weekend.
I am glad to hear that both the Honeypot and Minimum Time to Submit features are effectively filtering spam. Increasing the complexity of your quiz question is a great strategy; sometimes bots are pre-programmed to solve common arithmetic, so contextual or logic-based questions often prove much more resilient.
Please find the answers to your questions below:
- Will the beta version auto-update?
No, the beta version will not auto-update like the standard releases available through the WordPress repository. Once the stable version is officially released, we will inform you so you can manually update to the latest version. - What changes were made in the beta?
We enhanced the honeypot validation by applying the time check conditionally based on the specific token creation settings. It is very plausible that these changes fixed the issues you were previously experiencing. - Are you working on a second beta?
Yes, we are continuously monitoring reports and testing additional improvements regarding spam protection and overall plugin compatibility. - How else can we improve bot protection without external services?
Beyond Honeypot, Time Checks, and Quiz fields, we recommend:- Using highly contextual or industry-specific quiz questions.
- Using non-predictable or randomized field names (avoiding common IDs like name or email).
- Ensuring that caching is disabled on pages containing your forms to prevent token/field conflicts.
Additionally, we offer an hCaptcha integration, which is a highly effective way to stop more advanced bots if you decide to go that route.
Thank you again for your patience and for your valuable contribution to this process.
Hi @bmove ,
Thank you for the confirmation and for testing it further 🙂
That’s great to hear. We’re glad to know the forms are now working correctly on your setup, including with the 10-second time check enabled.
We truly appreciate your patience, testing efforts, and detailed feedback throughout the troubleshooting process.
For now, we are marking this thread as resolved. If you encounter any further issues in the future, please feel free to open a new support thread anytime. We’ll be happy to help.
Have a great day!
Hi @bmove ,
Thank you for your message and for testing the beta version.
We’ve reviewed your report and would like to inform you that we have made some code changes in the latest beta build related to the honeypot and time-check validation logic.
Could you please make sure you are using the latest beta version from the above mentioned link and test again after clearing all caches (including any server-side cache or CDN if used)?
Looking forward to your feedback.
I hope you are doing well,
We’ve implemented some cache-related fixes in this beta build that may help resolve the issue you were experiencing. After installing the beta version, please make sure to clear both your website cache and any server-side cache.
You can download the beta version from the link below:
Once tested, please let us know whether the issue has been resolved on your end or if you are still facing any problems. Your feedback will help us continue investigating and improving compatibility.
Looking forward to your update.
Hi @doffine ,
I hope you are doing well,
Thank you for sharing the additional information and for opening the support ticket.
We have received the screenshot and details successfully, and our technical team is currently reviewing them for further investigation.
Please feel free to update us after your weekend testing with any additional findings.
We appreciate your cooperation and patience throughout this process.
Hi @bmove ,
I hope you are doing well,
Thank you for contacting the CF7 Apps Support Team. I am glad to assist you today.
I just wanted to inform you that we are currently unable to replicate the issue on our end. However, our team is actively investigating it.
To help us further analyze and replicate the behavior, could you please provide:
- A screencast video demonstrating the issue
- The Contact Form 7 form configuration
- The Honeypot field/settings configuration
- The exact steps required to reproduce the issue
This information will help us identify whether the issue is related to a specific configuration, validation flow, or a recent change introduced in the latest CF7 release.
We appreciate your cooperation and look forward to your response.
Hi @doffine ,
I hope you are doing well.
Could you please confirm whether you have had a chance to install the beta version? If yes, kindly share your feedback with us. This will help us improve the plugin further and prepare a stable release for all users.
Looking forward to your response.
Hi @timohubois ,
Thank you for your response 🙂
You are absolutely right. The issue will be fully resolved once the new stable plugin version is officially released.
We have already fixed the issue on our end, and it is currently in the QA phase. Once we receive the green signal from the QA team, the fix will be included in the upcoming release.
Thank you for your patience and cooperation.
Hi @doffine ,
I hope you are doing well.
Thanks for reaching out to the CF7 Apps Support Team. I am glad to assist you today.
We’ve made some code changes in our beta version. Could you please download and test the updated plugin from the link below?
We would really appreciate it if you could test this on your end and confirm whether everything is now working as expected.
If the issue still persists, kindly share screenshots of the form backend fields and the honeypot settings. This will help us better understand the issue and provide you with accurate assistance.
Looking forward to your response.
Hi @timohubois ,
Thank you for the confirmation. I am glad to hear the issue has been resolved successfully. I am now marking this ticket as resolved.
If you are satisfied with our support and the plugin, we would really appreciate it if you could leave us a quick review on ww.wp.xz.cn. Your feedback helps us a lot and motivates our team to continue improving the plugin.
https://ww.wp.xz.cn/support/plugin/contact-form-7-honeypot/reviews/#new-post
Looking forward to your feedback.
Hi @timohubois @joergpe ,
I hope you are doing well.
We’ve made some code changes in our beta version and have fixed the issue you reported related to the dynamic honeypot transients and full-page cache compatibility.
Could you please download and test the updated plugin from the link below?
We would really appreciate it if you could test this on your end and confirm whether everything is now working as expected.
Looking forward to your feedback.