Happy to help.
On Jul 25, 11:49 am, Julien Phalip wrote:
> Thanks Jamie! Setting "verify_exists" to False did the trick. It's not
> the first time I get caught so that's a bit shameful... :/
>
> Like you say, it's worth trying the simple routes before looking at
> complicated things ;)
>
> Che
Thanks Jamie! Setting "verify_exists" to False did the trick. It's not
the first time I get caught so that's a bit shameful... :/
Like you say, it's worth trying the simple routes before looking at
complicated things ;)
Cheers,
Julien
On Jul 25, 7:19 pm, jamiecURLe wrote:
> I always try and g
I always try and go do the simple routes first before assuming that
the problem is something complicated.
Debugging this one might be tricky if you can't recreate the effect
locally and I'm sure you don't want to be debugging on a live site!
Do you have any signals connected to the models? If s
Thanks a lot Jamie. Your stab in the dark is very useful indeed.
The site is in fact hosted at Webfaction too, and it's only there that
I get the error. The model is quite simple - it only has Charfields,
URLFields and Emailfields. There is no inheritance, but there is a
OneToOneField relationshi
Hello Julien,
Without seeing the model and knowing who your hosting provider is and
what web servers your using to serve up your django app it is
difficult to say for sure but I have a hunch.
It could be that the save action for that one organisation is creating
form of memory intensive situatio
Hi,
I've got a really strange error on one of my sites. There is an
Organisation model which has a dozen of fields and 1,300 rows.
Saving organisation details in the admin usually works fine except for
one organisation. When I click 'Save', the page loads for ever and
then it fails with a 502 Pr
6 matches
Mail list logo