- Koha-devel - lists.koha-community.org

question about git install
by Samuel Desseaux 02 May '13

02 May '13

Hi! I've made a git install of koha. I've followed these instructions git clonehttp://git.koha-community.org/koha.git kohaclone cd kohaclone git checkout 3.10.04 So, when i make a git status, i've this # On branch v3.10.04 # Untracked files: # (use "git add <file>..." to include in what will be committed) # # MYMETA.json # MYMETA.yml # Makefile # blib/ # koha-tmpl/intranet-tmpl/prog/fr-FR/ # koha-tmpl/opac-tmpl/prog/fr-FR/ # pm_to_blib nothing added to commit but untracked files present (use "git add" to track) But, after installation, i'm on 3.11 (so, the next version). How can i solve this problem? Best regards samuel

3 4

Re: [Koha-devel] Koha-devel Digest, Vol 90, Issue 4
by David Cook 02 May '13

02 May '13

Hi Nicholas: Slick display! Perhaps someone else has already raised the idea, but might you consider filing a bug in Bugzilla where you can provide the perl, template, css, and images? That'll make it easier to share with others :). http://bugs.koha-community.org/bugzilla3/ David Cook Systems Librarian Prosentient Systems P/L ABN 31 078 409 168 72/330 Wattle St, Ultimo NSW 2007 tel: 02 92120899 fax: 02 92120885 dcook(a)prosentient.com.au -----Original Message----- From: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] On Behalf Of koha-devel-request(a)lists.koha-community.org Sent: Thursday, 2 May 2013 3:06 PM To: koha-devel(a)lists.koha-community.org Subject: Koha-devel Digest, Vol 90, Issue 4 Send Koha-devel mailing list submissions to koha-devel(a)lists.koha-community.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel or, via email, send a message with subject or body 'help' to koha-devel-request(a)lists.koha-community.org You can reach the person managing the list at koha-devel-owner(a)lists.koha-community.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Koha-devel digest..." Today's Topics: 1. Re: New books display for koha (Nicholas van Rheede van Oudtshoorn) ---------------------------------------------------------------------- Message: 1 Date: Thu, 2 May 2013 13:05:51 +0800 From: Nicholas van Rheede van Oudtshoorn <vanoudt(a)gmail.com> To: koha-devel(a)lists.koha-community.org Subject: Re: [Koha-devel] New books display for koha Message-ID: <CAJ1eDORER-nZutQWPp05BYFg3caAkHq+8QjaDW91QG34v797Kg(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" I should also mention that it can be seen running live at http://library.pbc.wa.edu.au/ :-) Nick On Thu, May 2, 2013 at 12:58 PM, Nicholas van Rheede van Oudtshoorn < vanoudt(a)gmail.com> wrote: > Oh, and of course one needs some css to make things look pretty! :-) > > /* Book Cover Display */ > div#newbooks { > background-color: rgba(69, 34, 17, 0.8); > background-image: -webkit-repeating-linear-gradient(left , > rgba(0, 0, 0, 0.1), transparent 30px), > -webkit-repeating-linear-gradient(left, > rgba(0, 0, 0, 0.1), transparent 50px), > -webkit-repeating-linear-gradient(right, rgba(0, 0, 0, 0.1), > transparent 70px), url(/noise.png) !important; > background-image: -moz-repeating-linear-gradient(left, rgba(0, > 0, 0, 0.1), transparent 30px), -moz-repeating-linear-gradient(left, > rgba(0, 0, 0, 0.1), transparent 50px), > -moz-repeating-linear-gradient(right, rgba(0, 0, 0, 0.1), transparent 70px), url(/noise.png) !important; > background-image: -ms-repeating-linear-gradient(left, rgba(0, > 0, 0, 0.1), transparent 30px), -ms-repeating-linear-gradient(left, > rgba(0, 0, 0, 0.1), transparent 50px), > -ms-repeating-linear-gradient(right, rgba(0, 0, 0, 0.1), transparent 70px), url(/noise.png) !important; > background-image: -o-repeating-linear-gradient(left, rgba(0, > 0, 0, 0.1), transparent 30px), -o-repeating-linear-gradient(left, > rgba(0, 0, 0, 0.1), transparent 50px), > -o-repeating-linear-gradient(right, rgba(0, 0, 0, 0.1), transparent 70px), url(/noise.png) !important; > background-image: repeating-linear-gradient(left, rgba(0, 0, > 0, 0.1), transparent 30px), repeating-linear-gradient(left, rgba(0, 0, > 0, 0.1), transparent 50px), repeating-linear-gradient(right, rgba(0, > 0, 0, 0.1), transparent 70px), url(/noise.png) !important; w } > > div.bookshelf { > background-image: url(/bookshelf.png); > background-size: 100% 190px; > vertical-align: bottom; > padding-top: 5px; > border: 10px solid #452211; > border-bottom: none; > background-color: transparent; > text-align: center; > } > > .bookshelf .bookCover { > display: inline-block; > margin-bottom: 40px; > margin-right: 10px; > } > > .thumbnail { > box-shadow: 2px 2px 2px 0 rgba(0,0,0,.7); > max-height: 150px; > border-radius: 2px 6px 6px 2px; > border: 1px solid rgba(0, 0, 0, .7); > min-height: 150px; > } > > td .thumbnail { > min-height: 114px; > max-height: 114px; > } > .bookCover .thumbnail, .bookCover .fakeCover { > border-radius: 2px 6px 6px 2px; > box-shadow: 2px 2px 2px 0 rgba(0,0,0,.7); > max-height: 150px; > height: 150px; > } > .biblio > .bookCover .thumbnail, .biblio > .bookCover .fakeCover { > -webkit-transform:skewy(-4deg); > -moz-transform:skewy(-4deg); > -ms-transform: skewy(-4deg); > -o-transform: skewy(-4deg); > transform: skewy(-4deg); > } > > .biblio > .bookCover:hover .thumbnail, .biblio > .bookCover:hover > .fakeCover { > box-shadow: 0 0 4px 2px rgba(255,255,255,.7); > -webkit-transform:skewy(0deg) scale(1.33); > -moz-transform:skewy(0deg) scale(1.33); > -ms-transform:skewy(0deg) scale(1.33); > -o-transform:skewy(0deg) scale(1.33); > transform:skewy(0deg) scalue(1.33); } span.shelfhint { > opacity: 0; > position: absolute; > top: 0px; > left: 0px; > width: 100%; > height: auto; > color: white; > z-index: 30; > background-color: black; > border-top-left-radius: 2px; > border-top-right-radius: 6px; > font-size: x-small; > -webkit-transition: all .5s ease-in-out 0s; > -moz-transition: all .5s ease-in-out 0s; > -o-transition: all .5s ease-in-out 0s; > -ms-transition: all .5s ease-in-out 0s; > transition: all .5s ease-in-out 0s; } > > a.biblio:hover > span.shelfhint { > opacity: .6; > -webkit-transition: all .5s ease-in-out 0s; > -moz-transition: all .5s ease-in-out 0s; > -o-transition: all .5s ease-in-out 0s; > -ms-transition: all .5s ease-in-out 0s; > transition: all .5s ease-in-out 0s; } > > .biblio:before { > background-color: rgba(0,0,0,.6); > width: 40px; > height: 105px; > bottom: 60px; > left: -15px; > box-shadow: 0 0 20px 10px rgba(0,0,0,.6); > display: block; > position: absolute; > content: ""; > -webkit-transform: skewx(15deg); > -moz-transform: skewx(15deg); > -ms-transform: skewx(15deg); > -o-transform: skewx(15deg); > transform: skewx(15deg); > z-index: 0; > } > > a.biblio { > text-decoration: none; > display: inline-block; > margin: 0 8px; > height: 190px; > vertical-align: bottom; > position: relative; > margin-left: 15px; > } > > #bookcover div.fakeCover { > margin: 1em .5em .5em; > } > div.fakeCover { > background-color: #54300c; > background-image: url(/leather.png), > -webkit-linear-gradient(left, transparent, rgba(0, 0, 0, 0.1) 1px, > rgba(0, 0, 0, 0.5) 4px, transparent 8px); > background-image: url(/leather.png), > -moz-linear-gradient(left, transparent, rgba(0, 0, 0, 0.1) 1px, > rgba(0, 0, 0, 0.5) 4px, transparent 8px); > background-image: url(/leather.png), -ms-linear-gradient(left, > transparent, rgba(0, 0, 0, 0.1) 1px, rgba(0, 0, 0, 0.5) 4px, > transparent 8px); > background-image: url(/leather.png), -o-linear-gradient(left, > transparent, rgba(0, 0, 0, 0.1) 1px, rgba(0, 0, 0, 0.5) 4px, > transparent 8px); > background-image: url(/leather.png), linear-gradient(left, > transparent, rgba(0, 0, 0, 0.1) 1px, rgba(0, 0, 0, 0.5) 4px, > transparent 8px); > border: 2px solid rgba(0, 0, 0, 0.5); > border-radius: 2px 6px 6px 2px; > width: 110px; > height: 150px; > position: relative; > text-decoration: none; > color: #999; > -webkit-transition: all 0.5s ease-in-out 0s; > -moz-transition: all 0.5s ease-in-out 0s; > -ms-transition: all 0.5s ease-in-out 0s; > -o-transition: all 0.5s ease-in-out 0s; > transition: all 0.5s ease-in-out 0s; } > > div.fakeCover > span { > color: rgba(0,0,0, 0.6); > background-color: rgba(255,255,255,.1); > border-radius: 5px; > border: 1px solid rgba(0,0,0,.05); > display: block; > font-family: arial,sans-serif; > height: auto; > margin: 8px; > margin-left: 15px; > padding: 2px; > text-align: center; > width: 81px; > max-height: 100px; > position: absolute; > > } > > div.fakeCover > span.title { > font-size: x-small; > top: 0px; > } > > div.fakeCover > span.author { > font-size: xx-small; > bottom: 0px; > } > > span.no-image { > display: none; > } > > > > On Thu, May 2, 2013 at 12:01 PM, Nicholas van Rheede van Oudtshoorn < > vanoudt(a)gmail.com> wrote: > >> Hello all! >> >> A while back (a few years, I think!) I wrote and posted to this >> mailing list a set of php scripts that provided a new books display. >> When we recently upgraded our koha instance (shifting to Plack in the >> process!), I decided to rewrite this new books display in perl. >> >> And I thought I'd put it up here in case anyone was interested in it. >> >> Perl's not my language of choice - so if there are any improvements >> to be made, please let me know. >> >> To use it, simply install the newbooksdisplay.pl in the opac cgi-bin >> directory, and add the following snippet to the OpacMain systempreferences: >> >> <h2 style="align="center">Newest books in the library</h2> <div >> id="newbooks"></div> <script type="text/javascript"> >> $("#newbooks").load("/cgi-bin/koha/newbooksdisplay.pl", function() { >> >> KOHA.Google.GetCoverFromIsbn(); >> >> }); >> >> </script> >> >> >> I've also modified the google-jackets.js to produce a nice artificial >> cover if none is available from google books (currently only if the >> correct >> HTML5 data tags are supplied, as in the newbooksdisplay) >> >> >> if (typeof KOHA == "undefined" || !KOHA) { >> var KOHA = {}; >> } >> >> /** >> * A namespace for Google related functions. >> */ >> KOHA.Google = { >> >> >> /** >> * Search all: >> >> >> >> * <div title="biblionumber" id="isbn" class="gbs-thumbnail"></div> >> * or >> * <div title="biblionumber" id="isbn" class="gbs-thumbnail-preview"></div> >> >> >> >> * and run a search with all collected isbns to Google Book Search. >> * The result is asynchronously returned by Google and catched by >> * gbsCallBack(). >> */ >> GetCoverFromIsbn: function(newWindow) { >> >> >> >> var bibkeys = []; >> $("div [id^=gbs-thumbnail]").each(function(i) { >> bibkeys.push($(this).attr("class").split(' ')[0]); // id=isbn >> }); >> bibkeys = bibkeys.join(','); >> >> >> >> var scriptElement = document.createElement("script"); >> this.openInNewWindow=newWindow; >> scriptElement.setAttribute("id", "jsonScript"); >> scriptElement.setAttribute("src", >> >> >> >> "http://books.google.com/books?bibkeys=" + escape(bibkeys) + >> "&jscmd=viewapi&callback=KOHA.Google.gbsCallBack"); >> >> >> >> scriptElement.setAttribute("type", "text/javascript"); >> >> document.documentElement.firstChild.appendChild(scriptElement); >> >> }, >> >> /** >> * Add cover pages <div >> >> >> >> * and link to preview if div id is gbs-thumbnail-preview >> */ >> gbsCallBack: function(booksInfo) { >> var target = ''; >> if (this.openInNewWindow) { >> target = 'target="_blank" '; >> >> >> >> } >> for (id in booksInfo) { >> var book = booksInfo[id]; >> $("."+book.bib_key).each(function() { >> var gbsre = /^gbs-thumbnail/; >> if ( gbsre.exec($(this).attr("id")) ) { >> >> >> >> var a = document.createElement("a"); >> a.href = book.info_url; >> if (typeof(book.thumbnail_url) != "undefined") { >> var img = document.createElement("img"); >> >> >> >> img.setAttribute("class","thumbnail"); >> img.src = book.thumbnail_url+"&zoom=1"; >> $(this).append(img); >> var re = /^gbs-thumbnail-preview/; >> >> >> >> if ( re.exec($(this).attr("id")) ) { >> $(this).append( >> '<div style="margin-bottom:5px; >> margin-top:-5px;font-size:9px">' + >> >> >> >> '<a '+target+'href="' + >> book.info_url + >> '"><img src="' + >> >> 'http://books.google.com/intl/en/googlebooks/images/gbs_preview_stick >> er1.gif' + >> >> >> >> '"></a></div>' >> ); >> } >> } else if ($(this).attr('data-title')) { >> var fakeCoverDiv = document.createElement("div"); >> >> >> >> $(fakeCoverDiv).attr("class", "fakeCover"); >> $(this).append(fakeCoverDiv); >> var auSpan = document.createElement("span"); >> $(auSpan).attr("class", "author"); >> >> >> >> $(auSpan).html($(this).attr("data-author")); >> $(fakeCoverDiv).append(auSpan); >> var tiSpan = document.createElement("span"); >> $(tiSpan).attr("class", >> "title"); >> >> >> >> $(tiSpan).html($(this).attr("data-title")); >> $(fakeCoverDiv).append(tiSpan); >> } else { >> var message = document.createElement("span"); >> >> >> >> $(message).attr("class","no-image"); >> $(message).html(NO_GOOGLE_JACKET); >> $(this).append(message); >> } >> } >> >> >> >> }); >> } >> } >> }; >> >> >> >

1 0

Re: [Koha-devel] New books display for koha
by Vimal Kumar V. 02 May '13

02 May '13

Dear *Nicholas, I appreciate your efforts to develop this nice feature for Koha. I think this feature is useful for lot of libraries. Can you document the entire process in Koha wiki? Regards, *-- Vimal Kumar V. Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: http://www.vimalkumar.info Blog: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

1 0

Koha 3.12 string freeze
by Jared Camins-Esakov 02 May '13

02 May '13

Good morning. As of this moment, Koha 3.12 is in string freeze, and any patch modifying any translatable strings will be held for Koha 3.12. Please use this opportunity to A) test, test, test, and test and B) translate the interface for Koha 3.12 once the Translation Manager gives you the go-ahead. Ruth, could you please update the PO files on translate.koha-community.orgat your earliest convenience and let koha-translate know? Regards, Jared Camins-Esakov -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins(a)cpbibliography.com (web) http://www.cpbibliography.com/

