Opened 9 years ago
Last modified 7 years ago
#26028 closed New feature
Improve instructions for overriding Django templates — at Version 6
Reported by: | Daniel Greenfeld | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.9 |
Severity: | Normal | Keywords: | |
Cc: | berker.peksag@… | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description (last modified by )
For dj-stripe, I get asked how to do this a lot. Rather than include instructions on how to do this in that third-party package, shouldn't this be improved in the core documentation?
Reference discussion: https://github.com/pydanny/dj-stripe/pull/254#issuecomment-168515982
Existing instructions on template overriding:
Change History (5)
comment:1 by , 9 years ago
Description: | modified (diff) |
---|
comment:2 by , 9 years ago
Description: | modified (diff) |
---|
comment:4 by , 9 years ago
comment:5 by , 9 years ago
Triage Stage: | Unreviewed → Accepted |
---|---|
Type: | Uncategorized → New feature |
comment:6 by , 9 years ago
Description: | modified (diff) |
---|---|
Summary: | Improve instructions for overloading Django templates → Improve instructions for overriding Django templates |
Note:
See TracTickets
for help on using tickets.
When I was researching how to customize third-party apps, I found this blog entry very useful for a rapid overview:
http://blog.yourlabs.org/post/19777151073/how-to-override-a-view-from-an-external-django-app
I also recently discovered this third-party app loader that allows one to extend templates, rather than replace them completely:
https://pypi.python.org/pypi/django-apptemplates/
From IRC discussions, it sounds like quite a few experienced people use forking for customization. It would be good to have clear guidelines about how to avoid forking , as well as guidelines on how to correctly do forking when you really have to.