초대 코드가 없으면 가입 시 오류 발생

It took me quite a while to sign up a new test user on my forum yesterday because I forgot to enter the invite code.

The error message that was shown wasn’t very helpful:

Something went wrong, perhaps this email is already registered, try the forgot password link

No matter which email I tried, the error was the same.

Would it be possible to display an error for the invite code field like when a required custom field is empty?


Maybe it would also be helpful to add an asterisk after “invite code,” since it is required too.

3개의 좋아요

I tested this again as there have been a lot of changes to the sign-up dialog in the past months. The error message shown when the invite code is missing is still the same.

I think an error message, “Please enter invite code,” below the invite code field, similar to the ones shown below the email, username, password, and custom user fields, would be helpful.

Thanks @Moin, you’re right that this error could be improved. I’ve opened a request with our team to fix this up. At this point, I don’t have an estimate for when this work might be complete based on the team’s other priorities.

3개의 좋아요

I think the only thing needed as a fix is to change the error message into “You did not enter the invite code” .

After all, when I look at the source, the only flow where this message will be shown is when the invite code is set, and not submitted. All other account registration errors return a custom error message.

When an email address is already registered, no message will be shown at all, and an email will be sent to that email address.

Hide email address taken 사이트 설정이 비활성화된 상태라면 이는 사실이 아닐 것 같습니다. 하지만 이 경우 이메일이 이미 등록되었을 수 있다는 오류가 표시되지 않는다는 점에서는 맞다고 생각합니다. 왜 그런지 궁금하네요. 이 경우, 이는 올바른 메시지인 것 같습니다.

Make reason for 'error moving posts' visible in the interface - #2 by zogstrip 의 영향으로, 이 경우에도 네트워크 응답을 확인하는 것이 의미 있을 것 같아 확인해 보니, errors: [ "param is missing or the value is empty or invalid: invite_code" ] 라는 오류도 존재합니다.

따라서 표시되는 오류를 비슷한 방식으로 개선할 수 있을 것입니다. 또한, 다른 모든 필드와 마찬가지로 프론트엔드에서 필드를 검증하는 것도 좋을 것 같습니다.

1개의 좋아요