Hi Gordana,
We're using 2.0.6, but we've applied by hand several patches from 2.0.7
and the upcoming 2.0.8. Trying a search on our system for a title with
an apostrophe such as boys don't cry worked just fine without any
change to the search terms. I tested this in our staff client and OPAC
and
Hi Ben,
Thanks for you suggestion. Just after the upgrade to 2.0.7, all of our
computers were upgrade to Windows 7 so everything was wiped clean.
Nevertheless, I did try clearing the cache for staff client and web browsers
and still came up with the problem.
I'll follow the bug ticket as
Hello Gordana,
This was a skin level fix, so since you are using a custom skin ('nc'), it must
be applied manually to your skin after upgrading. Since the fix is simply
deleting a single line, it should be pretty simple to take care of. See here
to view the actual change needed:
, July 19, 2011 12:57 PM
To: open-ils-general@list.georgialibraries.org
Subject: Re: [OPEN-ILS-GENERAL] apostrophe in title search causing
problems (Bug #744513)
Hi Gordana,
We're using 2.0.6, but we've applied by hand several patches from 2.0.7
and the upcoming 2.0.8. Trying a search on our
On Tue, Jul 19, 2011 at 1:04 PM, Dan Wells d...@calvin.edu wrote:
Hello Gordana,
This was a skin level fix, so since you are using a custom skin ('nc'), it
must be applied manually to your skin after upgrading. Since the fix is
simply deleting a single line, it should be pretty simple to
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?!?
Thanks again!
Gordana
Dan Scott d...@coffeecode.net 7/19/2011 1:27
On Tue, Jul 19, 2011 at 3:34 PM, Gordana Vitez gvi...@niagaracollege.ca 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,
MVLC uses git to maintain a branch specifically for changes to the
default skin. We thus use default with those changes. Might
documenting how we are (or rather, I am) doing this be of benefit?
Note that we have an easier time of this, as we install off of git,
not off of tarballs.
