3 ms·
> * Adding a link to a custom page onto the frontpage of the admin, ideally under a custom "App" header. This one's simple—just override base_site.html. As fo
by theli0nheart 9y ago
> * Adding a link to a custom page onto the frontpage of the admin, ideally under a custom "App" header.
This one's simple—just override base_site.html.
As for the others, I'm not really sure I understand what creating a read-only view / form for nested 1-1 objects means, but I'm sure there's a decent, not so crazy solution out there.
- Alex3917 9y ago> just override base_site.html And if your changes break in a future version of Django, how exactly is anyone going to be able to debug that? Having to override admin templates that are at best only semi-documented is incredibly hacky.
- theli0nheart 9y agoWith any Django app, you’re going to pin your requirements to a specific Django version as a matter of course. If the change is broken in a future Django version, you’d need to update it like you would need with any other breaking change. But, if experience is any guide, despite lots of tinkering with the admin, Django has yet to break anything I’ve customized in the admin (I’ve been using Django since 0.96). YMMV.
- Daishiman 9y agoDjango has the best deprecation policy of any framework I've seen. Breaking changes are always documented and given fair advance for changes. In many years of working with Django I have not really seen a significant breaking change in the admin unless you override private methods.