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.
I've got to fix it today or else staff and supporter badges won't go to
print in time, it's actually my highest priority thing.


On Tue, Sep 2, 2014 at 8:54 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):
> > -                a.badge_num += shift
> > +                min_num, max_num = BADGE_RANGES[int(attendee.badge_type)]
> > +                if not min_num <= attendee.badge_num <= max_num:
>
> I'm cool with a one-off script. If Dom doesn't actually write it today,
> will I being doing it?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/magfest/ubersystem/pull/502/files#r16984728>.
>