On Tue, Jul 19, 2011 at 3:34 PM, Gordana Vitez <[email protected]> wrote: > Hi everyone, > > Thanks to all for providing information and feedback. The patch has been > applied successfully for the libraries of the Niagara Evergreen Consortium. > > Don't you just love it when things work so well, so quickly?!?
Applying the "what can we learn from this" test - perhaps skin-level patches need to be called out separately in the release notes for each release? Without diving into everyone's catalogues, I can't say for sure, but I bet (& hope!) that most sites don't use /opac/skin/default/. The default skin is, of course, what we developers test, so a nice out-of-the-box install of Evergreen will have its bugs fixed, but most other Evergreen instances will not get bug fixes at upgrade time without special attention. The release notes section could look something like: Bug fixes - catalog --------------------------- The following list of catalog bugs were fixed in this release. When you upgrade to this release, your catalog will only benefit from these bug fixes if you are using the 'default' skin; if you are using a customized skin, you will need to apply the same fixes to your own customized version of the listed files. * 744513 - Do not strip apostrophes from advanced searches ** opac/skin/default/js/adv_global.js * ####### - Some other bug ** File 1 ** File 2 This would take a fair amount of effort to pull together, but might be worthwhile if someone(s) is/are willing to step up and do the work.
