Thanks for the response. So what code do I need to add so that, when creating a new object, the admin doesnt try to create related fields that are left entirely blank? I still see core=True as an option, but it no longer does anything, and I still dont understand what the solution is or will be.
Cheers Nick Russell Keith-Magee wrote: > On Feb 2, 2008 4:32 AM, NickJ <[EMAIL PROTECTED]> wrote: > > > > I wanted to bump this up, because if there is no solution I think this > > is an issue which needs to be rectified before it is merged to trunk. > > There is a solution - it just hasn't been documented yet. > > The oldforms 'core=True' approach has been deprecated in favour of > providing a checkbox that specifies that a row needs to be deleted. > When you set up the FormSet, you can specify if rows are deletable; if > they are, you get the checkbox on each row. This can be specified on a > per-form basis, rather than messing up the model definition. > Validation of individual rows (i.e., these three fields are required > as a minimum) is handled by the forms that are wrapped into a form > set. > > If you're still seeing core=True as an option, it's because work isn't > finished yet. There are still pieces of newforms-admin that rely upon > oldforms manipulators - we haven't finished housekeeping yet. > > Yours > Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
