At 15:49 09/09/99 , Evan Simpson wrote:
Errors which occur before the URL is fully resolved, and the resulting object called, generate hardwired error pages. Only after that process is complete is there an acquisition context in which standard_error_html can be found.
I'm not sure if there's a better way to handle it.
Maybe use the context build up until the error occurs? /a/b/c/*BANG* use /a/b/c/standard_html_error /a/b/c/d/*BANG* use /a/b/c/d/standard_html_error.. -- Martijn Pieters, Web Developer | Antraciet http://www.antraciet.nl | Tel: +31-35-7502100 Fax: +31-35-7502111 | mailto:mj@antraciet.nl http://www.antraciet.nl/~mj | PGP: http://wwwkeys.nl.pgp.net:11371/pks/lookup?op=get&search=0xA8A32149 ------------------------------------------