I sometimes get this weird error when trying to comment on posts: “language_not_allowed”. I’ve tried leaving the language as undetermined or setting it to English and neither seems to work.
How do I go about fixing this?
Suddenly I won’t see many/any posts newer than pre-break, any comments or posts classified as English (and presumably other languages) I can’t see at all. Even ones in the community I mod. Confirmed the issue existed in Memmy as well as lemmy.world and lemmy.ca
Hmm, oddly it seems like picking my language in my personal settings does pretty much nothing. I did notice it tries to add “Undetermined” to whatever I choose, and sometimes unselecting everything is buggy.
Did you try clicking the X box to the right of the language, and saving that?
Unfortunately there’s quite a few bugs in the current version of lemmy + lemmy-ui we’re on. Lemmy.world is on the latest beta release, so if you’re seeing the same problem there then it’s probably unresolved.
I did a quick look through open bug reports (https://github.com/LemmyNet/lemmy-ui/issues) but couldn’t see anything obviously matching this. You may want to report exactly what you’re seeing / doing.
Thanks for looking into it, tbh I didn’t report it because I attributed it to a combination of my own blundering around in settings, and the upgrades messing with servers. The issue only occurred on Chrome iOS as far as I can tell - but it seemed like I created some quantum settings situation whereby looking at my profile settings, language would always revert to ‘0 languages’ - that is what I also got when clicking the x. And then I would not be able to see the posts and comments I knew should be visible (sometimes there was a bit of time before things disappeared/stop appearing while it caught up). I tried switching apps and finally browsers and got it (using Safari/desktop Firefox) to stay at undetermined + English as long as I didn’t look at it via Chrome. I did clear cache and history and all that.
But at that point I was a bit tired of troubleshooting it and left it alone. I will try to recreate the problem for myself on both instances and submit a bug report if it is still occurring, though!!
