Here's the solution I came up with to allow sfDoctrineActAsKeyValueStorePlugin
to hydrate default values when injecting objects with the KeyValueStore
behavior, and also to save form values to the key/value store after the form is
submitted and validated.
It should be fairly easy to add support
Sounds like you'll be overriding the form's updateObject() method to
deal with your custom form fields by calling aSet and aGet on the
object.
On Wed, Jun 1, 2011 at 11:38 PM, John Kary wrote:
> I are doing a project where we our client runs ~15 competitions each
> year, but the application form