Hello,

exactly, and I'm advocating it's a real bug... :-)

If you need to save something even if the validation fails at a later point, you can do a full commit at anytime. The same is not true when trying to abort something that you don't know that will fail...

With the current Archetypes/CMFFormController integration it is impossible... :-/

My particular use case is the following:

- There's an AT content-type, and its schema has a reference field

- This field uses a special widget (UploadReferenceWidget) that allows you upload a file, creating a new File in ZODB *and* reference that File after its creation

- What happens now is that when the validation of any other field fails, I have no chance to abort the creation of that File

I'm talking specifically about ZODB here, but the same would apply for RDB and file system changes. Again, if the validation fails, I would expect that *no* persistent changes remains.

The fix could be done in Archetypes, but 'form processing' is a more general concept, and thus I would say that CMFFormController is the best place to do it.

And last, but not least, the proposed fix has tests and none of the existing CMFPlone, Archetypes, ATContentTypes, CMFFormController, CMFEditons, ..., tests fails after applying it... ;-)

--

_______________________________________________________

Dorneles Treméa · Developer, Jarn · www.jarn.com

Plone Solutions, Development, Hosting and Support

_______________________________________________________

Plone Solutions is now known as Jarn www.jarn.com/name-change