Updates:
Status: Fixed
Comment #5 on issue 2689 by trowb...@gmail.com: Error logging in to
ReviewBoard if not already logged in
http://code.google.com/p/reviewboard/issues/detail?id=2689
Django ticket 18692 was fixed in
https://github.com/django/django/commit/d0d5dc6cd76f01c8a71b677
Comment #4 on issue 2689 by chip...@gmail.com: Error logging in to
ReviewBoard if not already logged in
http://code.google.com/p/reviewboard/issues/detail?id=2689
2.7 is a good, safe bet. Note that all your existing packages are part of
your 2.4 setup, so you'll basically need to reinstall
Comment #3 on issue 2689 by duane1...@gmail.com: Error logging in to
ReviewBoard if not already logged in
http://code.google.com/p/reviewboard/issues/detail?id=2689
Thanks for the quick reply! Downgrading to Django 1.3.1 does work for now,
but I think I will try to upgrade to Python. Shoul
Comment #2 on issue 2689 by chip...@gmail.com: Error logging in to
ReviewBoard if not already logged in
http://code.google.com/p/reviewboard/issues/detail?id=2689
Filed a bug on the Django project:
https://code.djangoproject.com/ticket/18692
For what it's worth, Review Board 1.7 won't be
Updates:
Status: Confirmed
Comment #1 on issue 2689 by chip...@gmail.com: Error logging in to
ReviewBoard if not already logged in
http://code.google.com/p/reviewboard/issues/detail?id=2689
This looks to be the new code path in the Django security release. Why
we're hitting it, I do
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2689 by duane1...@gmail.com: Error logging in to ReviewBoard if
not already logged in
http://code.google.com/p/reviewboard/issues/detail?id=2689
Just recently upgraded to Review Board 1.6.11.
When logging in on a browser w