-
Notifications
You must be signed in to change notification settings - Fork 58
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
NoReverseMatch with custom url #83
Comments
Yes, I recently started maintaining this project again. |
When using this it marks the user as active, but that is the page it goes to afterward. \Python\Python311\Lib\site-packages\verify_email\views.py, line 58, in verify_user_and_activate 'link': reverse(login_page) ^^^^^^^^^^^^^^^^^^^ |
By the way, this is a really nice app |
I'm sorry but I don't understand the issue, could you be more specific? |
When the user clicks the verification link, that is the page that displays. I am assuming it should be the successful page. |
I'm guessing it might be a conflict with the app |
Yes when I get home tonight |
I sent a verification email and then redirected to http://127.0.0.1:8000/accounts/login/. The user is created and is set to inactive. When the user clicks the verification email they are marked active and this page is shown to them. NoReverseMatch at /verification/user/verify-email/anNsb3Zlcm5AZ21haWwuY29t/YnR3YWd4LWQ2ZGEwNGY4YWRkYzY4MDljNmIxMjE4NDEwZTE5NTMzOjFxY1JjbjpIcWRXNzFwclEwUW1fNnB3NE5MTUdsTmVsNFBQcmVmZjg4bnhkdFdYQmtF/Reverse for '/accounts/login/' not found. '/accounts/login/' is not a valid view function or pattern name.
Traceback Switch to copy-and-paste view
####################################################################
urlpatterns = [ views.py |
Sorry wrong urls.py urlpatterns = [ |
Ok, I understand better now. A couple of things:
|
I just stumbled upon this issue when trying to figure out why this library generated a wrong URL and I think it might be the same cause. I am specifying a custom URL for the view: path('welcome/<str:token>/', verify) This will generate URLs in the form of django-email-verification/django_email_verification/confirm.py Lines 73 to 85 in 49e841b
In particular it seems to always assume that the token comes at the end and there is no trailing slash (or anything else after the token, for that matter). In my opinion: |
I was curious if anyone is looking at this because I have an issue.
The text was updated successfully, but these errors were encountered: