On Tue, Sep 4, 2012 at 3:38 AM, Frankline wrote:
I'm creating a site in Python/Django and feel that the admin backend, as
good as it is, may not be a one-fit-for-all situations.
My question is this:
Have any of you ever had a need to have a custom admin backend?
Only just yesterday...
In what example situations would one create his/her own admin backend rather
than using the default admin panel that ships with Django?
I think it's only recently that the documentation actually reflected
the idea that the Django Admin should be used in production. I did a
very simple site w Django 2 years ago and was mocked in IRC for using
the built in django admin: "you are not doing it right". I'm pretty
thick skinned and ignored the comment, but I think it was usual to
write what you needed rather than let the client use the provided back
Anyway, to the question. Once the models, the intermediate models and
the interactions between all of them start getting sufficiently
complex, you will need to put new forms on front. Theoretically, you
don't want to store a "date" variable more than once for instance -
especially amongst things that are linked. my eg: School student
information system: courses, enrolments, tutorials, timetables,
students, attendance records and marks - the timetables, tutorials and
attendance will all need a date, but you only want one.
Using the provided admin to do this is possible, but it then creates
complex work flows and documentation - putting a new form on front can
smooth it out for users.
What are the disadvantages of rewriting your own backend?
It's more work, more code, more files = greater complexity, more
places to go wrong.