2 1

New books display for koha
by Nicholas van Rheede van Oudtshoorn 02 May '13

02 May '13

Hello all! A while back (a few years, I think!) I wrote and posted to this mailing list a set of php scripts that provided a new books display. When we recently upgraded our koha instance (shifting to Plack in the process!), I decided to rewrite this new books display in perl. And I thought I'd put it up here in case anyone was interested in it. Perl's not my language of choice - so if there are any improvements to be made, please let me know. To use it, simply install the newbooksdisplay.pl in the opac cgi-bin directory, and add the following snippet to the OpacMain systempreferences: <h2 style="align="center">Newest books in the library</h2> <div id="newbooks"></div> <script type="text/javascript"> $("#newbooks").load("/cgi-bin/koha/newbooksdisplay.pl", function() { KOHA.Google.GetCoverFromIsbn(); }); </script> I've also modified the google-jackets.js to produce a nice artificial cover if none is available from google books (currently only if the correct HTML5 data tags are supplied, as in the newbooksdisplay) if (typeof KOHA == "undefined" || !KOHA) { var KOHA = {}; } /** * A namespace for Google related functions. */ KOHA.Google = { /** * Search all: * <div title="biblionumber" id="isbn" class="gbs-thumbnail"></div> * or * <div title="biblionumber" id="isbn" class="gbs-thumbnail-preview"></div> * and run a search with all collected isbns to Google Book Search. * The result is asynchronously returned by Google and catched by * gbsCallBack(). */ GetCoverFromIsbn: function(newWindow) { var bibkeys = []; $("div [id^=gbs-thumbnail]").each(function(i) { bibkeys.push($(this).attr("class").split(' ')[0]); // id=isbn }); bibkeys = bibkeys.join(','); var scriptElement = document.createElement("script"); this.openInNewWindow=newWindow; scriptElement.setAttribute("id", "jsonScript"); scriptElement.setAttribute("src", "http://books.google.com/books?bibkeys=" + escape(bibkeys) + "&jscmd=viewapi&callback=KOHA.Google.gbsCallBack"); scriptElement.setAttribute("type", "text/javascript"); document.documentElement.firstChild.appendChild(scriptElement); }, /** * Add cover pages <div * and link to preview if div id is gbs-thumbnail-preview */ gbsCallBack: function(booksInfo) { var target = ''; if (this.openInNewWindow) { target = 'target="_blank" '; } for (id in booksInfo) { var book = booksInfo[id]; $("."+book.bib_key).each(function() { var gbsre = /^gbs-thumbnail/; if ( gbsre.exec($(this).attr("id")) ) { var a = document.createElement("a"); a.href = book.info_url; if (typeof(book.thumbnail_url) != "undefined") { var img = document.createElement("img"); img.setAttribute("class","thumbnail"); img.src = book.thumbnail_url+"&zoom=1"; $(this).append(img); var re = /^gbs-thumbnail-preview/; if ( re.exec($(this).attr("id")) ) { $(this).append( '<div style="margin-bottom:5px; margin-top:-5px;font-size:9px">' + '<a '+target+'href="' + book.info_url + '"><img src="' + 'http://books.google.com/intl/en/googlebooks/images/gbs_preview_sticker1.gif' + '"></a></div>' ); } } else if ($(this).attr('data-title')) { var fakeCoverDiv = document.createElement("div"); $(fakeCoverDiv).attr("class", "fakeCover"); $(this).append(fakeCoverDiv); var auSpan = document.createElement("span"); $(auSpan).attr("class", "author"); $(auSpan).html($(this).attr("data-author")); $(fakeCoverDiv).append(auSpan); var tiSpan = document.createElement("span"); $(tiSpan).attr("class", "title"); $(tiSpan).html($(this).attr("data-title")); $(fakeCoverDiv).append(tiSpan); } else { var message = document.createElement("span"); $(message).attr("class","no-image"); $(message).html(NO_GOOGLE_JACKET); $(this).append(message); } } }); } } };

