sdfpubnix

1444 readers

3 users here now

Fans of SDF

founded 2 years ago

MODERATORS

SDF@lemmy.sdf.org

[solved] cannot edit my post b/c of ~~slur filter?~~ (language selector bug in web UI) (lemmy.sdf.org)

submitted 3 weeks ago* (last edited 3 weeks ago) by evenwicht@lemmy.sdf.org to c/sdfpubnix@lemmy.sdf.org

5 comments fedilink hide all child comments

I posted the linked article and now I need to edit it.. some of the formatting looks terrible. But I am blocked. The editor lets me edit, but no matter what I do I cannot save the edits. There is a pop-up about forbidden language.

It’s an old Lemmy bug to not tell authors what word is the problem. But very bizarre that it accepted the post in the first place if it had a problem with it. My edits are certainly not causing that.

The post is not on sdf.org, so I suppose the problem could be with the hosting server.

you are viewing a single comment's thread
view the rest of the comments

[–] evenwicht@lemmy.sdf.org 1 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

thanks for the tip, but it seems to make no difference. I changed it from browser default to english. Is that the right setting? The screenshot does not render for me.

I simply tried to add the word “needed” to the end of the title, and it said “language not allowed”.

[–] MachineFab812@discuss.tchncs.de 2 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Its part of the web-page, next to/under the text-entry box. Normally, it should say "Select language \/" ... but yeah, you've now confirmed its not because you used a bad word or anything like so. I'm not aware of many communities that even have such filters.

[–] evenwicht@lemmy.sdf.org 1 points 3 weeks ago (1 children)

Oh, right! Indeed, I forgot there was a language specifier for the post itself. That fixed it. Thanks!

What a piece of shit software.

[–] MachineFab812@discuss.tchncs.de 1 points 3 weeks ago

I think the servers got an update or something. Lemmy is beautiful, and I'm more happy that its getting updates than I am concerned that an update introduced a bug with an easy-enough work-around.

On the other hand, maybe you and I just accidentally touched the drop-down and happened to create this issue for each of ourselves on the same day. Oh, and I happened to find your post before hitting this issue myself. Stranger things have happened.