standard_error_message no longer used in Zope 2.12?
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? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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 knows what's going on here? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----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 knows what's going on here?
Maybe nobody else cares enough to do the debugging you're too lazy to do? ;) Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ8JE2+gerLs4ltQ4RAnyIAJ9ShpEWp/UG5MDbiRR/SXEV44EszgCg1t/1 1KC1leCUCB1HmC8jLQfo7r8= =cb/l -----END PGP SIGNATURE-----
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 magnitude less time for that person to pipe up and say what they did rather than anyone, me included, having to trawl through a million layers of publisher code just to find out what they did. The same goes for WebDAV breaking when you use any kind of Zope 3 views, although I'm guessing that's less of an issue as I suspect the WebDAV sourceport is used by very few people nowadays. standard_error_message, on the other hand, is used pretty heavily, afaik, so I'm surprised more people don't care about it... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----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.
No, it hits the nail on the head. 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. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAknxcLYACgkQRAx5nvEhZLIwlQCfbqfD1Mf91LyIQEJaBKSouwu+ hxcAn1t5mLcqfIui4ffnZ80uQqkdgvlA =z057 -----END PGP SIGNATURE-----
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 of me to ask for whoever made this change to actually speak up and say what they did? Don't be so rediculous... Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
-----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 debugging yourself, even though you are perfectly capable of doing so.
What? So it's out of order of me to ask for whoever made this change to actually speak up and say what they did?
You're not out of order for speaking up. Not at all. However, you're the only person with a deep Zope knowledge who expects that other people do the debugging for him. The whole assumption that a specific committer somehow remembers that a specific code change he or she made breaks whatever you find to be broken is faulty. It's very easy to work on one end of Zope and inadvertently break something at the other end that may not be covered well enough by tests. You cannot just expect that someone will speak up and say "oh yeah, I broke standard_error_message". But you can provide some serious help by doing debugging and pinpointing the issue. The chance that someone will remember what they did and why once you describe the underlying cause will be a lot larger. And they will most likely fix it for you then. jens -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAknx0MIACgkQRAx5nvEhZLLycQCfTxmNPT9PEiNPiuTOC1YoAd0B 7EcAoJGX20wW3E2zWKbDaDKxeBCwx7fg =3689 -----END PGP SIGNATURE-----
-----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 you are perfectly capable of doing so.
What? So it's out of order of me to ask for whoever made this change to actually speak up and say what they did?
You are asserting that somebody made a conscious choice to break 'standard_error_message': it is far more likely that the breakage is an unintended consequence of some other change. Putting your effort into diagnosing the cause will do more to fix the problem than arguing about it. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJ8eH2+gerLs4ltQ4RAnjyAJ40vuPBSiUe/qYsholuXBRj2rjhMgCgqXKn 6KZioYxzmsjjvdXtqU6yc+A= =O1I6 -----END PGP SIGNATURE-----
participants (3)
-
Chris Withers -
Jens Vagelpohl -
Tres Seaver