Version 42 (modified by Simon G. <dev@…>, 8 years ago) (diff)

Removed some closed/stale tickets

Feature Grouping


This page was created as a way to collect tickets, wiki pages, etc. that have similar goals. A ticket keyword just isn't enough sometimes. Add a group, description, analysis, and/or links about a feature you are interested in. If there is too much information about the feature to fit on this page, then create a wiki page dedicated to that feature and link to it here.

Please note that there is already a grouping of VersionOneFeatures.


All of these might be the same thing: auto_now_add tickets

Cache System

A few tickets that seem to relate to the same problem with using the 2.4 decorator syntax for cache_page: (#1015, #2564, #2567)

contrib.comments rewrite

  • #3546 - Add timestamp and user for edits to Comment/FreeComment in contrib.comments
  • #1829 - refactor comment urls
  • #2134 - add comment object to comments/posted template
  • #1853 - admin documentation section errors for 'comments' tags
  • #2177 - include Free Preview and Posted Templates for Comments App (has patch)
  • #2228 - Add e-mail and URL to free comments (with patch, design. dec. needed)
  • #3091 - Add 'extra_context' and 'context_processors' to django.contrib.comments (with patch)
  • #3473 - Karma creation broken (with patch)
  • #3546 - Add timestamp and user for edits to Comment/FreeComment
  • #4189 - Fix for COMMENTS_BANNED_USERS_GROUP exploding the ORM when using the templatetag

edit_inline Issues

Many of these will be obsoleted by newforms-admin and subsequent changes after 0.96

  • Multiple FileFields & edit_inline interaction overwriting preceeding files (#2413, #792)
  • interacting with a specific unique_together ordering (#2470, #526, #2415)
  • problems with unique (#565)
  • edit_inline deleting stuff (#3425)
  • validator issues: (#265, #1690, #3043)
  • Manipulator allowing "stealing" of related objects (#3145)
  • Multiple Foreign Keys (#1939 & another 3 or 4 tickets marked as dupes)
  • Not using a sensible default state (#2159)
  • Causing KeyError, when follow=False in manipulator constructor or editable=False in model definintion (#2434, #1603)
  • OneToOne fields (#24)
  • Ignoring things with core=True (#2724)
  • Non-working prepopulate from (#957)
  • A possible better way of doing things (which Adrian says is "fantastic") #2248 (*note: backwards incompatible change)
  • Problem with auto_now_add (#1030)
  • Admin ordering not working (#2679)
  • feature: Javascript adding/deleting in admin interface (#13)
  • collapsing in admin interface (#494)
  • OneToOne edit_inline - can not add new object in Django admin (#3662)
  • OneToOne field - ChangeManipulator looks for related primary key (#3188)

Incorrect SQL construction

There are a bunch of these, so here's a placeholder for them. Many are already assigned to mtredinnick; the remainder should be. I'm working on a rewrite of the query creation portion of QuerySets -- Malcolm.


Current manipulator tickets should be tested with newforms to make sure the problems aren't repeated

Feature requests that need a decision on whether or not to add to newforms

Tickets still need to be looked at:


There are a few tickets aiming to add features to the Paginator class, and even a new implementation by Adrian in #1374. There is also code for a PaginatorTag.

Ability to disable admin pagination
The pagination module should have some limit, or a warning should be given in the documentation
Optimisation idea for Paginator object
Refactor the admin paginator customizations to make them reuseable

Reimplement the DatabaseFeatures.supports_select_related flag
Add a friendly error report when using select_related() on a reverse relation

Splitting models into separate files



admin list_editable with unique_together raises Integrity Error
TextField with unique (or in unique_together) constraint breaks for large inputs in Postgres
Unable to have abstract model with unique_together
Index ordering in index_together and unique_together
Cannot drop unique_together constraint on a single field with its own unique=True constraint
inspectdb does not properly handle renamed fields for unique_together

Web services / REST


  • Models CRUD via web services (#115) with a lot of duplicates
  • [patch] XMLRPC support for django (#547) for part of a solution (set as duplicate of #115)

On the web:

On mailing-lists:

Back to Top