[OPEN-ILS-GENERAL] apostrophe in title search causing

[Yamil Suarez]

Tom,

I would love to see a simple summary of your workflow using Git to  
keep track of new changes to the default skin. Though I understand  
that it might not translate if one is starting from a tarball based  
installation.

Thanks,
Yamil

P.S. Congrats





On Jul 20, 2011, at 12:00 PM, open-ils-general-request at list.georgialibraries.org 
  wrote:
>
> ------------------------------
>
> Message: 3
> Date: Tue, 19 Jul 2011 15:57:44 -0400
> From: Thomas Berezansky <tsbere at mvlc.org>
> Subject: Re: [OPEN-ILS-GENERAL] apostrophe in title search causing
> 	problems(Bug #744513)
> To: open-ils-general at list.georgialibraries.org
> Message-ID: <20110719155744.35533kygwh0nd88w at mail.mvlc.org>
> Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed"
>
> 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.
>
> Thomas Berezansky
> Merrimack Valley Library Consortium
>
>
> Quoting Dan Scott <dan at coffeecode.net>:
>
>> On Tue, Jul 19, 2011 at 3:34 PM, Gordana Vitez
>> <gvitez at 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, 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.
>>
>
>
>
>
> End of Open-ils-general Digest, Vol 61, Issue 24
> ************************************************