On Jun 7, 4:44 pm, "Diez B. Roggisch" <[email protected]> wrote: > On Jun 7, 2011, at 9:58 PM, Noah Davis wrote: > > > Adding strip_name=True to the form resulted in non-mangled field names > > ('firstname' rather than 'person_form.firstname'), but still allowed > > me to pre-populate the fields (which, as per the TW documentation, I > > was unable to do with unnamed widgets). This seems to have solved the > > immediate problem. As an aside, show_errors=True does not appear to > > function correctly under this circumstance, either. Thank you much for > > the help. And if there's any further testing I can help with... > > The whole error-showing-business was quite a mess when using complex forms > with nested parts. For our own fork of TW1, I fixed that. I can see if I can > backport that, if it solves the issues. > > What would of course help tremendously would be a simple demo-app > (quickstarted) that exhibits the problematic behavior. Then I can recreate & > fix the problem.
I've hacked together a quickstarted app that shows the behavior. But I'm still new to this, so what's the best way to package it (I've tried generating eggs in the past with limited success) ? And would you rather have it attached to something, or stuck somewhere? > > diez -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
