I'll keep the support contract in mind. For now, I think we can muddle
along without it.
Thanks again for all your help.
David
On Friday, July 31, 2015 at 5:17:49 PM UTC-4, Christian Hammond wrote:
Glad it works, David! Sorry for the Power Pack issue. I'll see if we can
bullet-proof that
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
Glad it works, David! Sorry for the Power Pack issue. I'll see if we can
bullet-proof that a bit more.
If it helps down the road, we've been providing support contracts to
customers and working with them closely when major issues like this come
up, to help them get up and running quickly as soon
Hi David,
First, to cover the PySVN vs. Subvertpy question, Subvertpy was only the
default for the first release or two of 2.0.x. It had a lot of
compatibility problems and broke in far too many situations, so we flipped
the defaults. If it was working for you and you want to go back to it, you
Christian,
Thanks for the quick response.
1. I don't need or want subvertpy. I just noticed that the error was in
pysvn. I'll stick with what you guys have determined works best; i.e.,
pysvn.
2. I don't remember ever setting passwords for the repositories. I see
what I guess is encrypted
Christian,
Thanks for the quick response.
1. I don't need or want subvertpy. I just noticed that the error was in
pysvn. I'll stick with what you guys have determined works best; i.e.,
pysvn.
2. I created the site directory from scratch, but then tried to find stuff
from the backup site
OK, progress.
I edited my SQL dump file, replacing the tab-initial-character-encrypted
passwords with plain-text passwords. Not sure what they used to be, so I
just put something simple. Then I dropped the reviewboard database and
recreated it as utf8, and loaded the edited dump file.
Now I
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
