On Thu, Mar 19, 2015 at 10:55 AM, Tim Tisdall tisd...@gmail.com wrote:
On Thu, Mar 19, 2015 at 1:44 PM, Ryan J Ollos rjol...@apache.org wrote:
The plugins are responsible for upgrading the INI file configuration when
necessary. That is not to say that the Bloodhound plugins do this
On Thu, Mar 19, 2015 at 1:44 PM, Ryan J Ollos rjol...@apache.org wrote:
The plugins are responsible for upgrading the INI file configuration when
necessary. That is not to say that the Bloodhound plugins do this correctly
for all cases.
A backup of your original INI file would help us
On Thu, Mar 19, 2015 at 9:04 AM, Tim Tisdall tisd...@gmail.com wrote:
Well, I tried a fresh install and compared the .ini files. I tried to
match my old .ini files to the new ones as much as possible and that
seems to have corrected the problem. I guess the main issue is
there's no method
Well, I tried a fresh install and compared the .ini files. I tried to
match my old .ini files to the new ones as much as possible and that
seems to have corrected the problem. I guess the main issue is
there's no method of upgrading the .ini files when upgrading to a
newer version. In previous
On Tue, Mar 17, 2015 at 1:16 PM, Gary Martin gary.mar...@wandisco.com wrote:
Hmm... I think I found one way to replicate the error but it is not clear
that it matches your problem yet. If on my test server I hit a path like
products/DEF/products/DEF/somethingelse then I get that error (where
On Mon, Mar 16, 2015 at 7:58 PM, Gary Martin gary.mar...@wandisco.com wrote:
Just been looking at the area of the code that I think the error is coming
from. Coming to this for the first time, and blind to the means by which
this error is triggered, I'd probably want to know what the value of
Hi,
Just been looking at the area of the code that I think the error is coming
from. Coming to this for the first time, and blind to the means by which
this error is triggered, I'd probably want to know what the value of
path_info on line 78 of bloodhound_multiproduct/multiproduct/web_ui.py
I'm
Not an expert at all, but what database backend are you using? I successfully
upgraded from Version 0.7 to 0.8 using MySQL.
I also have the mentioned base_url-warning, but it hasn't affected me, afaik.
Can you create another (empty) install?
16 mar 2015 kl. 21:49 skrev Tim Tisdall
I'll stick some print statements in there tomorrow and see what I find.
On Mon, Mar 16, 2015 at 7:58 PM, Gary Martin gary.mar...@wandisco.com wrote:
Hi,
Just been looking at the area of the code that I think the error is coming
from. Coming to this for the first time, and blind to the means
MySQL is the backend I'm using. I previously upgraded into 0.7 and
had no issues, so I'm surprised by the problems I'm having this time.
On Mon, Mar 16, 2015 at 5:22 PM, Oscar Edvardsson os...@monivent.se wrote:
Not an expert at all, but what database backend are you using? I successfully
I'm kind of stuck with a useless install here... Is there nothing I
can do to fix this?
On Mon, Mar 9, 2015 at 3:47 PM, Tim Tisdall tisd...@gmail.com wrote:
Any debugging commands (ie inserting of logging statements, etc) I
could run to give you some additional information on this?
On Fri,
On Fri, Mar 6, 2015 at 11:22 AM, Tim Tisdall tisd...@gmail.com wrote:
I've moved to a new server and am trying to update to 0.8, I'm having
some issues, though...
For every ticket I try to access I get the following error in the logs:
HTTPNotFound: 404 Not Found (Unable to render product
I've moved to a new server and am trying to update to 0.8, I'm having
some issues, though...
For every ticket I try to access I get the following error in the logs:
HTTPNotFound: 404 Not Found (Unable to render product page. Wrong setup?)
I tried creating a new product in the Admin pages to see
13 matches
Mail list logo
