Conflict of overriding core views
Added by Pok Lau almost 14 years ago
I was curious about what happen if there is more than one plugins are overriding the Redmine core views. So I made a copy of the issues/show.rhtml file and put the file into two different plugins, make some customisation by adding
In plugin_a/app/issues/show.rhtml
<hr />
<p><strong>Test override view in plugin a</strong></p>
and in plugin_b/app/issues/show.rhtml
<hr />
<p><strong>Test override view in plugin b</strong></p>
What I found is Redmine pick up the plugin_a one and ignore the plugin_b one. Wondering if the engine is interested in the one comes arphabetically earlier, so I move the customised issues/show.rhtml from plugin_a to plugin_c.
Guess what happen this time? Yes, it displays the plugin_b one.
Assuming in a Redmine system, there is a couple of projects that require different plugins and there are more than one plugins wanting to override the same core view, (for example in project A, I need functionality in plugin A that overrides issues/show.rhtml; then in project B, plugin B is required, so both plugin A and plugin B are installed in the system)is there a way for Redmine to handle this?
Replies (1)
RE: Conflict of overriding core views
-
Added by Felix Schäfer almost 14 years ago
Redmine provides (some) view_hooks for stuff like that, feel free to ask for more if those aren't enough.