Hi Roger,
I finally got it sorted. The class providing the error handling needed
to implement our view marker interface, so the solution was:
class VortexNotFoundPagelet (NotFoundPagelet):
zope.interface.implements (IVortexBrowserView)
and:
I'm not sure if this will
Regards
Roger Ineichen
_
END OF MESSAGE
> -Ursprüngliche Nachricht-
> Von: zope3-users-boun...@zope.org
> [mailto:zope3-users-boun...@zope.org] Im Auftrag von andrew
> Gesendet: Dienstag, 20. Januar 2009 22:54
> An: zope3-users@zope.org
> Betreff: [Zope3-U
Hi All,
I'm having a problem setting up a custom error page using the
z3c.pagelet approach, which I'm using successfully for other pages in my
app. I've tried configuring my error pages as such:
but when I trigger, e.g., a not found error I get:
2009-01-21T10:45:43 ERROR Site
On Tue, Jan 20, 2009 at 07:46:28PM +0100, Adam GROSZER wrote:
> Hello Paul,
>
> We're doing here in an overrides.zcml:
>
>
> where ./zope.pot and language folders exist
Thanks Adam. I just tried that - it seems that my new directory
becomes the only source of all translations for that domain;
Hello Paul,
We're doing here in an overrides.zcml:
where ./zope.pot and language folders exist
Tuesday, January 20, 2009, 6:04:32 PM, you wrote:
PW> If I have a zope 3 (actually a Five) application that ships with some
PW> translations, is it possible to provide an alternate .po or .mo file
PW
If I have a zope 3 (actually a Five) application that ships with some
translations, is it possible to provide an alternate .po or .mo file
that overrides the default translations? How do I ensure that my
translations take precedence?
We had a hack that did this job at product initialization time