1 2

Re: [Koha-devel] Major surprise - "automatic" upgrade
by Mason James 01 May '13

01 May '13

On 2013-05-1, at 3:07 AM, Paul wrote: > At 11:16 AM 4/30/2013 +1200, you wrote: > >> On 2013-04-30, at 9:38 AM, Paul wrote: >> >> > Hi Jared, >> > >> > At 10:41 AM 4/28/2013 -0400, you wrote: >> >> Paul, >> >> >> >> I've looked at the code in cleanup_database.pl (and search.pl), and can't see any obvious reason to "redirect to Installer." >> >> >> >> So -- what has happened? Â Can I dump the cleaned db back into production? What are the specific changes 3.8.5 to 3.8.10 that required "updating"? >> >> >> >> >> >> The redirect is because you had a newer version of the code than the database was run on. >> > >> > Thanks for your reply, but this is worrisome. I had at {server}/ a tarred 3.8.10. I had at {server}/home/paul/ an untarred 3.8.10 (for .dif purposes.) >> > >> >> Koha doesn't have any support for automatic upgrades, so I guess you must have untarred 3.8.10 at some point. >> > >> > [see above] O.K. it's not "automatic" but it did in fact run automatically without my permission. I ran: >> >> >> for the record Paul, Koha is *designed* to do this very thing >> >> it forces the web-update page, if the database is older than the codebase (as yours is) >> >> >> this is a 'feature' to stop stupid humans from corrupting their Koha databases, when attempting to run mismatched codebases and db versions > > Tnx for the reply, but I fear you misunderstood. The "automatic upgrade" I was referring to was from 3.8.5 to 3.8.10 (the whole Koha "system.") > The db update is by design and a very proper feature -- no surprise there. > > Best - Paul > > Tired old sys-admin lol, no Paul - i do not 'misunderstand' anything here hmmm, your 'automatic upgrade' was caused by... - you manually pointing your 3.8.5 Koha to a 3.8.10 codebase, (then forgetting you did that) - you manually logging-in as the Koha database user at the install/upgrade page - you manually clicking 'upgrade' did i miss anything??

