On Tuesday, January 13, 2004, at 11:21 PM, Travis Miller wrote:
hi Dirk,
i just (configure/make/make install)ed Zope-2.7.0-b4 and i immediately
ran into the .min/.max/... security changes when i tried to rename an
object through the ZMI.
I got around the min/max by adding them to the list on
hi Dirk,
i just (configure/make/make install)ed Zope-2.7.0-b4 and i immediately
ran into the .min/.max/... security changes when i tried to rename an
object through the ZMI.
i tried your patch but after the change, zopectl errors when run:
[EMAIL PROTECTED]:~> ./InstanceHome27b4/bin/zopect
Dirk wrote:
Hi Johan,
maybe the patch can fix your problem.
Thanks!
--
Johan Carlsson Tel: + 46 8 31 24 94
Colliberty Mob: + 46 70 558 25 24
Torsgatan 72Email: [EMAIL PROTECTED]
SE-113 37 STOCKHOLM Skype: colliberty
___
Hi Johan,
maybe the patch can fix your problem.
Regards,
Dirk--- DT_Util.py.orig Sat Jan 10 22:58:45 2004
+++ DT_Util.py Sat Jan 10 22:56:43 2004
@@ -58,6 +58,11 @@
else:
d[name] = f
+from AccessControl.ZopeGuards import guarded_min, guarded_max
+
+d['min'] = NotBindable(guar
Since the new security release for Zope 2.6.3 (and 2.7) the _.min and
_.max doesn't work any more.
But they are still used by the ZMI in the following places:
OFS\dtml\properties.dtml(140): size="">
OFS\dtml\properties.dtml(152): size="">
OFS\dtml\propertyType.dtml(93): size="">
OFS\dtml\renameFo
