19

I can't access /admin/flags/site-specific-close-reasons on either of the sites where I'm a moderator (here and here). Clicking the "Manage community-specific close reasons" link from /admin/links gives me an "Oops! Something Bad Happened!" page.

Other moderators report seeing the same, so it's not just me.

What gives?

Improve this question
6
  • 4
    Yes, yes it is. :/ Thanks for the report.
    – Catija
    Sep 27, 2022 at 20:04
  • 1
    We've identified the problem and a fix should go out tomorrow, thanks for catching this!
    – Kyle Pollard StaffMod
    Sep 27, 2022 at 22:55
  • @KylePollard so, how bad was it?
    – Robert Columbia
    Sep 28, 2022 at 0:17
  • 1
    Not bad at all, that mod page uses a made up placeholder post, and our code was trying to get information from the database about it. "Where is the post with an ID of -1!?"
    – Kyle Pollard StaffMod
    Sep 28, 2022 at 2:09
  • @KylePollard Thanks for the quick fix! Btw, the reason I wanted to access that page was to report two typos in it, so expect another bug report on the same topic very soon :-)
    – Rand al'Thor
    Sep 28, 2022 at 6:35
  • 1
    Hmm, this change went out today, but I'm still getting the exception in production. I'll check again tomorrow.
    – Kyle Pollard StaffMod
    Sep 28, 2022 at 23:51

1 Answer 1

Reset to default
7

This was a bug, thank you for reporting it.

This page uses a placeholder post to generate the close post notice preview. However, the placeholder had an ID of -1. Some new code incorrectly handled this id and tried to fetch it from the database, which totally blew up. We've now fixed this bug.

Improve this answer
1
  • 2
    Thanks! And another thanks to whoever changed "discribe" to "describe" and "this will message will" to "this message will" in that page - no further bug report coming after all :-)
    – Rand al'Thor
    Sep 29, 2022 at 18:57

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .