Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Wrong field lookup in views

See original GitHub issue

Hi, thanks for this plugin! It looks like it’ll save at least few hours of unnecessary work!

I just have installed the plugin and started getting internal server error from views.py. The issue is the line 102:

users = User.objects.filter(email__iexact=email)

In an app that I’m currently working on, there’s no email field, but it’s actually a username field that stores the email.

How about updating the plugin, so that it allows to parametrize the name of the field used throughout the data flow? This parameter could be use in views.py, but also in serializers.py (so there are no inconsistencies in parameter between them) and elsewhere.

Thanks!

Issue Analytics

State:
Created 5 years ago
Comments:13

Top GitHub Comments

1reaction

J-F-Farcommented, May 28, 2019

Thanks for your quick response.

I’m having problems with this. I just installed the latest version 1.1.0rc1 into my project, and configured the settings value: 'DJANGO_REST_LOOKUP_FIELD = ‘username’.

This hasn’t made any difference. The view is still expecting an ‘email’.

In the commit tagged ‘1.1.0rc1’, the view ‘ResetPasswordRequestToken’ still uses the ‘EmailSerializer’, which is expecting the POSTed value to be a properly formatted EmailField, right?

Have you been able to verify that this works?

0reactions

anx-ckreuzbergercommented, Aug 8, 2019

No worries 😃

I’ll take a look at it, thank you!