I simply added that line as a comment, I would have course included
this line, but the point was to show that execution never seems to hit
that point.
On another note, my 500 errors have gone as of now, sadly without any
changes to the system. The problem is definitely outside of django
(though c
> You really need to find a way to get the traceback, without that its
> really hard to say what the problem is. Tools likehttp://areciboapp.com
> are useful for this, but just setting DEBUG=True and restarting your
> Apache/whatever should be enough.
I'll have to try that arecibo, since I'm 100%
The size might be due to the fact were using Novell's iChain
possibly?
Here is the form processing code. This form, oddly enough, was
working perfectly fine for a little while, so it seems to be a non-
consistent bug (though I haven't been able to get it to work once at
all today.) This form doe
I am getting a 500 server error when I try to submit (via "POST") a
certain form. The form is built like so:
CATEGORY_CHOICES = (
('desktop', 'Desktop Computer'),
('laptop', 'Laptop Computer'),
('printer', 'Printer'),
('phone', 'Phone'),
('other', 'Other')
)
class WorkorderFo
4 matches
Mail list logo