-
-
Notifications
You must be signed in to change notification settings - Fork 859
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
[Bug]: language_not_allowed: language_not_allowed #3150
Comments
I can confirm this. It happens consistently from lemmy-ui unless I manually select English, and it happens in Jerboa too (which renders Jerboa unusable, since it doesn't have a language drop-down). |
The language implementation in Lemmy either needs to improve, needs better documentation, or needs to go. I understand the purpose of it,but half of the posts I cannot comment because of some misconfiguration either on my instance, their instance, their client, or my client. It seems clunky and overly complex. |
Yeah I don't understand it's purpose either. |
At very least, validation needs to go. |
Same as #3451 which is fixed, closing this one. |
Requirements
Summary
Summary. Was able to comment on this post.
Even created a reply with the word, "test". That is the deleted comment being displayed.
However, when attempting to write an actual comment, it sits and spins for ever.
After tailing the server logs, I noticed the below "language_not_allowed" errors occuring every time I attempted to reply.
Steps to Reproduce
Technical Details
Version
BE: 0.17.4
Lemmy Instance URL
lemmyonline.com -> beehaw.org
The text was updated successfully, but these errors were encountered: