Tres Seaver wrote:
Is it really the case that no-one knows what's going on here?
Maybe nobody else cares enough to do the debugging you're too lazy to do? ;)
Tres,
That's not exactly fair.
Someone must have made a conscious change for this to happen.
It would take and order or two of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 24, 2009, at 09:49 , Chris Withers wrote:
Tres Seaver wrote:
Is it really the case that no-one knows what's going on here?
Maybe nobody else cares enough to do the debugging you're too lazy
to do? ;)
Tres,
That's not exactly fair.
Jens Vagelpohl wrote:
Sorry Chris, but that's exactly the method you use every single time.
You complain very loudly and expect others to come to your help and
fix stuff without doing any debugging yourself, even though you are
perfectly capable of doing so.
What? So it's out of order
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 24, 2009, at 16:35 , Chris Withers wrote:
Jens Vagelpohl wrote:
Sorry Chris, but that's exactly the method you use every single time.
You complain very loudly and expect others to come to your help and
fix stuff without doing any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Jens Vagelpohl wrote:
Sorry Chris, but that's exactly the method you use every single time.
You complain very loudly and expect others to come to your help and
fix stuff without doing any debugging yourself, even though
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Chris Withers wrote:
Hi,
Is this the case?
Should it be the case?
In any case, how do I customise the site error message in Zope 2.12?
Getting on for a week later and no answer.
Is it really the case that no-one
