This is definitely a bug in Review Board that is still posing a problem. I'm
going to try again to fix it for beta 1.
They're all stored in the database. The issue is that they're cached after
loading (so we don't hit the database every time). The cache is
per-instance. I have code in there to che
The version I'm using is "a4".
I don't have a problem with restarting apache afterward. But it would
be useful if, at least, when I make a change, and then quit my
browser, and bring it back up again, that the saved settings appear.
But I'm not getting that, and it's a little disconcerting, becau
Which version are you using? I had this same issue up to 1.0 alpha2,
when I upgraded to alpha4 these issues went away. I can't speak for
alpha3 as i skipped that release.
> And I've had problems setting up the Advanced Authentication settings
> (I'd really like to use either AD authentication, o
On Feb 20, 2009, at 11:47 AM, Dan Morrow wrote:
>
> Where are the settings stored for logging and authentication?
My experience has been that you have to restart apache after making
configuration changes, or else not all the mod_python instances seem
to notice.
> Here's my problem. If I g
Where are the settings stored for logging and authentication?
Here's my problem. If I go to the "Logging" setting, I turn on the
"Enable Logging" checkbox, and type in a path, which I know that
Apache can write to. Then I hit the "Save" button, and the "Log
directory" box is blank. If I refresh t