4 3

Re: [Koha-devel] Major surprise - "automatic" upgrade
by Paul 30 Apr '13

30 Apr '13

At 12:08 PM 4/30/2013 +1200, Chris Cormack wrote: [big snip] >But as Jared says it will not do this without you entering your >database user and password, and explicitly clicking to tell it to >upgrade. It will give you the page, but it won't upgrade until you >tell it. > >The only automatic thing is it telling you you need to upgrade your database Thanks Chris (and Jared, Marcel and Mason.) That was my understanding and it functioned as expected: it "upgraded the *database* from 3.8.5 to 3.8.10" the first time after I ran './cleanup_database.pl --zebraqueue -v' -- at this point I could not log in on the staff page as "paul" (or any other staff-user), had to log in as "koha" and got: Web installer Step 3 We are upgrading from Koha 3.08.05.000 to 3.08.10.000, you must update your database Update report : Upgrade to 3.08.06.000 (3.8.6 release) done / .. / Upgrade to 3.08.10.000 (3.8.9 release) done Everything went OK, update done. Continue to log in to Koha The "worrisome mystery" is why the "upgrading from Koha 3.08.05.000 to 3.08.10.000" took place at all! Let me be clear, it took place without my knowledge and without my "informed" consent. I say "informed" because, when I ran './cleanup_database.pl --zebraqueue -v' I was obviously logged in as user=koha, but the '-v' verbose gave me no warning whatsoever that it had found either the tarred 3.8.10 on the root of the server or the untarred 3.8.10 at /home/paul/ -- but equally obviously user=koha has the necessary permissions to carry out the "system upgrade." It is obvious that the 'cleanup' Perl script provoked the system upgrade which took a couple of hours (no CLI messages whatsoever), as the database upgrade took just a couple of seconds. This is reproducible: I restored the 3.8.5 from backup, and can confirm the update to 3.8.10. after running './cleanup_database.pl --zebraqueue -v'. The other elements of the same script - logs, mail, import and sessions do not provoke the system upgrade. I will now restore the backup again, delete the tarred and untarred 3.8.10s and expect no upgrade :=) The mystery remains ... Thanks and regards all round, Paul --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

