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.
Blocks view fails if blocked usernames contain + sign
See original GitHub issueI’m using a system where we use emails as usernames.
If an username like user+test@domain.tld gets blocked, then the rendering of /admin/defender/blocks/ fails with the following error:
Reverse for ‘defender_unblock_username_view’ with arguments ‘(u’user+test@domain.tld’,)’ and keyword arguments ‘{}’ not found. 1 pattern(s) tried: [u’admin/defender/blocks/username/(?P<username>[A-Za-z0-9-._@]+)/unblock$']
Obviously that’s because the + is not in the group of allowed chars for the regexp. Can we make the regexp a bit more permissive? I understand a + sign is OK in an URL and as part of a username.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That sounds fine, feel free to submit a PR and I’ll review, and if it looks good, we can merge.
Thanks, closing.