• [x] Did you check to see if this issue already exists?
  • [x] Is this only a single bug? Do not put multiple bugs in one issue.
  • [x] Is this a question or discussion? Don’t use this, use https://lemmy.ml/c/lemmy_support .
  • [x] Is this a UI / front end issue? Use the lemmy-ui repo.

Issue Summary

When editing a community as a remote user, it changes the community.local flag to false, causing the community return a 404. however it will now be accessible at https://[instance]/c/[community]@[instance].

Steps to Reproduce

  1. I tested this with a local community: https://lemmy.ca/c/test
  2. I appointed a moderator from a different instance (https://sh.itjust.works/u/smorks)
  3. I had that moderator edit the community.
  4. The community now returns an error when accessing the original url (https://lemmy.ca/c/test) but accessing it using (https://lemmy.ca/c/test@lemmy.ca) works. In the database, the community.local field is now set to false. updating it back to true fixes the 404 on the original url.

edit: ~you can fix this issue by editing the community with a local mod.~ i don’t believe this works, sorry!

Originally posted by smorks in #3017

  • issue_tracking_bot@lemm.eeOPB
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Copying here from Matrix for ease of reference until this is fixed. The following **completely untested ** SQL should fix the issue

    lemmy=# select id, actor_id from community where name='<your community name>';
    lemmy=# update community set local='t' where id=<the correct id from above>;
    

    Originally posted by jason-watkins in #3017