-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13/01/2004, at 4:19 PM, Stuart Bishop wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The 'security audit work for the 2.7 branch' commit on 8th Jan made
the following change in PageTemplates/Expression.py:
As well as in other locations such as
Dear Sir or Madame I'm wrigting because I started to do a plone site in
zope.I would lke to know if I can change the url and/or port where the plone
site stays.I would like to know how to chenge this path
http:\\localhost:8080\Plone.
Yours faithfully,
Fábio Afonso
I forward-ported these to the 2.7 branch & the head. Any testing
you can do to make sure I didn't break anything would be appreciated.
Brian Lloyd[EMAIL PROTECTED]
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -Original Message-
> From
+1
I think the problem is same as reported by Kazuya Fukamachi
http://mail.zope.org/pipermail/zope-dev/2003-December/021315.html
and me.
http://mail.zope.org/pipermail/zope-dev/2003-December/021338.html
At least this is important problem in Japanese (maybe Korea and Chinese)
developpers.
>Hi t
On Wednesday 14 January 2004 09:20, Yuppie wrote:
> Did you see my other mail? Adding 'hasattr' (not 'guarded_hasattr') to
> _NEED_WRAPPING works for me.
Thanks for the clarification. Now it works.
Robert
___
Zope-Dev maillist - [EMAIL PROTECTED]
ht
Hi there,
Some changes in Zope 2.7 break the possibility to make management_page_charset
a callable (for instance a method).
This breaks Formulator, as it uses this facility. This works just fine
in Zope 2.6, but breaks in Zope 2.7.
The silly thing is that Formulator 2.6.0 breaks in Zope 2.7 ex
Hi Robert!
robert wrote:
I found this,
however 'has_order_support' is not the third argument.
That is why I do not unterstand what happens.
[...]
_.hasattr(this().aq_self, 'has_order_support')
I don't know that code very well, but this is how I understand what happens:
All names in the TemplateDi