[2.1.4]: 2: Undefined array key "code"

[andrew-davie]

Basic Information

My error log is showing several of this error per-day, apparently when someone tries to register (user is Guest).
Essentially it just says "2: Undefined array key "code"

Steps to reproduce

I do not know how to reproduce. I have some successful registrations, and some of these log events suggesting registration basically works, but some condition causes it to fail sometimes, and trigger a code error. I have tried registering myself and it seemed to go OK. The message seems pretty straightforward, and the point in the code where it literally tries to access the array with the key 'code' is obvious. I just don't know the code well enough to understand why or what's going on.

Expected result

We should not be seeing an error in the log - this appears to be a code bug.
In other words, failed registrations are a different issue to this.

Actual result

As noted, it's intermittent and appears to be related to new registrations.
All that I know is the error log showing the message.

Version/Git revision

2.1.4

Database Engine

MySQL

Database Version

5.7.44-percona-sure1-log

PHP Version

8.1

Logs

No response

Additional Information

No response

[arekpietrzyk]

Same issue here.

[DiegoAndresCortes]

Title of this issue needs to be updated to indicate it's for 2.1

[sbulen]

I can't reproduce, but note that this isn't a registration error - it's a search error. It's just using the function in Registration.php that validates the code.

But the "vid=search" indicates this is a search request.

So it appears the option to use verification on guest searches is enabled.

[sbulen]

I saw a user report on another forum that they got this code error after using the forgot password email link.

[andrew-davie]

Another observation - my last 8 error messages were from a consistent (almost) IP address. [52.230.152.*] where the last number varies. Strangely, this appears to be Microsoft. Just coincidence I suppose, but I thought I'd mention it.

[arekpietrzyk]

I have no past logs now, but for me, it started right after upgrading to 2.1.4