#2724: edit_inline ... foreignkey(core=True) bug
-------------------------------------------+--------------------------------
   Reporter:  [EMAIL PROTECTED]             |                Owner:  adrian     
    
     Status:  closed                       |            Component:  Admin 
interface
    Version:  SVN                          |           Resolution:  worksforme  
   
   Keywords:  rel, core=True, edit_inline  |                Stage:  Accepted    
   
  Has_patch:  1                            |           Needs_docs:  1           
   
Needs_tests:  1                            |   Needs_better_patch:  0           
   
-------------------------------------------+--------------------------------
Changes (by [EMAIL PROTECTED]):

  * status:  new => closed
  * needs_tests:  0 => 1
  * keywords:  => rel, core=True, edit_inline
  * needs_docs:  0 => 1
  * has_patch:  0 => 1
  * resolution:  => worksforme

Comment:

 Please tell me if that patch works for you.
 It is working for me for using core=True on child members,
 in a very simple Poll/Choice app:
 
 Choice model:
 {{{
 
 class Choice(models.Model):
       poll   = models.ForeignKey(Poll, edit_inline=models.TABULAR, \
         max_num_in_admin=3, num_extra_on_change=0)
       choice = models.CharField(maxlength=200, core=True)
       votes  = models.IntegerField(core=True, default=0)
       def __str__(self):
           return self.choice
       class Admin:
             pass
 }}}
 
 As a work-around, apply the patch and use max_num_in_admin and
 num_extra_on_change
 to see if it makes any differences.. It seems to break things without
 theses, but
 with the following changes, it doesnt show any error while trying to add
 new polls
 in the admin. As a side-note, I havent found good docs for the rel
 attribute,
 what is this for anyway ??

-- 
Ticket URL: <http://code.djangoproject.com/ticket/2724#comment:6>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django updates" 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/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to