You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to register an account earlier today, and the first-time registration page kept throwing Server Error (500) until I changed my password to exclude special characters (such as "Ÿ" and similar). It might be worth adding support for unicode or saying explicitly on the registration page to use non-unicode characters.
The text was updated successfully, but these errors were encountered:
According to this stackoverflow thread, it could have to do with the encoding of ocfweb's python files being us-ascii which only uses a subset of UTF-8 instead of the entire UTF-8, including special characters such as the above and emojis (!).
Switching entirely to UTF-8 could be a broader solution, but in general I would like to look into other encodings before settling.
Additionally, it could be an issue with the django database, but my research on this repo fell short as I couldn't find details about the database in my short amount of time searching. If anyone has information, drop a reply.
If ocfweb does use a django database for auth (though I suspect an LDAP service is used), the solution on the blog post above may provide an answer.
Also happy to provide steps to convert python files or make a script to convert us-ascii -> UTF-8 if necessary, or if this problem is still relevant next time someone looks at this.
As an alternative, I can also look at specifying on the registration page that only latin characters a-zA-Z and any additional characters such as numbers or special characters can be used. If you're reading this and I haven't done this please ping me.
I was trying to register an account earlier today, and the first-time registration page kept throwing Server Error (500) until I changed my password to exclude special characters (such as "Ÿ" and similar). It might be worth adding support for unicode or saying explicitly on the registration page to use non-unicode characters.
The text was updated successfully, but these errors were encountered: