I haven't done that before, so I'll have to figure out how to do it. Thanks for the advice....I'll look into doing that, because I have seen this recommendation made to others, so I should probably learn.
However, in the meantime, I think I may have a theory as to why this is happening. When the error was reproduced for me, it seems to happen only during certain errors uploading attachments using the MultiFileUploadField. Now that certain other issues were fixed with this control, I can only reproduce this problem by trying to upload a file larger than the maximum set in Form#setMaxSize. What you said earlier, about how only fields that failed validation should fail to be retained in the form, got me to thinking: since this restriction is set in the Form object, does that block the model update for ALL fields? That would make sense, but it would also make this method nearly unusable except on a dedicated form (i.e. a form used only for uploading files). In that case, I'm better off manually validating upload size. On Tue, Jul 20, 2010 at 5:13 PM, Jeremy Thomerson <jer...@wickettraining.com > wrote: > On Tue, Jul 20, 2010 at 1:22 PM, Ray Weidner < > ray.weidner.develo...@gmail.com> wrote: > > > > > > > Back to the original question, when you say "all changes to the form > > > are lost" - do you mean that the form rerenders with absolutely no > values > > > filled out? Only the fields that failed conversion or validation > should > > be > > > blank. > > > > > > See, that throws me off, too. Yes, the supposedly valid fields are not > > being preserved after submit and fail validation. I would have thought > > that > > they should have been preserved, LDM be damned, but they aren't, so that > > was > > my theory as to what was causing this. > > > > So if that's not causing it, what could be causing such a thing? I'd > > including source code here, but I'm not even sure what part is causing > the > > problem, so that would be a lot of code. Any ideas? > > > Best thing to do is try to create a quickstart that reproduces it. > Typically, you find your error while doing this. If not, you have > something you can give us that we can quickly run to debug your problem. > > -- > Jeremy Thomerson > http://www.wickettraining.com >