Hi Eric,
Thanks for your post, that I could understand the issue that was happening
at my reviewboard instance.
Did you figure out the solution for this.
With your approach to turning the Debug = True, I am currently able to
access the repositories / enter the edit screen.
But unfortunately,
Further, the reviewboard database was created with UTF8 character set.
MariaDB [reviewboard]> show variables like "character_set_database";
++---+
| Variable_name | Value |
++---+
| character_set_database | utf8 |
The specific
--
To reply, visit https://hellosplat.com/s/beanbag/tickets/4446/
--
New ticket #4446 by sdubrul
For Beanbag, Inc. > Review Board
Status: New
Christian Hammond writes:
> If the external Review Board server is requiring Basic Auth for access
> (outside of our Basic Auth requests in the API), then that may be a
> problem. You're dealing with two different kinds of authentication. I'm not
> sure from your
Hi,
I am pretty new to reviewboard and have attempted to migrate reviewboard
instance across hosts and versions.
Our older RB version was and the upgrade was to 2.5.6.1
Steps followed for the upgrade were
(1) Dump data on the older server (mysql)
(2) Drop the previously created reviewboard
Hi,
Wierdly, I tried following approach and it worked:
-copied MIDDLEWARE_CLASSES from settings.py and added
django.contrib.auth.middleware.RemoteUserMiddleware
after AuthenticationMiddleware in settings.py
-Went to admin account using username and password that was created at
rb-site