There are a variety of pages that display bib details and the like that use the cataloging toolbar:
In order to reduce the risk of bugs like bug 11829 and to eliminate error-prone code duplication, the population of variables required by the cataloging toolbar should be centralized. A couple options include:
- a central routine in the Koha namespace (Koha::Template::Toolbars::Cataloguing?)
- a template block that uses template plugins to fetch the required information
I'm leaning towards the latter so long as the performance penalty of potential repeated fetches in the database isn't too high.
Some feedback on IRC:
<gmcharlt> I would appreciate feedback on bug 11836, as I see a couple different directions for centralizing the cataloging toolbar management code
<huginn`> Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11836 enhancement, P5 - low, ---, gmcharlt, NEW , population of template variables used by cat-toolbar.inc should be centralized
<wajasu> i'd go with the later option, since its presentation specfic. But if you want a test written, the class you mentioned might be easier to write one for.
<gmcharlt> bug 11837 is similar
<huginn`> Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11837 enhancement, P5 - low, ---, gmcharlt, NEW , generation of template-variables used by members-toolbar.inc should be centralized
<wajasu> i have the same problem trying to schedule. let me look at the code.
<gmcharlt> wajasu: actually, I don't think it's any harder to write test cases for template plugins
<gmcharlt> e.g., t/db_dependent/Koha_template_plugin_Branches.t
<wajasu> ok. a plugin.