Re: [Django] #13971: Excluding a declared field in ModelForm in form’s subclass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
+--
 Reporter:  mitar   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.2
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Design decision needed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by bloguseer@…):

 Our replica watches are exact copies of the original products. The high
 quality replica watches can make a statement on you wherever you go. Most
 of them come with stainless steel cases and sapphire crystal mineral
 glass.[http://www.bestreplicawatches.co/ replica handbags],
 [http://www.bestreplicawatches.co/replica-watches-omega-c-9_13.html omega
 replica watches],
 [http://www.bestreplicawatches.co/replica-watches-breitling-c-9_42.html
 Breitling replica].

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13971: Excluding a declared field in ModelForm in form’s subclass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
+--
 Reporter:  mitar   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.2
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Design decision needed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by codysomerville):

 * cc: cody.somerville@… (added)


-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13971: Excluding a declared field in ModelForm in form’s subclass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
+--
 Reporter:  mitar   |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Forms   |  Version:  1.2
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Design decision needed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by codysomerville):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 Closing this as a duplicate of ticket:8620

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13971: Excluding a declared field in ModelForm in form’s subclass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
--+
   Reporter:  mitar   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Forms
Version:  1.2 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Design decision needed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+

Comment (by anonymous):

 This bug is highly annoying and completely goes against the rest of the
 framework. Mitar's fix also doesnt do anything for me.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13971: Excluding a declared field in ModelForm in form’s subclass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
--+
   Reporter:  mitar   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Forms
Version:  1.2 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Design decision needed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
Changes (by lsemel):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 Editing the user change form is something that's really common in Django
 projects, and as a new Django user, this was one of the first bugs I ran
 into.  I spent a lot of time wondering if we were doing something wrong
 until I finally found this bug report.  It would be ideal if this were
 fixed in the next version so as not to put off new users.

-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13971: Excluding a declared field in ModelForm in form’s subclass

[Django]

#13971: Excluding a declared field in ModelForm in form’s subclass
--+--
   Reporter:  mitar   |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Forms
Version:  1.2 | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Design decision needed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+--
Changes (by graham_king):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
Django 
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 django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.