Please consider incorporating a doc patch (attached to #11313) for this 
release, and backpatching it to previous docs (1.1 - 1.4).

The current implementation of list_editable in the Django admin is 
fundamentally broken in the face of possible changes to the data while the 
list page is up in the browser.  It has caused data destruction in our 
organization, and others.

When I get my head above water, I would be glad to help out actually fixing 
the bug, but I find it unconscionable that a known critical bug like this 
be allowed to continue to trap new users.  It should never have been marked 
as a new feature. The doc patch is simple and to the point, and was 
requested by otheres twice 13 months ago and 3 years ago, when there was 
activity on this bug in the past.

Thanks,

Fred Cox

----- Forwarded Message -----
*From:* Django <nore...@djangoproject.com>
*To:* 
*Cc:* django-upda...@googlegroups.com 
*Sent:* Tuesday, December 4, 2012 1:44 PM
*Subject:* Re: [Django] #11313: list_editable fields don't support 'save' 
in multiuser environment

#11313: list_editable fields don't support 'save' in multiuser environment
--------------------------------+--------------------------------------
    Reporter:  margieroginski  |                    Owner:  nobody
        Type:  Bug            |                  Status:  reopened
    Component:  contrib.admin  |                  Version:  1.1-beta-1
    Severity:  Normal          |              Resolution:
    Keywords:                  |            Triage Stage:  Accepted
    Has patch:  1              |      Needs documentation:  1
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
--------------------------------+--------------------------------------
Changes (by aaugustin):

* severity:  Release blocker => Normal


Comment:

1.5 beta has been released. At this stage, only tickets that must be fixed
for RC1 can be release blockers.

Please don't abuse Trac's flags to push your personal agenda at the
expense of everyone else who's waiting for 1.5 final.

If you want to drive more attention to this issue, please write to the
django-developers mailing list.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/11313#comment:18>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/3FR94650of8J.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to