# 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).

## Harcoded Stuff¶

This means HTML markup 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. For other elements, we need to use ugly hacks or strange CSS.

The solution is to implement floppy-forms (https://github.com/brutasse/django-floppyforms) with Django.

## Javascripts¶

Some Javascripts are about 5 years old. Others are pretty new. Some are jQuery, some not. Still a bit messy and hard to customize.

see Javascripts.

## Reordering Edit-Inlines¶

First, the can_order attribute is not available with the admin interface. Second, in case of errors, formsets are not returned in the right order. Therefore, reordering inlines is currently only possible with some hacks.

## HTML5 input types¶

There is unpredictable behaviour with certain input types (e.g. number) and Django should remove these types from our point of view (at least with the admin interface). Moreover, form validation should not be moved to the frontend of the admin interface.

see https://code.djangoproject.com/ticket/23075 (although this ticket is marked with “fixed”, the behaviour is still inconsistent)

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).

## The App Index¶

Again, we don’t think customers/editors are interested in your apps.

## Autocompletes¶

As an alternative to Related Lookups it should also be possible to implement Autocompletes. Grappelli includes Autocompletes, but it should be possible without hacking the admin-interface.

## Help text and Many-to-Many Fields¶

The help_text doesn’t show up with M2M-Fields, when using the RawID-Widget (e.g. with Autocompletes). Nothing we can do about that.

## Searching Generic Relations¶

It’s not possible to use a content_object within search_fields.