2 1

zebraidx segfault
by Waylon Robertson 30 Apr '13

30 Apr '13

zebraidx[11218]: segfault at 8000000d ip b65cb24e sp bfa28040 error 4 in libc-2.7.so[b6559000+155000] this occurs while im trying to do a full reindex / reset.... so the reindexing does not reach completion. help please! anyone got a clue? Linux manzoma-prod 2.6.26-2-686 #1 SMP Sun Mar 4 22:19:19 UTC 2012 i686 GNU/Linux total used free shared buffers cached Mem: 2022 1973 49 0 17 1830 just in case its relevant.

4 3

Re: [Koha-devel] Major surprise - "automatic" upgrade
by Mason James 30 Apr '13

30 Apr '13

On 2013-04-30, at 11:16 AM, Mason James wrote: On 2013-04-30, at 9:38 AM, Paul wrote: > Hi Jared, > > At 10:41 AM 4/28/2013 -0400, you wrote: >> Paul, >> >> I've looked at the code in cleanup_database.pl (and search.pl), and can't see any obvious reason to "redirect to Installer." >> >> So -- what has happened? Â Can I dump the cleaned db back into production? What are the specific changes 3.8.5 to 3.8.10 that required "updating"? >> >> >> The redirect is because you had a newer version of the code than the database was run on. > > Thanks for your reply, but this is worrisome. I had at {server}/ a tarred 3.8.10. I had at {server}/home/paul/ an untarred 3.8.10 (for .dif purposes.) > >> Koha doesn't have any support for automatic upgrades, so I guess you must have untarred 3.8.10 at some point. > > [see above] O.K. it's not "automatic" but it did in fact run automatically without my permission. I ran: for the record Paul, Koha is *designed* to do this very thing it forces the web-update page, if the database is older than the codebase (as yours is) this is a 'feature' to stop stupid humans from corrupting their Koha databases, when attempting to run mismatched codebases and db versions

