Florent Guillaume wrote:
> We can't potentially break currently perfectly working applications.
> I'd propose either:
>
> - introduce a config flag somewhere (zope.conf), off by default,
> switching the zope 2 REQUEST.debug to not using form/cookies/others but
> the proper attribute that zope 3 exp
Philipp von Weitershausen wrote:
Several components that we'd like to use in Zope2, such as the
SequenceEngine from Zope3, use the Zope 3 ZPT engine to render some
things. (This has nothing to do with Zope 2 using or not using the Zope
3 ZPT engine.)
The Zope 3 ZPT engine, in particular
zope.app
Chris Withers wrote:
> Philipp von Weitershausen wrote:
>> Philipp von Weitershausen wrote:
>>> Several components that we'd like to use in Zope2, such as the
>>> SequenceEngine from Zope3,
>>
>> That's meant to say SequenceWidget, and we already *are* using it in
>> Five, so not supporting request
Philipp von Weitershausen wrote:
Philipp von Weitershausen wrote:
Several components that we'd like to use in Zope2, such as the
SequenceEngine from Zope3,
That's meant to say SequenceWidget, and we already *are* using it in
Five, so not supporting request.debug would mean dropping support for
Philipp von Weitershausen wrote:
> Several components that we'd like to use in Zope2, such as the
> SequenceEngine from Zope3,
That's meant to say SequenceWidget, and we already *are* using it in
Five, so not supporting request.debug would mean dropping support for
SequenceWidget or having to reim
