This really should be a new thread, but in your case, something is either
wrong with your Djblets install, or something is wrong with permissions, or
something.. That file is provided by Djblets, and you shouldn't see this
error. I've never actually seen this particular problem before.
I find it v
TemplateDoesNotExist at /trial5/
deco/box.html
Request Method: GET Request URL:
http://mumbaireviewsrv.geometric.local/trial5/ Django Version: 1.4.6
Exception
Type: TemplateDoesNotExist Exception Value:
deco/box.html
Exception Location: /usr/lib/python2.6/site-packages/django/template/loa
On Aug 27, 2013, at 14:58, Christian Hammond wrote:
> What type of auth were you using? You'll want to ensure you have the proper
> Python modules installed for LDAP, NIS or ActiveDirectory.
We are using LDAP. I was able to log in after using the FQDN for our server (I
googled for "Cookies mu
What type of auth were you using? You'll want to ensure you have the proper
Python modules installed for LDAP, NIS or ActiveDirectory.
Can you visually confirm for me that the SECRET_KEY is the same across
instances?
Christian
On Tuesday, August 27, 2013, Alfred von Campe wrote:
> On Aug 27, 2
On Aug 27, 2013, at 11:07, I wrote:
> But now I have another problem. During this upgrade, the paths to the RB
> site have changed slightly, and after the installation I get a message about
> a missing htdocs/media/uploaded directory using he old path. So I guess that
> somewhere in the datab
On Aug 23, 2013, at 16:29, David Trowbridge wrote:
> Let's try this--after creating the new site, but before loading the database
> dump, delete the new database that rb-site created.
This seems to have worked. Because I had tried to install ReviewBoard 1.6.6
via easy_install, my server was i
On Aug 23, 2013, at 16:29, David Trowbridge wrote:
> Let's try this--after creating the new site, but before loading the database
> dump, delete the new database that rb-site created.
Sigh, I started playing with installing ReviewBoard 1.6 with easy install, and
seems to have broken rb-site:
It's probably safe enough to install a new 1.7.x site, nuke the database,
copy the old one over, and do an upgrade, without reinstalling 1.6.x. The
major changes are in the database, and the in-DB versioning should work
fine from a 1.7.x install.
One important thing is to copy over the SECRET_KEY
Let's try this--after creating the new site, but before loading the
database dump, delete the new database that rb-site created.
-David
On Fri, Aug 23, 2013 at 1:26 PM, Alfred von Campe wrote:
> On Aug 23, 2013, at 16:14, David Trowbridge wrote:
>
> What's happening is that rb-site install is
On Aug 23, 2013, at 16:14, David Trowbridge wrote:
> What's happening is that rb-site install is creating a bunch of tables, and
> then you're importing in the database dump but it's ending up with a mix of
> old and new.
>
> I'd recommend installing 1.6.6 on the new server, importing the data
Alfred,
What's happening is that rb-site install is creating a bunch of tables, and
then you're importing in the database dump but it's ending up with a mix of
old and new.
I'd recommend installing 1.6.6 on the new server, importing the database
dump, and then upgrading in-place.
-David
On Fri
I'm trying to upgrade a REviewBoard instance from 1.6.6 to 1.7.13. I've
created a dump of the existing database and am running the following script on
the new server:
#!/bin/sh
RB_SITE="/var/www/html/rb"
RB_USER="admin"
RB_EMAIL=""
RB_DOMAIN=""
RB_PASSWORD=""
# Delete and create e
12 matches
Mail list logo
