Opened 12 years ago
Closed 12 years ago
#617 closed enhancement (cant-reproduce)
Replacing template hooks by templates override
| Reported by: | Tumulte | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | programming | Keywords: | |
| Cc: | Parent Tickets: |
Description
I've toyed a bit with template hooks, and I must say I'm not so very fond of it.
The thing I dislike is that you have to modify templates. That is to say that some part of the plugin behavior is outside of the plugin.
I think it'd be a way better idea to add an overriding system for plugins, in that order
Base templates -> themes -> plugins (plugins win all the time).
That said, it can be a good idea to add hooks in some places you'd expect to be modified often (in the forms before the submit, at the end of media data's template...)
Note:
See TracTickets
for help on using tickets.
Actually this already works exactly as you said with base templates -> themes -> plugins. (I think themes actually might get priority, I don't remember, one of them does).
The template hooks is a *new feature* that allows you to not have to do that in common places, so that multiple plugins can edit things at the same time.
So basically, this is already a feature! I can walk you through how to do it on IRC.