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.
  • squirrel@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 month ago

    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 (he/him)@feddit.org
      link
      fedilink
      English
      arrow-up
      7
      ·
      1 month ago

      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
        link
        fedilink
        English
        arrow-up
        4
        ·
        1 month ago

        This does seem like a regression, though.

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

          • LeGaosaureOP
            link
            fedilink
            English
            arrow-up
            6
            ·
            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.

    • LeGaosaureOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      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!