parameter is not valid for captcha why?

[mark leenheer]

Seeing the error "parameter is not valid" for captcha field once in awhile in one of my templates causing it to end badly.

It won't do it in debug and only once in awhile when running, I can't seem to catch it happening or figure out why?

I am using -1 for form and I don't think anything is dynamic that I can see. Also using 3 different search strings/criteria. Besides it's not an element not found error...

It's doing it about 5-10% of the time only.

What does it mean when it says that?

 

[nevadahsot]

Could you show the address?

Maybe I could give a unique/funny solution.
(Just for captcha img/input locating issure.)

 

[mark leenheer]

Could you show the address?

Maybe I could give a unique/funny solution.
(Just for captcha img/input locating issure.)

It's just a standard Re-captcha as is on thousands of sites..
It's not a location issue if it were, it would say element not found pretty sure.

No one has seen this before or knows what it means?

My template is running perfectly except for this one random error :mad:

 

[rostonix]

Please make screenshot of this error and provide us logs. Thank you.

 

[nevadahsot]

This is how I do ---Recaptcha !
(Not for "parameter is not valid" problem.)

 

[mark leenheer]

This is the error.

These are my cap settings



It's not a location issue, it works 90% of the time just fine.

Also, when I get this error it shuts down the entire instance immediately, It seems to happen before or when the captcha is sent to service.
I also tried multiple captcha services (same issue).

it does not even complete the bad end routine I have in place
to save my account data....

 

[mark leenheer]

dupe post

 

[rostonix]

Make a screenshot of this action's settings:

 

[mark leenheer]

Make a screenshot of this action's settings:

Yup, I sent logs as requested too.

It is the captcha



Originally I was using look ahead in the regex *.recaptcha but someone told me that may be causing the issue so I edited it to what it shows now. It's still doing it after eliminating the look ahead from regex.
Just a FYI in case the logs show that.

 

[mark leenheer]

Big thanks to Bigcajones for helping me solve this.

Apparently it was finding multiple images and getting confused or whatnot.

I eliminated the group 1 entry in the cap recognition data and it's now working like a champ.

I figure I'd post here just in case anyone else runs into this issue in the future and also so you admin guys can relax if you were still working / thinking on it.

@Nevada, looks like your method would have fixed it too