It doesn't happen to me any longer, cause I learned my lesson,
but in the beginning I was always confused about the error message
when an exception happened in the __init__ method of a view.
The Exception gets caught, and interpreted as if the object object/view
does not exist. I then always checked if I made a mistake in my
zcml declaration or did something wrong with names.
It never occured to me that the url was correct, but the __init__
method threw errors.
On Tue, Sep 14, 2010 at 12:00, Marius Gedminas <mar...@gedmin.as> wrote:
> What are the most obscure error conditions you've encountered while
> developing Zopeish applications?
>  ZTK, Grok, Bluebream, the old Zope 3.x KGSes all qualify.
> I'm talking about situations where the error message/traceback are
> disconnected from the actual cause. For example, forgetting to add a
> security declaration in ZCML can cause TraversalError (because
> ForbiddenAttribute is a subclass of AttributeError), which leads the
> developer off to a wild goose chase looking for why the attribute is
> missing (was it misspelled? did it come from an old database?) the first
> few times this kind of error happens.
> One of the goals we came up with in the Zope Summit in Halle was to
> identify the most annoying of these kinds of error messages and fix
> them. I need your help for the identifying part!
> Marius Gedminas
> http://pov.lt/ -- Zope 3/BlueBream consulting and development
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> -----END PGP SIGNATURE-----
> Zope-Dev maillist - zope-...@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> https://mail.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -