Begin fixing badge numbers

Changes the 8.5 badge numbers, and starts making uber check if they're in range when shifting them up or down.

This isn't a very good solution, but we can use this to fix the staff and supporter badges and make them adhere to the new numbers. Basically, you can select "next available badge" on a Supporter or Staff badge, and it will fix all those badges' numbers... except the one you're actually changing.
Cool makes sense. I mean, clearly something related to this is bugged out
somewhere in uber, maybe this was it.


On Tue, Sep 2, 2014 at 8:30 AM, Victoria Earl <notifications@github.com>
wrote:

> In uber/badge_funcs.py:
>
> > @@ -74,7 +74,12 @@ def shift_badges(attendee, down, until = MAX_BADGE):
> >              shift = -1 if down else 1
> >              for a in Attendee.objects.filter(badge_type = attendee.badge_type, badge_num__gte = attendee.badge_num) \
> >                                       .exclude(badge_num = 0).exclude(id = attendee.id).exclude(badge_num__gt = until):
>
> So, when messing around with the badges code, I was able to get my local
> copy of uber to push badges down below their minimum in the badge range. I
> believe this is part of what happened to the Supporter and Staff badges in
> 8.5 uber.
>
> Perhaps a one-time script would be a better option in this case, since
> Staff/Supporter badges are done being added. But I started out with
> piggybacking on the shift code to try to figure things out, and it got too
> late to try to do anything else. So that's why there's a PR.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/magfest/ubersystem/pull/502/files#r16983746>.
>