Excellent. The "DEBUG = True" was just the ticket.
The problem was that we had installed the PowerPack extension for the trial
period on the old server. We never used it after that, so I completely
forgot about it. But, its presence was known to the backup, so whenever I
clicked on a repository link, it was trying to import some power pack stuff
By the way, I chose to debug this on a separate debug install that I did
this morning on a VM. I did not want to disrupt the masses until I was
sure I had a solution. Took a few whacks, but mostly worked well.
All I had to do was install the PowerPack via easy_install. I did not
bother to enable it, since we don't plan to use it. But my VM will now
happily load the admin repository pages. And, I'm about to disrupt the
masses for a moment while I restart httpd on the production server.
Thank you for all your *excellent* help. We love the tool.
On Thursday, July 30, 2015 at 6:06:14 PM UTC-4, Christian Hammond wrote:
> Hi David,
> Been in meetings. Sorry for not getting back to you sooner.
> That's odd. If you get a 500, it should definitely appear in the log. What
> you can try doing if that's not happening is *temporarily* setting this in
> your $sitedir/conf/settings_local.py:
> DEBUG = True
> (This *will* change behavior of the site, so remove it when done with this
> Reload the web server and go back to that repository. You should get a
> detailed traceback now, along with all the variables at each point in the
> Review Board - https://www.reviewboard.org
> Beanbag, Inc. - https://www.beanbaginc.com
Supercharge your Review Board with Power Pack:
Want us to host Review Board for you? Check out RBCommons:
Happy user? Let us know! https://www.reviewboard.org/users/
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/d/optout.