-
Notifications
You must be signed in to change notification settings - Fork 2
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
Make sort_name sortable 🙃 #1146
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works great! Just one comment.
RECAPTCHA_PRIVATE_KEY=(str, ""), | ||
# Test keys from: | ||
# https://developers.google.com/recaptcha/docs/faq#id-like-to-run-automated-tests-with-recaptcha.-what-should-i-do | ||
RECAPTCHA_PUBLIC_KEY=(str, "6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI"), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Locally, I had to remove the corresponding (empty) recaptcha variables from .env.local
to get this to work. django-environ
seems to parse empty variables as present and won't use the default.
We should probably remove these variables from .env.local.example
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great catch. Done!
Overview
This PR updates the configuration of the sort_name field so ElasticSearch will actually sort by it. Reference: django-haystack/django-haystack#569
Connects #1142
Testing Instructions
This change requires an index rebuild to take effect, so you'll have to test locally.