27

Today I got to 15000 reputation on Super User. I received the notification that I could now protect questions (eligible for protection as per the FAQ).

Interestingly enough, it didn't work. I just couldn't find the link. So I brought it up on Meta.SU.

It turns out: At exactly 15000 reputation, you can't protect a question. If you are at 15001, it works though. Probably the internal check uses a reputation > 15000 check instead of reputation ≥ 15000. Should be easy to fix.

Improve this question
3
  • … could also be that this is an issue for all other privileges?
    – slhck
    Sep 21, 2011 at 22:43
  • possibly ... Ill have a quick look
    – waffles
    Sep 22, 2011 at 2:46
  • 1
    yeah .. I changed in 12 other spots as well
    – waffles
    Sep 22, 2011 at 2:52

1 Answer 1

Reset to default
17

crisis averted

Crisis has been averted :) my bug.

Improve this answer
12
  • 18
    You just wanted to show off that awful color scheme.
    – Jarrod Dixon
    Sep 22, 2011 at 2:46
  • 1
    So is this how you guys communicate at SE corporate? By tossing meta comments over the cubicle walls? :P
    – user102937
    Sep 22, 2011 at 2:54
  • @RobertHarvey yeah ... either that or the twitters :)
    – waffles
    Sep 22, 2011 at 2:56
  • 3
    "MinAgeBeforeAllowingProtectInDays". So I'm guessing you guys don't need to comment your variables
    – Michael Mrozek
    Sep 22, 2011 at 2:56
  • @Jarrod's right, Obsidian is a much nicer theme.
    – Tim Stone
    Sep 22, 2011 at 2:57
  • @TimStone I dunno I have a soft spot for Vibrent Ink alternateidea.com/blog/articles/2006/1/3/… must be my old Ruby days
    – waffles
    Sep 22, 2011 at 3:00
  • 6
    Also, that code made me realize it's possible to protect answers (if you're a mod)
    – Michael Mrozek
    Sep 22, 2011 at 3:01
  • @MichaelMrozek I noticed that too, but the option doesn't show up in the mod menu... how did you pull that off?
    – nhinkle
    Sep 22, 2011 at 5:18
  • well protecting answers is clearly a bug :) fixing @nhinkle
    – waffles
    Sep 22, 2011 at 5:33
  • @waffles, I'm guessing from that link that the theme you use isn't for VS - do you use a similar one in VS (if you use VS that is!) that's on t'internet anywhere, it's very soothing on the eyes! =) On another note, wrapping !post.IsProtected && post.IsQuestion as a property bool IsProtectable - overkill? I'm curious what fix you went for... duplicating the post.IsQuestion check, mass refactor, or something else entirely? (Only because I'm always interested in seeing how other people tweak their code)
    – Rob
    Sep 22, 2011 at 11:54
  • @Rob already restructured that code to fix the bug Michael raised, I use a self modified version of studiostyl.es/schemes/vibrant-ink in vs 2010
    – waffles
    Sep 22, 2011 at 12:07
  • @waffles - theme downloading as I type - thankee :)
    – Rob
    Sep 22, 2011 at 12:08

You must log in to answer this question.

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