this post was submitted on 17 Oct 2024
22 points (100.0% liked)

Lemmy

12572 readers
1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to !meta@lemmy.ml.

founded 4 years ago
MODERATORS
nutomic@lemmy.ml
22
Community sidebar reverting to previous state (lemmy.blahaj.zone)
submitted 1 month ago by LeGaosaure@lemmy.blahaj.zone to c/lemmy@lemmy.ml
9 comments fedilink hide all child comments
 

Hello, I'm a community moderator and I noticed that my updates to the community sidebar constantly get cancelled. Is this a known bug?

More details:

  • I can save the new state and it displays the new state correctly, both from the community's instance and from mine, but it changes back to the previous state after some time, going from a few hours to several days.
  • I'm not 100% sure but it seems like the sidebar reverts to its previous state after I make a new post in the community.
  • The last time I needed to make a change was in March and it worked perfectly. I've been trying to make this one stick since October 10th.
top 9 comments
sorted by: hot top controversial new old
[–] squirrel@discuss.tchncs.de 6 points 1 month ago (2 children)

The same thing happened to me. I tried editing the sidebar from my main account which isn't on the instance the community is on.

What worked for me: I had to edit the sidebar from an account that's on the same instance that the community is hosted on.

[–] Blaze@feddit.org 7 points 1 month ago (1 children)

What worked for me: I had to edit the sidebar from an account that’s on the same instance that the community is hosted on.

That's it. Moderation fully works from a local account, not for federated accounts

[–] MentalEdge@sopuli.xyz 3 points 1 month ago (1 children)

This does seem like a regression, though.

I've definitely made changes from off-instance accounts before.

[–] Blaze@feddit.org 5 points 1 month ago (1 children)

Oh, it is

[–] LeGaosaure@lemmy.blahaj.zone 6 points 1 month ago

Thanks everyone for your confirmations. I'll keep the workaround in mind in case this doesn't get solved soon, and can confirm it worked for me before.

[–] sag@lemm.ee 2 points 1 month ago

Also happen to me.

[–] flamingos@feddit.uk 1 points 1 month ago (2 children)

This has been fixed https://github.com/LemmyNet/lemmy/pull/4937

[–] Blaze@feddit.org 2 points 1 month ago

Thank you for your contribution!

[–] LeGaosaure@lemmy.blahaj.zone 1 points 1 month ago

Thank you! Though I don't understand github enough to see if this mean the fix will apply with the next update of the instances or if it's supposed to already be deployed? If someone could clarify for me I'd very much appreciate it!