3 2

Re: [Koha-devel] Major surprise - "automatic" upgrade
by Paul 30 Apr '13

30 Apr '13

Hi Jared, At 10:41 AM 4/28/2013 -0400, you wrote: >Paul, > >I've looked at the code in <http://cleanup_database.pl>cleanup_database.pl >(and <http://search.pl>search.pl), and can't see any obvious reason to >"redirect to Installer." > >So -- what has happened? Â Can I dump the cleaned db back into production? >What are the specific changes 3.8.5 to 3.8.10 that required "updating"? > > >The redirect is because you had a newer version of the code than the >database was run on. Thanks for your reply, but this is worrisome. I had at {server}/ a tarred 3.8.10. I had at {server}/home/paul/ an untarred 3.8.10 (for .dif purposes.) >Koha doesn't have any support for automatic upgrades, so I guess you must >have untarred 3.8.10 at some point. [see above] O.K. it's not "automatic" but it did in fact run automatically without my permission. I ran: './cleanup_database.pl --zebraqueue -v' and Koha *updated* from 3.8.5 to some variant of 3.8.10. Note the '-v' -- but it sat there running with nothing "verbose." >You can take a look at the release notes for the versions between 3.8.5 >and 3.8.10:Â ><http://git.koha-community.org/gitweb/?p=koha.git;a=tree;f=misc/release_note…>http://git.koha-community.org/gitweb/?p=koha.git;a=tree;f=misc/release_note… I can find no mention of 'db' or 'database' >Based on the "Update report" you shared, it doesn't look like there were >any actual database changes in between versions 3.8.5 and 3.8.10, but I >couldn't say that with certainty without checking (you can take a look at >the release notes linked above, and by reviewing the >installer/data/mysql/<http://updatedatabase.pl>updatedatabase.pl file on >the 3.8.10 installation). I have looked at it, but question why it would be triggered? >The update is trigged whenever you have an older version of the database >than the code, By what? And "the code" in what? The relevant code in cleanup_database.pl is "$sth2 = $dbh->prepare("DELETE FROM zebraqueue WHERE id=?");" a simple MySQL directive. Why does 'cleanup_database.pl' even look for '<http://updatedatabase.pl>updatedatabase<http://updatedatabase.pl>.pl' and|or "other/more recent" versions of "the code"? The bottom line is "why does a simple .pl using TRUNCATE lead to an upgrade"? >Most likely downgrading to 3.8.5 would not cause any problems at all, "Downgrading" is new to me. Do you mean "restore system from backup"? Best - Paul >even if there were database changes, but it's always a good idea to check. > >Regards, >Jared > >-- >Jared Camins-Esakov >Bibliographer, C & P Bibliography Services, LLC >(phone) +1 (917) 727-3445 >(e-mail) <mailto:jcamins@cpbibliography.com>jcamins(a)cpbibliography.com >(web) <http://www.cpbibliography.com/>http://www.cpbibliography.com/

2 1