... necessary, because when setting fields for an upgraded schema,
applyData tries to get the - inexistent - old value from the field to
compare it against the newvalue.
On Tue, 2011-02-15 at 14:34 +0100, Johannes Raggam wrote:
> well, for schema upgrades, also following patch seems to be necessa
well, for schema upgrades, also following patch seems to be necessary:
>From c11064b8d8a7607d41071250f587f097f8c130a3 Mon Sep 17 00:00:00 2001
From: Johannes Raggam
Date: Tue, 15 Feb 2011 14:29:56 +0100
Subject: [PATCH 2/2] gracefully set newvalue for upgraded schemas, where
oldvalue isn't avail
On Tue, Feb 15, 2011 at 1:21 PM, Johannes Raggam wrote:
> while - IMO - zope.schema throws that error justifiably, i think
> zope.formlib should handle it more gracefully in setUpEditWidgets. i
> think, this error comes with every schema upgrade for zope.formlib based
> edit-forms. so, what do you
