-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Captcha throws a token failure error when submitting a form more than once, without refreshing the page #5
Comments
Hi, @iDiegoNL Can you share the backend responsible for the form above? To demonstrate the issue, and have a solution quickly. |
@ousid I have created a repository to showcase the code and issue here: https://github.com/iDiegoNL/coderflexx-laravel-turnstile-livewire-bug-example/blob/master/app/Http/Livewire/ExamplePage.php To reproduce the issue on the example repo, simply press the "Submit" button twice. However, I am not sure if this issue belongs in this repo, or in the coderflexx/filament-turnstile repo. |
@iDiegoNL I see you are using filament form, package. Have you tried the filament package? |
Yes, this issue happens with your filament package as well (see the composer.json file in the example repo that I linked) :). Therefore, i am not sure if this issue belongs in this repo, or in the other. |
@iDiegoNL, yeah. That's odd. Maybe a quick solution for now, is to have an PS: if you have any suggestion on how to be done, or an Idea. I'll be happy to hear them out. |
Fixed in coderflexx/filament-turnstile#12 Note: This feature is only available for filament |
What happened?
The captcha throws a token failure error when submitting a form more than once, without refreshing the page.
How to reproduce the bug
Steps to reproduce:
turnstile_check_message
validation error, presumably because it's trying to re-use a token while they're single-use.Package Version
1.0.4
PHP Version
8.1
Laravel Version
10.13.1
Which operating systems does with happen with?
No response
Notes
No response
The text was updated successfully, but these errors were encountered: