Django Issues

There are some known problems with the Django admin-interface. I´m going to list them here in order to avoid confusion (because the problems are not related to Grappelli whatsoever). See also: http://code.djangoproject.com/wiki/DjangoDesign
Most of these Issues are around for quite a while and they are unlikely to be solved.

If you think there´s something missing here (or if an Issue has been resolved), please drop me an email.

Reordering Edit-Inlines

UPDATE: We´ve integrated a pure js-based-solution in order to drag/drop inlines with Grappelli 2.2 and newer.

Because in case of errors, formsets are not returned in the right order, reordering inlines is currently not possible.
(Solution seems to be coming ... somewhere.)

see http://code.djangoproject.com/ticket/14238

Translating App Names

It´s not possible to translate the names of apps within the admin-interface which leads to a strange language mix (esp. on the index page).
(There´s already a ticket but IMHO it does not solve the problem.)

Update (2010-09): Currently, this doesn´t work at all (even with using locales).
see http://code.djangoproject.com/ticket/3591

The Admin Index Site

Currently, the admin index site reflects the structure of your applications/models. We don´t think editors (who use the admin site) are interested in the structure of your project/applications. What they want is the most reasonable list of models, divided into different sections (not necessarily apps).
(Solved with Grappelli-Admin-Tools ... but still looking for a better way to handle this issue.)

Admin Site Objects and Related Lookups

If you use different Admin Site Objects, you have to register every related model within every site object you want to use that model for. Grappelli assumes that you registered all models with your main adminsite.
(This is not considered an issue by the django developers.)

Searching Generic Relations

It´s not possible to use a "content_object" within the search_fields. As far as I know, there´s no workaround.
(I´m not sure if this will be solved.)

Messages in Admin

It´s currently not possible to distinguish between Success- and Error-Messages. (Solved with the most recent version of Django.)

M2M RawID Field has no Unicode representation

see http://code.djangoproject.com/ticket/10293 ... the Patch provided there does work.

Popups, Actions and list_editables

With the current version of Django, Actions are visible within popups but delete confirmation doesn´t handle popups correctly. Moreover, list_editables are also visible. From our point of view, editing elements shouldn´t be possible with popups (and hasn´t been before actions are introduced).

see http://code.djangoproject.com/ticket/11700

Admin Documentation

The document structure of the admin_doc templates is a bit messy (about every second template has a different structure). Therefore, it´s hard to style these pages. Trying to do our best to give it a decent look though.

Moreover, all admin-views lead to an error.

Admin Documentation: Translation

Translation of the Admin Documentation is half-baked.

ModelAdmin Media Definitions

There´s no distinction between Media for Change-Forms and Media for the Changelist. If you define to load TinyMCE within your Model, it´s already loaded in the Changelist. The same goes for Stylesheets.

We think there should be distinctive Media-Classes for Change-Form and Changelist. Although it´s not that important, because the javascripts & stylesheets are in your browser-cache anyway.

Harcoded Stuff

With "Hardcoded Stuff", I´m referring to HTML-Code within Views (instead of using Templates). There´s a lot of this within the Admin-Interface and therefore it´s just not possible to style some elements.
(Solved with Grappelli ... to be released soon.)

HTML/CSS Framework

For the Admin-Interface to be customizable, flexible and extensible, we need a coherent scheme with either HTML and CSS. If one wants to customize the change-form for example, it shouldn´t be like "ok, let´s add a new block ... let me think ... there´s no class for what I want ... so let´s just add a new class". instead it should be like "ok, let´s add a new block ... I´m checking the HTML/CSS docs ... finding the right class ... done." otherwise, almost every 3rd-party app using the admin-interface ends up with custom styles and code-blocks.
(Solved with Grappelli ... to be released soon.)