Hello @josueardon,
Fluent Forms generates token for various events. As you have disabled token based spam protection, we cannot identify the issue on your form. To assist you further, could you please enable token based spam protection temporarily and record a video to show us the issue so that we can take a further look?
Thank you
I think the issue was with your caching. After enabling the token based spam protection please make sure you clear the cache of your site.
Thank you for your answer guys. The issue is not solved. I had cleared the cache, I know that. But just in case, I clared again all caches: server, local, devices, etc. but it does not work. I even asked people to try in different countries, but this is the message that one gets after trying to send the form: https://mayangatewayimages.b-cdn.net/Screenshots/Screen%20Shot%202025-03-14%20at%2017.50.17.png
I already lost a lot of potential clients, so I won’t enable the token based option again so that you can see it, becuase while you check it, I’m going to lose clients again. I’m not fun of installing more plug-ins, and my website is very well optimized so I don’t want to make the pages slow either. I will look for other solution to stop spam.
-
This reply was modified 1 year, 1 month ago by
Josue Ardon. Reason: Typos
Hello Josue,
I sincerely apologize for the inconvenience and the impact this issue has had on your business. I completely understand how frustrating it must be to lose potential clients due to this.
If possible to help resolve this , could you share a list of the plugins and the server cache you’re using? This will allow me to replicate your setup on my end and pinpoint the exact cause of the issue.
I truly appreciate your patience, and I assure you that I’ll do my best to find a solution for you.
Looking forward to your response.
Best regards
-
This reply was modified 1 year, 1 month ago by
Lukman Nakib.
Thank you Lukman. The plugins that I have besides Fluent forms are FluentSMTP, GenerateBlocks, GenerateBlocks Pro, GP premium, Load video on click, Perfmatters, Redirection, Redis Object Cache, Reivews and raiting/Google reviews, The SEO Framework, and WPCode Lite. I do the cache server-side.
I desabled the Token Based Spam to solve the issue, and because of that it is not a problem for me anymore, I just need to find another solution to stop the spam messages that doesn’t affect performance and speed. But I guess this information can be usefull for you guys.
@pyrobd Your reply has been archived and your account has been flagged. Do not ask for access to a forum user’s site, even a test or staging site again.
While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.
If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.
Thankfully are other ways to get information you need:
- Ask the user to install the Health Check plugin and get the data that way.
- Ask for a link to the http://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
- Ask the user to create and post a link to their phpinfo(); output.
- Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
- Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site visitors).
- Ask the user for the step-by-step directions on how they can reproduce the problem.
You get the idea.
We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.
When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.
