From mjr at phonecoop.coop Mon Jul 1 12:20:32 2013 From: mjr at phonecoop.coop (MJ Ray) Date: Mon, 01 Jul 2013 10:20:32 +0000 Subject: [Koha-devel] Old bugs to check Message-ID: Would you check some of these rather old bugs to suggest what to do, please? Maybe some can be RESOLVED FIXED by now or need a question. Please leave your reply on the bug web page - I might not see replies to this mail. Ideally, tell irc.oftc.net #koha know that you're looking at a bug. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6456 Display of barcode in search result in staff client http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6122 Catalogue reports exclude biblio without item http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6624 Allow Koha to use the new read API from OpenLibrary http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6301 super librarians can't export bib records from all libraries if indybranches on http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6421 ability to have different opac styles for different libraries http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3343 duplicate subfields in authority http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5535 users tags not appearing until approved http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5404 C4::Koha::subfield_is_koha_internal_p no longer serves a purpose http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5594 default sort order for items on bib records http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2389 overdue_notices.pl needs a test mode http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5784 link to acq from budgets & funds http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5273 Publication Details for serial subscriptions not showing when in item record edit http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5985 Incorrect date in budgets and failed to edit funds children http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5986 Inconsistent handling of patron deletion permission http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3162 Authority subfileds definitions and Show/Show Collapsed/Hide option http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5920 remove html from downloaded reports http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6605 Store Patron Reading History separate from issues/old_issues http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5576 Access Koha via SSL http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6223 Patron categories should have a default set of permissions -- Email robot driven by MJ Ray (slef), member of www.software.coop, http://koha-community.org supporter, web and library systems developer. Available for hire (including development) at http://www.software.coop/ From samuel.desseaux at ecp.fr Mon Jul 1 14:19:25 2013 From: samuel.desseaux at ecp.fr (Samuel Desseaux) Date: Mon, 01 Jul 2013 14:19:25 +0200 Subject: [Koha-devel] UNIMARC_sync_date_created_with_marc_biblio.pl Message-ID: <51D173CD.8040704@ecp.fr> Hi, I've noticed a problem with my biblio records. Biblio.datecreated and biblio.timestamp are well fullfilled in the database but are not displayed in the biblio record. I've executed this but with no results (in koha / misc / maintenance /) perl *UNIMARC_sync_date_created_with_marc_biblio.pl. Has someone an idea? Best regards, Samuel * -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.tajoli at cineca.it Tue Jul 2 10:07:50 2013 From: z.tajoli at cineca.it (Zeno Tajoli) Date: Tue, 02 Jul 2013 10:07:50 +0200 Subject: [Koha-devel] SQL files and transaltion Message-ID: <51D28A56.8030009@cineca.it> Hi to all, I now that there bugs in develop about a new method to translate MySQL setup and MARC21/Unimarc sql definitions. But, for paid user, i need to create a full italian MySQl setup for 3.12. And I also need to create a full italian MARC21 sql configuration. So, in you opinion what is the best option for Koha comunity ? My plan is: a)I prepare and send patches to translate the present MySQL setup in master and 3.12 but not for MARC21 translation. I think to use two different bug number, one for master update and an other for 3.12 update. Is it OK ? b)About MARC21 translation, I wait and I help in testing the code. I think that the new translation workflow for MARC21 will be present in 3.14. But I can change my plan. Bye Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli at cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate From M.de.Rooy at rijksmuseum.nl Tue Jul 2 11:08:36 2013 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Tue, 2 Jul 2013 09:08:36 +0000 Subject: [Koha-devel] SQL files and transaltion In-Reply-To: <51D28A56.8030009@cineca.it> References: <51D28A56.8030009@cineca.it> Message-ID: <809BE39CD64BFD4EB9036172EBCCFA310FFCF6DE@S-MAIL-1B.rijksmuseum.intra> Hi Zeno and all others, > But, for paid user, i need to create a full italian MySQl setup for 3.12. > And I also need to create a full italian MARC21 sql configuration. > So, in you opinion what is the best option for Koha comunity ? > My plan is: > a)I prepare and send patches to translate the present MySQL setup in > master and 3.12 but not for MARC21 translation. > I think to use two different bug number, one for master update and an > other for 3.12 update. Is it OK ? The proposed i18n function in bug 10509 is for master (3.14), and is still in a Needs Signoff state. So we should see if people are willing to test and sign off. If so, it will not be that hard to move all language folders including Italian to the new style in some weeks after that. (With great benefits: less redundancy and ready for inclusion in a Pootle workflow.) If you only focus on translating 3.12 now (and not on master while in transition), we could pickup your translations from your 3.12 translation and insert them in a followup for the Italian language folder. If you also send patches now for 3.14, we will have competing changes and a duplication of effort. If you create a report with patches for 3.12, it could be helpful if you include [3.12 ONLY] or something similar already in the title of the report? Would this work for you? > b)About MARC21 translation, I wait and I help in testing the code. I > think that the new translation workflow for MARC21 will be present in 3.14. Actually same here: Please translate this in 3.12 and have contact again to pickup your changes to incorporate them in a 3.14 followup for it-IT. Hope I was clear enough.. Regards, Marcel From z.tajoli at cineca.it Tue Jul 2 11:17:10 2013 From: z.tajoli at cineca.it (Zeno Tajoli) Date: Tue, 02 Jul 2013 11:17:10 +0200 Subject: [Koha-devel] SQL files and transaltion In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA310FFCF6DE@S-MAIL-1B.rijksmuseum.intra> References: <51D28A56.8030009@cineca.it> <809BE39CD64BFD4EB9036172EBCCFA310FFCF6DE@S-MAIL-1B.rijksmuseum.intra> Message-ID: <51D29A96.7040802@cineca.it> Hi Marcel and all, Il 02/07/2013 11:08, Marcel de Rooy ha scritto: > > The proposed i18n function in bug 10509 is for master (3.14), and is still in a Needs Signoff state. >So we should see if people are willing to test and sign off. As soon as possible I will test 10509 on master. > If you only focus on translating 3.12 now (and not on master while in transition), we could pickup your translations from your 3.12 translation > and insert them in a followup for the Italian language folder. Ok, I will prepare the patches only for 3.12 with a clear mark in the name [3.12 ONLY]. For MySQL setup and for MARC21 translation. Bye Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli at cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate From M.de.Rooy at rijksmuseum.nl Tue Jul 2 14:51:28 2013 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Tue, 2 Jul 2013 12:51:28 +0000 Subject: [Koha-devel] QA: Passed QA queue Message-ID: <809BE39CD64BFD4EB9036172EBCCFA310FFD07E9@S-MAIL-1B.rijksmuseum.intra> Hi Galen, Saw this note from Paul on bug 7167. Probably, your answer may be of interest to more people. We can all see 40 patches in that queue, but we do not know your strategy in handling them (apart from the fact that it is different from that of former RMs). But I could have missed something :) Thanks! Marcel ________________________________________ Van: bugzilla-daemon at bugs.koha-community.org [bugzilla-daemon at bugs.koha-community.org] Verzonden: dinsdag 2 juli 2013 11:48 Aan: Marcel de Rooy Onderwerp: [Bug 7167] updatedatabase improvements http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167 --- Comment #244 from Paul Poulain --- Galen, did you forget this patch ? Any other comment ? -- You are receiving this mail because: You are on the CC list for the bug. From gmc at esilibrary.com Tue Jul 2 15:12:47 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Tue, 2 Jul 2013 09:12:47 -0400 Subject: [Koha-devel] QA: Passed QA queue In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA310FFD07E9@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA310FFD07E9@S-MAIL-1B.rijksmuseum.intra> Message-ID: Hi, On Tue, Jul 2, 2013 at 8:51 AM, Marcel de Rooy wrote: > Saw this note from Paul on bug 7167. > Probably, your answer may be of interest to more people. We can all see 40 > patches in that queue, but we do not know your strategy in handling them > (apart from the fact that it is different from that of former RMs). > But I could have missed something :) > It's quite simple -- I do not consider my job as being one of automatically pushing any patch that reaches the passed-QA status. I will take the time I need to review and test nearly [1] every patch, and in particular any like bug 7167 that proposes a significant change. Bigger patches take more time, especially those that have architectural implications. The revamp of the schema update mechanism proposed in bug 7167 has been under discussion for a long time, and is not IMO one that should be automatically pushed, especially given that it's been quite a while since patches have been rejected simply because of merge conflicts with updatedatabase.pl. Further, I *do* view my job to include responsibility for final review of architectural changes to Koha. A patch that adds a necessary improvement to Koha but whose implementation is lacking or would present long-term maintenance issues is going to receive enhanced scrutiny from me. There are other major architectural patches, most recently and most notably DBIx::Class support, that I have been focusing my effort on; bug 7167 in my estimation is not at the same level of priority. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmc at esilibrary.com Tue Jul 2 15:17:55 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Tue, 2 Jul 2013 09:17:55 -0400 Subject: [Koha-devel] QA: Passed QA queue In-Reply-To: References: <809BE39CD64BFD4EB9036172EBCCFA310FFD07E9@S-MAIL-1B.rijksmuseum.intra> Message-ID: Hi, On Tue, Jul 2, 2013 at 9:12 AM, Galen Charlton wrote: > > It's quite simple -- I do not consider my job as being one of > automatically pushing any patch that reaches the passed-QA status. I will > take the time I need to review and test nearly [1] every patch... > As somebody pointed out, I left the footnote off: [1] Some string patches I just eyeball. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Tue Jul 2 21:30:45 2013 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Wed, 3 Jul 2013 07:30:45 +1200 Subject: [Koha-devel] QA: Passed QA queue In-Reply-To: References: <809BE39CD64BFD4EB9036172EBCCFA310FFD07E9@S-MAIL-1B.rijksmuseum.intra> Message-ID: <20130702193045.GP4598@rorohiko.wgtn.cat-it.co.nz> * Galen Charlton (gmc at esilibrary.com) wrote: > Hi, > On Tue, Jul 2, 2013 at 8:51 AM, Marcel de Rooy > wrote: > > Saw this note from Paul on bug 7167. > Probably, your answer may be of interest to more people. We can all see > 40 patches in that queue, but we do not know your strategy in handling > them (apart from the fact that it is different from that of former RMs). > But I could have missed something :) > > It's quite simple -- I do not consider my job as being one of > automatically pushing any patch that reaches the passed-QA status. I will > take the time I need to review and test nearly [1] every patch, and in > particular any like bug 7167 that proposes a significant change. Which isn't really that different from the previous RM, or speaking for myself, when I did RM or RMaint. I, for one, welcome the scrutiny. We are all human (at least I'm pretty sure we all are) and we make mistakes. Galen has caught at least one thing I missed when QAing. Stability FTW :) Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From chris at bigballofwax.co.nz Tue Jul 2 23:35:18 2013 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Wed, 3 Jul 2013 09:35:18 +1200 Subject: [Koha-devel] Linux server with some spare cpu cycles? Message-ID: Hi All As you know we run jenkins for our integration testing, what you might not know is a lot of the jobs used to run on a my server at home as a node. This server is dead, and the disks are on my desk, so this is a call for anyone who has a server that they wouldnt mind letting jenkins use as a node. Basically it just needs ssh access, and java on the machine, it installs pretty much everything else. Any offers? Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmc at esilibrary.com Wed Jul 3 00:06:21 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Tue, 2 Jul 2013 18:06:21 -0400 Subject: [Koha-devel] Linux server with some spare cpu cycles? In-Reply-To: References: Message-ID: Hi, On Tue, Jul 2, 2013 at 5:35 PM, Chris Cormack wrote: > This server is dead, and the disks are on my desk, so this is a call for > anyone who has a server that they wouldnt mind letting jenkins use as a > node. > Basically it just needs ssh access, and java on the machine, it installs > pretty much everything else. > > Any offers? > I've spun up a Linode in Tokyo for this purpose, but I asked Chris, and it turns out that the more nodes there are, the merrier. Consequently, others should feel free to offer their servers if they feel so inspired. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From Katrin.Fischer.83 at web.de Wed Jul 3 00:20:53 2013 From: Katrin.Fischer.83 at web.de (Katrin Fischer) Date: Wed, 03 Jul 2013 00:20:53 +0200 Subject: [Koha-devel] QA: Passed QA queue In-Reply-To: <20130702193045.GP4598@rorohiko.wgtn.cat-it.co.nz> References: <809BE39CD64BFD4EB9036172EBCCFA310FFD07E9@S-MAIL-1B.rijksmuseum.intra> <20130702193045.GP4598@rorohiko.wgtn.cat-it.co.nz> Message-ID: <51D35245.8040505@web.de> Am 02.07.2013 21:30, schrieb Chris Cormack: > * Galen Charlton (gmc at esilibrary.com) wrote: >> Hi, >> On Tue, Jul 2, 2013 at 8:51 AM, Marcel de Rooy >> wrote: >> >> Saw this note from Paul on bug 7167. >> Probably, your answer may be of interest to more people. We can all see >> 40 patches in that queue, but we do not know your strategy in handling >> them (apart from the fact that it is different from that of former RMs). >> But I could have missed something :) >> >> It's quite simple -- I do not consider my job as being one of >> automatically pushing any patch that reaches the passed-QA status. I will >> take the time I need to review and test nearly [1] every patch, and in >> particular any like bug 7167 that proposes a significant change. > > Which isn't really that different from the previous RM, or speaking > for myself, when I did RM or RMaint. I, for one, welcome the > scrutiny. We are all human (at least I'm pretty sure we all are) and > we make mistakes. Galen has caught at least one thing I missed when > QAing. > > Stability FTW :) > > Chris > And he has also found something I missed - scrutiny and stability FTW :) I think Galen is doing a wonderful job as RM and I wouldn't want him to do it any different. Katrin From gmc at esilibrary.com Wed Jul 3 04:58:47 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Tue, 2 Jul 2013 22:58:47 -0400 Subject: [Koha-devel] 3.14 RM update #1 posted Message-ID: Hi, I've posted my first formal update to the Koha community at: http://koha-community.org/koha-3-14-release-managers-update-1/ I won't copy and paste the whole thing here, but if there is anything that might make future updates more useful, please let me know. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Wed Jul 3 09:10:26 2013 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Wed, 3 Jul 2013 07:10:26 +0000 Subject: [Koha-devel] QA: Passed QA queue In-Reply-To: <51D35245.8040505@web.de> References: <809BE39CD64BFD4EB9036172EBCCFA310FFD07E9@S-MAIL-1B.rijksmuseum.intra> <20130702193045.GP4598@rorohiko.wgtn.cat-it.co.nz>, <51D35245.8040505@web.de> Message-ID: <809BE39CD64BFD4EB9036172EBCCFA310FFD1D19@S-MAIL-1B.rijksmuseum.intra> Probably, we can close this thread now. >>> It's quite simple -- I do not consider my job as being one of >>> automatically pushing any patch that reaches the passed-QA status. I will >>> take the time I need to review and test nearly [1] every patch, and in >>> particular any like bug 7167 that proposes a significant change. No RM should push automatically. Please take your time. I agree with your last comment on 7167 btw. >> Which isn't really that different from the previous RM, or speaking >> for myself, when I did RM or RMaint. I, for one, welcome the >> scrutiny. We are all human (at least I'm pretty sure we all are) and >> we make mistakes. Galen has caught at least one thing I missed when >> QAing. I welcome the scrutiny as well and hope to have acted accordingly during my QA work so far too. Note that this was certainly not the point of this thread. > I think Galen is doing a wonderful job as RM and I wouldn't want him to > do it any different. The intention of my message was more to ask what was happening behind the scenes.. (There appears to be no hidden branch where Galen does special git trics, or he just does not want to tell about it :) So, Galen, please go on: if Quality>Quantity then Stability++; Regards, Marcel From M.de.Rooy at rijksmuseum.nl Wed Jul 3 13:59:46 2013 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Wed, 3 Jul 2013 11:59:46 +0000 Subject: [Koha-devel] Bugzilla: Reply on comment Message-ID: <809BE39CD64BFD4EB9036172EBCCFA310FFD2098@S-MAIL-1B.rijksmuseum.intra> Hi all, I recently (last update?) and regularly have trouble with Reply on Bugzilla. It does sometimes no longer paste the comment in the text box. Anyone else having this too? Or found a way to resolve it? Thanks, Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Wed Jul 3 15:02:30 2013 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 03 Jul 2013 15:02:30 +0200 Subject: [Koha-devel] Bugzilla: Reply on comment In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA310FFD2098@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA310FFD2098@S-MAIL-1B.rijksmuseum.intra> Message-ID: <51D420E6.4000401@biblibre.com> Le 03/07/2013 13:59, Marcel de Rooy a ?crit : > Hi all, > I recently (last update?) and regularly have trouble with Reply on Bugzilla. > It does sometimes no longer paste the comment in the text box. > Anyone else having this too? Or found a way to resolve it? Yep, I sometimes have this problem as well. But I haven't found how to fix it. I'm using Firefox with some modules like lazarus, stylish, greasemonkey, firebug that could have an impact. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper From M.de.Rooy at rijksmuseum.nl Wed Jul 3 15:53:48 2013 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Wed, 3 Jul 2013 13:53:48 +0000 Subject: [Koha-devel] Test suite in t/db_dependent/lib/KohaTest Message-ID: <809BE39CD64BFD4EB9036172EBCCFA310FFD2104@S-MAIL-1B.rijksmuseum.intra> Hi, My question about the files in the mentioned folder is: Is anyone using these test units at all? Could we delete them? Note that Jenkins appears not to run t/db_dependent/database_dependent.pl but only the *.t files. The script database_dependent.pl only refers to lib/KohaTest.pm and all unit tests in lib/KohaTest. commit 80568463eac45ede97268c02ee7d59028cb3ff9b introduced t/database_dependent.pl (2008) commit eff21765f9784e09905042dd7080cbef099306d9 moved it to t/db_dependent/ Note also that it needs two additional cpan modules: Test::Class and Test::Class::Load Currently, we are often updating files in this directory. We are finding them with grep etc. and we update them. But if no one is using them, we could better remove them and have less maintenance issues. Before opening a report with a "large delete" patch, just asking around here. Please respond if you know that they are in use! Thanks, Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at biblibre.com Wed Jul 3 16:19:41 2013 From: jonathan.druart at biblibre.com (Jonathan Druart) Date: Wed, 3 Jul 2013 16:19:41 +0200 Subject: [Koha-devel] Test suite in t/db_dependent/lib/KohaTest In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA310FFD2104@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA310FFD2104@S-MAIL-1B.rijksmuseum.intra> Message-ID: Hi Marcel, This question was in my todo list, thanks to ask :) I have the same impression, these UT files are never used, but it is possible I missed something. Regards, Jonathan 2013/7/3 Marcel de Rooy : > Hi, > > > > My question about the files in the mentioned folder is: Is anyone using > these test units at all? Could we delete them? > > > > Note that Jenkins appears not to run t/db_dependent/database_dependent.pl > but only the *.t files. > > The script database_dependent.pl only refers to lib/KohaTest.pm and all unit > tests in lib/KohaTest. > > > > commit 80568463eac45ede97268c02ee7d59028cb3ff9b introduced > t/database_dependent.pl (2008) > commit eff21765f9784e09905042dd7080cbef099306d9 moved it to t/db_dependent/ > > > > Note also that it needs two additional cpan modules: Test::Class and > Test::Class::Load > > > > Currently, we are often updating files in this directory. We are finding > them with grep etc. and we update them. But if no one is using them, we > could better remove them and have less maintenance issues. > > > > Before opening a report with a "large delete" patch, just asking around > here. Please respond if you know that they are in use! > > > > Thanks, > > Marcel > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ From oleonard at myacpl.org Wed Jul 3 20:23:59 2013 From: oleonard at myacpl.org (Owen Leonard) Date: Wed, 3 Jul 2013 14:23:59 -0400 Subject: [Koha-devel] Testers wanted: New OPAC theme based on Bootstrap Message-ID: As many of you know, I have been working on a new theme for the OPAC based on the Bootstrap framework. The design is based primarily on CCSR. My goal is to have a theme that feels more modern, is fully-responsive, and which is maintains all the functionality of the current prog theme. I have a branch up on Gitorious, and I would love to get some feedback: http://gitorious.org/koha-dev/koha-dev The branch is called "bootstrap-opac." Select the "bootstrap" theme once you have it checked out. The theme has come a long way since I last posted screenshots, with lots of work on the responsive aspect of it. Not everything is perfect, but I think it's in a good state to get some other eyes on it. Thanks, Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From liz at catalyst.net.nz Wed Jul 3 23:22:39 2013 From: liz at catalyst.net.nz (Liz Rea) Date: Thu, 04 Jul 2013 09:22:39 +1200 Subject: [Koha-devel] Bugzilla: Reply on comment In-Reply-To: <51D420E6.4000401@biblibre.com> References: <809BE39CD64BFD4EB9036172EBCCFA310FFD2098@S-MAIL-1B.rijksmuseum.intra> <51D420E6.4000401@biblibre.com> Message-ID: <51D4961F.7030006@catalyst.net.nz> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've noticed on some websites (including Koha), pasting in without putting something in manually like a space doesn't seem to activate the submit buttons. You might try pasting, then hitting the space bar or something and see if that helps. Cheers, Liz On 04/07/13 01:02, Paul Poulain wrote: > Le 03/07/2013 13:59, Marcel de Rooy a ?crit : >> Hi all, >> I recently (last update?) and regularly have trouble with Reply on Bugzilla. >> It does sometimes no longer paste the comment in the text box. >> Anyone else having this too? Or found a way to resolve it? > > Yep, I sometimes have this problem as well. But I haven't found how to > fix it. > I'm using Firefox with some modules like lazarus, stylish, greasemonkey, > firebug that could have an impact. > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJR1JYfAAoJELbCpJ03Jji3cSAH/AgT+aVV4ebENJEdXVRkspJ2 hSYOEzrgBO64MXFgiJOMaglEXoZOctc3a/BCg/KdlYYxW+nC+6FoHn1JJd0LJlsF 2Vru9tS0OsXhbNG9WUyCQ4Il/e0ILbQHH3+QT6FfC8Sumlx/fVdBe3IBSnxVXh1p illTW5HUS2q7iypxagcJ2M2YobcRAfrvAnSKWrpW5Y7F8DfT9v1f15wvpdVIVlMr soglLxlteVeGupRykuYiKBDOKkzqTAax0Q1R/XghKrQMAJplgyStxIO7oFRypZSb tdApZqA9Bo2XTRjIcxxtPgG2puz74pDv8/0Q7PmtkgmraPfPriN9KZaXoHNxvn0= =SRFt -----END PGP SIGNATURE----- From chris at bigballofwax.co.nz Wed Jul 3 23:22:55 2013 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Thu, 4 Jul 2013 09:22:55 +1200 Subject: [Koha-devel] Test suite in t/db_dependent/lib/KohaTest In-Reply-To: References: <809BE39CD64BFD4EB9036172EBCCFA310FFD2104@S-MAIL-1B.rijksmuseum.intra> Message-ID: On 4 July 2013 02:19, Jonathan Druart wrote: > > Hi Marcel, > > This question was in my todo list, thanks to ask :) > I have the same impression, these UT files are never used, but it is > possible I missed something. > > Regards, > Jonathan > +1 to removing Chris From gmc at esilibrary.com Thu Jul 4 03:05:29 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Wed, 3 Jul 2013 21:05:29 -0400 Subject: [Koha-devel] Test suite in t/db_dependent/lib/KohaTest In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA310FFD2104@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA310FFD2104@S-MAIL-1B.rijksmuseum.intra> Message-ID: Hi, On Wed, Jul 3, 2013 at 9:53 AM, Marcel de Rooy wrote: > Currently, we are often updating files in this directory. We are finding > them with grep etc. and we update them. But if no one is using them, we > could better remove them and have less maintenance issues. > > Before opening a report with a "large delete" patch, just asking around > here. Please respond if you know that they are in use! > To my knowledge, this set of test scripts is not being actively used. Consequently, I have no objection to a patch that removes them, but it would be a niceness to look over the individual tests and see which ones can be easily ported to the current DB-dependent test framework. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Thu Jul 4 10:24:56 2013 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 4 Jul 2013 08:24:56 +0000 Subject: [Koha-devel] Test suite in t/db_dependent/lib/KohaTest In-Reply-To: References: <809BE39CD64BFD4EB9036172EBCCFA310FFD2104@S-MAIL-1B.rijksmuseum.intra> Message-ID: <809BE39CD64BFD4EB9036172EBCCFA310FFD2633@S-MAIL-1B.rijksmuseum.intra> Thanks for your responses, Chris, Galen and Jonathan. I opened up two reports: 10539 now removes unused files from the codebase. I will use 10540 to report unit tests to inject back into the currently used test suite. Anyone is invited to join in that effort. (This will take some time, I guess.) Marcel Van: Galen Charlton [mailto:gmc at esilibrary.com] Verzonden: donderdag 4 juli 2013 3:05 Aan: Marcel de Rooy CC: koha-devel at lists.koha-community.org Devel Onderwerp: Re: [Koha-devel] Test suite in t/db_dependent/lib/KohaTest Hi, On Wed, Jul 3, 2013 at 9:53 AM, Marcel de Rooy > wrote: Currently, we are often updating files in this directory. We are finding them with grep etc. and we update them. But if no one is using them, we could better remove them and have less maintenance issues. Before opening a report with a "large delete" patch, just asking around here. Please respond if you know that they are in use! To my knowledge, this set of test scripts is not being actively used. Consequently, I have no objection to a patch that removes them, but it would be a niceness to look over the individual tests and see which ones can be easily ported to the current DB-dependent test framework. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From john.fink at gmail.com Sat Jul 6 03:25:11 2013 From: john.fink at gmail.com (John Fink) Date: Fri, 5 Jul 2013 21:25:11 -0400 Subject: [Koha-devel] Fwd: Koha Docker image In-Reply-To: References: Message-ID: Hi Koha-devel folks, Sent this to the Koha general list, but was advised that it's probably more of interested to devel. Also, I omitted the index page -- has instructions amongst other stuff. https://index.docker.io/u/jbfink/koha/ jf ---------- Forwarded message ---------- From: John Fink Date: Fri, Jul 5, 2013 at 4:29 PM Subject: Koha Docker image To: koha at lists.katipo.co.nz Hey folks, Spent some time today whipping up a Docker (http://docker.io) image for Koha for a talk I'm going to be giving about Docker later this year. If anybody on-list would like to see how it stands up, you can pull it from Docker's index with docker pull jbfink/koha . Note that I am by no means a Koha expert and this is my first time messing with Koha since... oh... 2002 or so, so there may be things with my Koha install which are broken or boneheaded in some way. jf -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at bigballofwax.co.nz Sat Jul 6 08:39:58 2013 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Sat, 6 Jul 2013 18:39:58 +1200 Subject: [Koha-devel] Fwd: Koha Docker image In-Reply-To: References: Message-ID: On 6 July 2013 13:25, John Fink wrote: > Hi Koha-devel folks, > > Sent this to the Koha general list, but was advised that it's probably more > of interested to devel. Also, I omitted the index page -- has instructions > amongst other stuff. https://index.docker.io/u/jbfink/koha/ > Hi John It took a really long time to pull over here in nz (about an hour) but it all appears to be working fine Chris From z.tajoli at cineca.it Sat Jul 6 08:43:30 2013 From: z.tajoli at cineca.it (Zeno Tajoli) Date: Sat, 6 Jul 2013 08:43:30 +0200 (CEST) Subject: [Koha-devel] libgd-gd2-perl and ibgd2-noxpm-dev in wheezy Message-ID: <1607039763.6293855.1373093010798.JavaMail.root@cineca.it> Hi to all, I'm tring a git install of 3.12.x on Debian wheezy amd64. I find that the libraries libgd-gd2-perl and libgd2-noxpm-dev don't work well together. If I want to install libgd2-noxpm-dev, I need to remove libgd-gd2-perl. In fact I don't know if we want GD2 with or without XPM (X pixmap) and fontconfig support. Bye Zeno Tajoli From john.fink at gmail.com Sun Jul 7 05:35:01 2013 From: john.fink at gmail.com (John Fink) Date: Sat, 6 Jul 2013 23:35:01 -0400 Subject: [Koha-devel] Fwd: Koha Docker image In-Reply-To: References: Message-ID: Chris, Thanks so much for trying it out - I appreciate it. jf On Jul 6, 2013 2:40 AM, "Chris Cormack" wrote: > On 6 July 2013 13:25, John Fink wrote: > > Hi Koha-devel folks, > > > > Sent this to the Koha general list, but was advised that it's probably > more > > of interested to devel. Also, I omitted the index page -- has > instructions > > amongst other stuff. https://index.docker.io/u/jbfink/koha/ > > > Hi John > > It took a really long time to pull over here in nz (about an hour) but > it all appears to be working fine > > Chris > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjr at phonecoop.coop Mon Jul 8 14:16:13 2013 From: mjr at phonecoop.coop (MJ Ray) Date: Mon, 08 Jul 2013 13:16:13 +0100 Subject: [Koha-devel] libgd-gd2-perl and ibgd2-noxpm-dev in wheezy In-Reply-To: <1607039763.6293855.1373093010798.JavaMail.root@cineca.it> References: <1607039763.6293855.1373093010798.JavaMail.root@cineca.it> Message-ID: <51DAAD8D.5050904@phonecoop.coop> On 06/07/13 07:43, Zeno Tajoli wrote: > If I want to install libgd2-noxpm-dev, I need to remove libgd-gd2-perl. > > In fact I don't know if we want GD2 with or without XPM (X pixmap) > and fontconfig support. I'm pretty sure it's unlikely that we use XPM support anywhere, so you can have it either way: however, if you remove libgd-gd2-perl, you will need to rebuild it from source if you want to use any Koha features that use it (not sure what they are off the top of my head). I'd include fontconfig support just because it's nice, but I doubt we use it through GD either. Hope that informs, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/ From robin at catalyst.net.nz Mon Jul 8 14:46:23 2013 From: robin at catalyst.net.nz (Robin Sheat) Date: Mon, 08 Jul 2013 13:46:23 +0100 Subject: [Koha-devel] libgd-gd2-perl and ibgd2-noxpm-dev in wheezy In-Reply-To: <1607039763.6293855.1373093010798.JavaMail.root@cineca.it> References: <1607039763.6293855.1373093010798.JavaMail.root@cineca.it> Message-ID: <51DAB49F.5050408@catalyst.net.nz> Op 06/07/13 07:43, Zeno Tajoli schreef: > I'm tring a git install of 3.12.x on Debian wheezy amd64. > I find that the libraries libgd-gd2-perl and libgd2-noxpm-dev > don't work well together. You could just install the koha-perldeps package to get them all for you. >From Koha's point of view, the dependencies specify: libgd-gd2-noxpm-perl | libgd-gd2-perl so either is fine. -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D From ernesarias at hotmail.com Tue Jul 9 17:49:05 2013 From: ernesarias at hotmail.com (Ernesto Arias) Date: Tue, 9 Jul 2013 15:49:05 +0000 Subject: [Koha-devel] koha reservation expires automatically In-Reply-To: References: , , , , <5.2.1.1.2.20130531151932.01e75138@localhost>, <5.2.1.1.2.20130601121012.10d698f0@localhost>, , <51AC62D1.1000208@calyx.net.au>, , Message-ID: HelloTank?s a lot for the patch Could you give me same guidanse how to aply it.Regards,Ernesto > Date: Wed, 19 Jun 2013 08:55:40 +0200 > Subject: Re: [Koha-devel] koha reservation expires automatically > From: jonathan.druart at biblibre.com > To: ernesarias at hotmail.com > CC: koha-devel at lists.koha-community.org > > Hello Ernesto, > > The bug 8367 introduces this feature. It needs a signoff :) > > Regards, > Jonathan > > 2013/6/19 Ernesto Arias : > > Hi, I found this option and this waht I need. > > Now what I want to know if it is possible to differentiate the time expire > > depending on which library is. > > For example: For one library 7 days and for another 10 days. > > ________________________________ > > Date: Mon, 3 Jun 2013 19:33:05 +1000 > > From: bob at calyx.net.au > > To: koha-devel at lists.koha-community.org > > Subject: Re: [Koha-devel] koha reservation expires automatically > > > > > > On 03/06/13 18:06, Ernesto Arias wrote: > > > > Hi, I?m using the version 3.6.7 of Koha in the library of mi university in > > Argentina. > > I don?t know how to do that reservation expires automatically in a > > determinate period of time if the user didnt pick the book up. > > It?s there any posibility to do that? > > Sory for mi poor English and mi ignorance. > > Regards > > Ernesto > > > > Hi Ernesto, > > There are system preferences that may provide the functionality you are > > seeking. They in the Reserves Policies area: Administration/System > > Preferences/Circulation. The key one is ReservesMaxPickUpDelay and there > > are others that are related to it. > > > > I hope this helps. > > Bob Birchall > > Calyx > > > > _______________________________________________ Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website > > : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : > > http://bugs.koha-community.org/ > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.tajoli at cineca.it Tue Jul 9 19:48:22 2013 From: z.tajoli at cineca.it (Zeno Tajoli) Date: Tue, 09 Jul 2013 19:48:22 +0200 Subject: [Koha-devel] koha reservation expires automatically In-Reply-To: References: , , , , <5.2.1.1.2.20130531151932.01e75138@localhost>, <5.2.1.1.2.20130601121012.10d698f0@localhost>, , <51AC62D1.1000208@calyx.net.au>, , Message-ID: <51DC4CE6.5050605@cineca.it> Hi Ernesto and all, Il 09/07/2013 17:49, Ernesto Arias ha scritto: > Hello > Tank?s a lot for the patch > Could you give me same guidanse how to aply it. A wiki page about sign off is here: http://wiki.koha-community.org/wiki/Sign_off_on_patches I suggest you to read it with your IT guru, and check also pages that are here: http://wiki.koha-community.org/wiki/Category:Git Could be difficult to learn everything connect with the topic but at the end: -- You will know much better Koha -- You will able now and in the future to use new feature much more quickly. -- You will help Koha to became better and with more features. There is also a much more easly way to sign-off pathes, with sandboxes: http://wiki.koha-community.org/wiki/Sandboxes But this patch could not sign-off with sandboxes, "It's not possible currently to properly test zebra/dbupdate/installer patches with those sandboxes" And this patch has an dbupdate. Bye Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli at cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate From ernesarias at hotmail.com Wed Jul 10 05:53:46 2013 From: ernesarias at hotmail.com (Ernesto Arias) Date: Wed, 10 Jul 2013 03:53:46 +0000 Subject: [Koha-devel] koha reservation expires automatically In-Reply-To: <51DC4CE6.5050605@cineca.it> References: , , , , , , , , <5.2.1.1.2.20130531151932.01e75138@localhost>, , <5.2.1.1.2.20130601121012.10d698f0@localhost>, , , , <51AC62D1.1000208@calyx.net.au>, , , , , , <51DC4CE6.5050605@cineca.it> Message-ID: Hi all!,I tried to aply the patch by copying manually the lines that are different in all the files.The problem is that there are a lot of differens in my files (koha version 3.6.7) and the files that are included in the bug 8367.Can I solved this problem?? or I need to update my koha?sory for mi ignorance I?m very new.RegardsErnesto > Date: Tue, 9 Jul 2013 19:48:22 +0200 > From: z.tajoli at cineca.it > To: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] koha reservation expires automatically > > Hi Ernesto and all, > > Il 09/07/2013 17:49, Ernesto Arias ha scritto: > > Hello > > Tank?s a lot for the patch > > Could you give me same guidanse how to aply it. > > A wiki page about sign off is here: > http://wiki.koha-community.org/wiki/Sign_off_on_patches > > I suggest you to read it with your IT guru, and check also pages that > are here: http://wiki.koha-community.org/wiki/Category:Git > > Could be difficult to learn everything connect with the topic but at the > end: > -- You will know much better Koha > -- You will able now and in the future to use new feature much more quickly. > -- You will help Koha to became better and with more features. > > There is also a much more easly way to sign-off pathes, with sandboxes: > http://wiki.koha-community.org/wiki/Sandboxes > > But this patch could not sign-off with sandboxes, > "It's not possible currently to properly test zebra/dbupdate/installer > patches with those sandboxes" And this patch has an dbupdate. > > Bye > Zeno Tajoli > -- > Dr. Zeno Tajoli > Dipartimento Gestione delle Informazioni e della Conoscenza > z.tajoli at cineca.it > fax +39 02 2135520 > CINECA - Sede operativa di Segrate > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.tajoli at cineca.it Wed Jul 10 07:07:42 2013 From: z.tajoli at cineca.it (Zeno Tajoli) Date: Wed, 10 Jul 2013 07:07:42 +0200 (CEST) Subject: [Koha-devel] koha reservation expires automatically In-Reply-To: Message-ID: <914200727.6659381.1373432862402.JavaMail.root@cineca.it> Hi Ernesto, >I tried to aply the patch by copying manually the lines that are different in all the files. >The problem is that there are a lot of differens in my files (koha version 3.6.7) and the files that are included in the bug 8367. >Can I solved this problem?? or I need to update my koha? please don't work on your production server. Always wok on a test server. That the sign-off of patch must done on the master developement version , use 'git clone git://git.koha-community.org/koha.git kohaclone' to retrive the code. Download the code and in the head dir download the patch Apply the patch with git am -3 -i -u http://wiki.koha-community.org/wiki/Sign_off_on_patches#Apply_patch It is very difficult to port this patch to koha version 3.6.7. In my opinion a plan for you could be: Test the patch on master with a test server. If the path work, install a test server with last version of 3.12.x port the patch to 3.12.x If all works, port your installation to 3.12.x and use the patch in production. I don't if you have the tecnical skill to do this job, I suggest you to ask for a localy tecnical help. Bye Zeno Tajoli From fridolyn.somers at biblibre.com Wed Jul 10 16:06:40 2013 From: fridolyn.somers at biblibre.com (Fridolyn SOMERS) Date: Wed, 10 Jul 2013 16:06:40 +0200 Subject: [Koha-devel] UNIMARC_sync_date_created_with_marc_biblio.pl In-Reply-To: <51D173CD.8040704@ecp.fr> References: <51D173CD.8040704@ecp.fr> Message-ID: <51DD6A70.1040408@biblibre.com> This script uses 099$c and $d. Do you have these fields in your framework ? Regards, Le 01/07/2013 14:19, Samuel Desseaux a ?crit : > Hi, > > I've noticed a problem with my biblio records. > > Biblio.datecreated and biblio.timestamp are well fullfilled in the > database but are not displayed in the biblio record. > > I've executed this but with no results (in koha > / misc > / maintenance > /) perl > *UNIMARC_sync_date_created_with_marc_biblio.pl. > > Has someone an idea? > > Best regards, > > Samuel > * > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Fridolyn SOMERS Biblibre - P?le support fridolyn.somers at biblibre.com From M.de.Rooy at rijksmuseum.nl Thu Jul 11 09:16:11 2013 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 11 Jul 2013 07:16:11 +0000 Subject: [Koha-devel] FW: QA: Language material in install/mysql/data Message-ID: <809BE39CD64BFD4EB9036172EBCCFA310FFD68BA@S-MAIL-1B.rijksmuseum.intra> Just an update on this development: Bug 10509 now contains the i18n concept (with thanks to Galen). This patch adds some code to Installer.pm to support use of the sql i18n function while installing various languages. Bug 10520 changes the English folder (so no global folder for now). It inserts i18n calls in all .sql files for translatable columns. (i18n will do nothing for English itself.) The next step is changing the other languages: These .sql files will (mostly) be converted to a i18n definition that just contains the translation of string expressions. Running a language install now comes down to defining the right translation definition and then running the corresponding English script. When we reach this goal, we will have removed a lot of redundancy from the installer/data/mysql folder. Adding a notice or marc tag will be a lot easier (just insert in English, with automatic propagation to other languages). Generating translations via PO will be within reach. Both reports are ready for sign-off. Before starting work on the other language folders, I hope to see some progress on 10509 / 10520. The test plan for 10509 includes some tests that may illustrate the concept more clearly. Thanks! From danielg.koha at gmail.com Fri Jul 12 22:48:44 2013 From: danielg.koha at gmail.com (Daniel Grobani) Date: Fri, 12 Jul 2013 13:48:44 -0700 Subject: [Koha-devel] Call for news for the July newsletter Message-ID: Dear Koha kommunitarians, I'm harvesting news for this month's newsletter. Please send me by the 20th anything you think your fellow community members might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two for the gossip/society column about what you're currently working on. And if you know of a go-live not announced on the list, please be sure to let me know about it. Thanks, Daniel Grobani From fridolyn.somers at biblibre.com Mon Jul 15 13:17:04 2013 From: fridolyn.somers at biblibre.com (Fridolyn SOMERS) Date: Mon, 15 Jul 2013 13:17:04 +0200 Subject: [Koha-devel] Possible OPAC security pb Message-ID: <51E3DA30.5020602@biblibre.com> Hie, I've just opened http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10590. I've set it to critical because I think it is a security problem existing at OPAC : In opac-topissues the parameter limit is directly added at the end of the SQL query, without testing its value. A user can edit this parameter to add SQL code to query : for example : limit=10;DROP+TABLE+borrowers;. Please have a look and test. Best regards, -- Fridolyn SOMERS Biblibre - P?le support fridolyn.somers at biblibre.com From robin at catalyst.net.nz Mon Jul 15 16:20:14 2013 From: robin at catalyst.net.nz (Robin Sheat) Date: Mon, 15 Jul 2013 15:20:14 +0100 Subject: [Koha-devel] Possible OPAC security pb In-Reply-To: <51E3DA30.5020602@biblibre.com> References: <51E3DA30.5020602@biblibre.com> Message-ID: <51E4051E.7060807@catalyst.net.nz> Op 15/07/13 12:17, Fridolyn SOMERS schreef: > I've just opened > http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10590. > I've set it to critical because I think it is a security problem > existing at OPAC : So, on analysis, it is a terribly bad code smell that needs to be fixed, however you're not likely to be in immediate danger unless your mysql server has multiple statement execution turned on[0]. This said, there are two patches there now: Fridolyn's one that filters on input, and my followup that parameterises the SQL to add another layer of defence (also doing queries the way they're supposed to be done.) These are in the process of being tested and QAed now, people are encouraged to apply them as soon as they're in a release (or in git if you run from that) in case there is some vulnerable path to it I haven't thought of. [0] http://dev.mysql.com/doc/refman/5.0/en/c-api-multiple-queries.html -- thanks Galen for bringing that to my attention. -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 263 bytes Desc: OpenPGP digital signature URL: From tomascohen at gmail.com Mon Jul 15 17:16:46 2013 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Mon, 15 Jul 2013 12:16:46 -0300 Subject: [Koha-devel] July 15th: it's String Freeze Message-ID: Hi everyone, We are a week out from new releases of the 3.8.x, 3.10.x and 3.12.x stable branches. If you know of some QA-ed patch that deserves to be applied soon to the stable branches just let us know about it in the next 12 hours. Tomorrow morning (UTC-3 time) we are extracting the new strings to let translators have fun. Thanks The Release Maintenance Team (chall, bgkriegel and tcohen) -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmc at esilibrary.com Mon Jul 15 17:22:09 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Mon, 15 Jul 2013 08:22:09 -0700 Subject: [Koha-devel] Possible OPAC security pb In-Reply-To: <51E4051E.7060807@catalyst.net.nz> References: <51E3DA30.5020602@biblibre.com> <51E4051E.7060807@catalyst.net.nz> Message-ID: Hi, On Mon, Jul 15, 2013 at 7:20 AM, Robin Sheat wrote: > This said, there are two patches there now: Fridolyn's one that filters > on input, and my followup that parameterises the SQL to add another > layer of defence (also doing queries the way they're supposed to be > done.) > These two patches have now been tested and pushed to master [1, 2] [1] http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=57866d6b67c3f8b29290150f21c71395315a73fe [2] http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=89cf013a6fadcb1347151798f3fdab0d8c75cd15 Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolyn.somers at biblibre.com Mon Jul 15 20:19:53 2013 From: fridolyn.somers at biblibre.com (Fridolyn SOMERS) Date: Mon, 15 Jul 2013 20:19:53 +0200 Subject: [Koha-devel] Possible OPAC security pb In-Reply-To: References: <51E3DA30.5020602@biblibre.com> <51E4051E.7060807@catalyst.net.nz> Message-ID: <51E43D49.7040104@biblibre.com> Thanks everyone. Le 15/07/2013 17:22, Galen Charlton a ?crit : > Hi, > > On Mon, Jul 15, 2013 at 7:20 AM, Robin Sheat wrote: > >> This said, there are two patches there now: Fridolyn's one that filters >> on input, and my followup that parameterises the SQL to add another >> layer of defence (also doing queries the way they're supposed to be >> done.) >> > > These two patches have now been tested and pushed to master [1, 2] > > [1] > http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=57866d6b67c3f8b29290150f21c71395315a73fe > [2] > http://git.koha-community.org/gitweb/?p=koha.git;a=commit;h=89cf013a6fadcb1347151798f3fdab0d8c75cd15 > > Regards, > > Galen > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Fridolyn SOMERS Biblibre - P?le support fridolyn.somers at biblibre.com From vanoudt at gmail.com Fri Jul 19 04:51:43 2013 From: vanoudt at gmail.com (Nicholas van Oudtshoorn) Date: Fri, 19 Jul 2013 10:51:43 +0800 Subject: [Koha-devel] Catalogue Statistics report - limiting by dewey number Message-ID: Greetings all! Got a bit of a question here. As part of our academic (re)accreditation process, we need to provide a list of books aquired in a specific subject area over the past year. Fantastic - the Catalogue Report should do all that. (Well, it should do it when the patches in bug report 10608 are applied!) My problem: how to restrict the report according to the dewey number of the items. (This is, I think, the easiest way for us to show which books relevant to a specific subject area). However, looking at the code, it appears in catalogue_stats.pl that $has_dewey is disabled (in fact, the comment says it doesn't work - not sure why it and its remnants remain in both the perl and the templates???) So, unable to filter on dewey number, I've taken to filtering on the koha full call number. The problem is that I want to filter on the dewey part of the call number - not the full string. And this causes problems. Let me demonstrate. Using the current code path, if I'm searching for items between 227.0 and 227.15, I get 299 records (see APPENDIX A). Changing the code to cast the call number to a float as below (which gives me just the dewey localtion) if (@$filters[4]){ @$filters[4]=~ s/\*/%/g ; $strcalc .= " AND items.itemcallnumber >= (0+" . $dbh->quote(@$filters[4]) .")"; } if (@$filters[5]){ @$filters[5]=~ s/\*/%/g; $strcalc .= " AND items.itemcallnumber <= (0+" . $dbh->quote(@$filters[5]) .")"; } now gives me 308 records (see APPENDIX B) - including ones like 227 BRU where the decimal component (227.0) is implied. My question (at last!): is changing the code as above the right way to go about fixing this problem? (I realise that ideally one would want to make it an option in the report....). This same issue applies to other report modules - such as the circulation stats.... Any suggestions? How do other libraries deal with this? God bless, Nicholas van Oudtshoorn IT - Perth Bible College http://library.pbc.wa.edu.au/ APPENDIX A: THE ORIGINAL CODE PATH'S OUTPUT ---------------------------------------------------------------------------------------- items.itemcallnumber / items.homebranch TOTAL 227.02 BAR 1 227.02 BIR 1 227.02 DAV 1 227.02 DOD 1 227.02 DUN 1 227.02 ELL 1 227.02 ENG 1 227.02 GOM 1 227.02 GOO 1 227.02 GOR 1 227.02 GRI 1 227.02 KRU 1 227.02 LOA 1 227.02 MCR 1 227.02 MEY 1 227.02 NEY 1 227.02 OBR 1 227.02 RAM 1 227.02 REY 2 227.02 RID 1 227.02 ROB 1 227.02 SCH 3 227.02 SEI 1 227.02 SOB 1 227.02 STE 1 227.02 STR 2 227.02 TOI 2 227.02 WIL 1 227.02 WRI 3 227.02 YOU 1 227.02 ZIE 1 227.03 HAW 1 227.05 GAS 2 227.06 CAM 1 227.06 ELL 1 227.06 FOW 1 227.06 GRO 1 227.06 HAF 1 227.06 HAN 2 227.06 KEC 1 227.06 KRE 1 227.06 MAR 1 227.06 REA 1 227.06 SCR 1 227.06 STE 1 227.06 THI 1 227.06 WHI 1 227.066 BAN 2 227.066 DOT 1 227.066 HAN 1 227.066 REI 1 227.07 WES 1 227.08 WIL 1 227.08251 MUR 1 227.09 ARM 1 227.09 CON 2 227.09 GRO 1 227.09 HOW 1 227.09 MEI 1 227.09 OAK 1 227.09 PIN 1 227.09 RIC 1 227.09 SCH 1 227.091 RAM 1 227.092 DUN 2 227.092 OBR 1 227.092 WHI 1 227.1 ACH 1 227.1 BAR 10 227.1 BAR v.1 1 227.1 BAR v.2 1 227.1 BAR v.3 1 227.1 BAR v.4 1 227.1 BES 3 227.1 BLA 3 227.1 BOI 1 227.1 BOI v.3c.1 1 227.1 BOW 1 227.1 BRA 1 227.1 BRA v.6c.2 1 227.1 BRI 1 227.1 BRU 3 227.1 BUR 1 227.1 BYR 1 227.1 CHA 1 227.1 COA 1 227.1 COF 1 227.1 COS 1 227.1 CRA 3 227.1 DAV 1 227.1 DAW 1 227.1 DEH 1 227.1 DEW 1 227.1 DOD 4 227.1 DON 1 227.1 DUN v.1 1 227.1 DUN v.2 1 227.1 DYK 1 227.1 EDW 2 227.1 ELL 2 227.1 EPP 2 227.1 EPP V.1 1 227.1 EPP V.2 1 227.1 FIT 1 227.1 FOR 1 227.1 GOD v.1c.1 1 227.1 GOD v.2c.1 1 227.1 GRA 1 227.1 GRI 1 227.1 HAL 2 227.1 HAR 2 227.1 HEN 2 227.1 HOD 2 227.1 HOY 1 227.1 HUN 4 227.1 IRO 2 227.1 JOH 2 227.1 JOH v.1 1 227.1 JOH v.2 1 227.1 KAS 2 227.1 KEE 1 227.1 KEL 1 227.1 KIR 1 227.1 KRO 1 227.1 KRU 1 227.1 KUN 1 227.1 LEN 1 227.1 LLO v.11 1 227.1 LLO v.12 1 227.1 LLO v.1c.1 1 227.1 LLO v.2c.1 1 227.1 LLO v.3 1 227.1 LLO v.3c.2 1 227.1 LLO v.4 1 227.1 LLO v.4c.2 1 227.1 LLO v.5c.1 1 227.1 LLO v.5c.2 1 227.1 LLO v.6 1 227.1 LLO v.6c.2 1 227.1 LLO v.7 1 227.1 LLO v.7c.2 1 227.1 LLO v.8 1 227.1 LLO v.9c.1 1 227.1 LOA 1 227.1 LUT 2 227.1 MAC 1 227.1 MAC v.1c.1 1 227.1 MAC v.2c.1 1 227.1 MAL 1 227.1 MAT 1 227.1 MCC 2 227.1 MCD 1 227.1 MEE 1 227.1 MIT 2 227.1 MOO 7 227.1 MOR 3 227.1 MOU 6 227.1 MUR 2 227.1 MUR v.1c.2 1 227.1 NAS 3 227.1 NEW 2 227.1 NYG 2 227.1 NYS 1 227.1 OLS 1 227.1 OSB 1 227.1 PAI 1 227.1 PAL 1 227.1 PAT 1 227.1 PBC v.10 1 227.1 PBC v.1c.1 1 227.1 PBC v.2c.1 1 227.1 PBC v.3c.1 1 227.1 PBC v.4c.1 1 227.1 PBC v.5c.1 1 227.1 PBC v.6c.1 1 227.1 PBC v.7c.1 1 227.1 PBC v.8c.1 1 227.1 PBC v.9c.1 1 227.1 PET 1 227.1 PHI 1 227.1 PHI v.1 1 227.1 PHI v.2 1 227.1 RAT 1 227.1 RHY 1 227.1 RID 3 227.1 SAN 3 227.1 SCH 5 227.1 SCO 1 227.1 SCR 1 227.1 SEC 1 227.1 SHU 1 227.1 SPR 1 227.1 STE 2 227.1 STH 1 227.1 STO 3 227.1 STO v.1c.1 1 227.1 STO v.1c.2 1 227.1 STU 1 227.1 THO v.1c.1 1 227.1 THO v.2c.1 1 227.1 THO v.3c.1 1 227.1 THR 1 227.1 TUC 1 227.1 VIN 1 227.1 WIE 2 227.1 WIL 1 227.1 WUE 3 227.1 ZIE 1 227.104 IRO 1 227.105 SWA 1 227.106 DEI 1 227.106 GAT 1 227.106 GRE 1 227.106 MOU 1 227.106 SAB 1 227.106 SOD 1 227.107 PAU 1 227.108 WAL 1 227.12 GAM 1 TOTAL 299 APPENDIX B: THE MODIFIED CODE PATH'S OUTPUT: --------------------------------------------------------------------------------- items.itemcallnumber / items.homebranch TOTAL 227 BRU 1 227 FAL 1 227 HEB 1 227 LAK 1 227 MAC 1 227 RIC 1 227 SHE 1 227 STE 1 227 WAY 1 227.02 BAR 1 227.02 BIR 1 227.02 DAV 1 227.02 DOD 1 227.02 DUN 1 227.02 ELL 1 227.02 ENG 1 227.02 GOM 1 227.02 GOO 1 227.02 GOR 1 227.02 GRI 1 227.02 KRU 1 227.02 LOA 1 227.02 MCR 1 227.02 MEY 1 227.02 NEY 1 227.02 OBR 1 227.02 RAM 1 227.02 REY 2 227.02 RID 1 227.02 ROB 1 227.02 SCH 3 227.02 SEI 1 227.02 SOB 1 227.02 STE 1 227.02 STR 2 227.02 TOI 2 227.02 WIL 1 227.02 WRI 3 227.02 YOU 1 227.02 ZIE 1 227.03 HAW 1 227.05 GAS 2 227.06 CAM 1 227.06 ELL 1 227.06 FOW 1 227.06 GRO 1 227.06 HAF 1 227.06 HAN 2 227.06 KEC 1 227.06 KRE 1 227.06 MAR 1 227.06 REA 1 227.06 SCR 1 227.06 STE 1 227.06 THI 1 227.06 WHI 1 227.066 BAN 2 227.066 DOT 1 227.066 HAN 1 227.066 REI 1 227.07 WES 1 227.08 WIL 1 227.08251 MUR 1 227.09 ARM 1 227.09 CON 2 227.09 GRO 1 227.09 HOW 1 227.09 MEI 1 227.09 OAK 1 227.09 PIN 1 227.09 RIC 1 227.09 SCH 1 227.091 RAM 1 227.092 DUN 2 227.092 OBR 1 227.092 WHI 1 227.1 ACH 1 227.1 BAR 10 227.1 BAR v.1 1 227.1 BAR v.2 1 227.1 BAR v.3 1 227.1 BAR v.4 1 227.1 BES 3 227.1 BLA 3 227.1 BOI 1 227.1 BOI v.3c.1 1 227.1 BOW 1 227.1 BRA 1 227.1 BRA v.6c.2 1 227.1 BRI 1 227.1 BRU 3 227.1 BUR 1 227.1 BYR 1 227.1 CHA 1 227.1 COA 1 227.1 COF 1 227.1 COS 1 227.1 CRA 3 227.1 DAV 1 227.1 DAW 1 227.1 DEH 1 227.1 DEW 1 227.1 DOD 4 227.1 DON 1 227.1 DUN v.1 1 227.1 DUN v.2 1 227.1 DYK 1 227.1 EDW 2 227.1 ELL 2 227.1 EPP 2 227.1 EPP V.1 1 227.1 EPP V.2 1 227.1 FIT 1 227.1 FOR 1 227.1 GOD v.1c.1 1 227.1 GOD v.2c.1 1 227.1 GRA 1 227.1 GRI 1 227.1 HAL 2 227.1 HAR 2 227.1 HEN 2 227.1 HOD 2 227.1 HOY 1 227.1 HUN 4 227.1 IRO 2 227.1 JOH 2 227.1 JOH v.1 1 227.1 JOH v.2 1 227.1 KAS 2 227.1 KEE 1 227.1 KEL 1 227.1 KIR 1 227.1 KRO 1 227.1 KRU 1 227.1 KUN 1 227.1 LEN 1 227.1 LLO v.11 1 227.1 LLO v.12 1 227.1 LLO v.1c.1 1 227.1 LLO v.2c.1 1 227.1 LLO v.3 1 227.1 LLO v.3c.2 1 227.1 LLO v.4 1 227.1 LLO v.4c.2 1 227.1 LLO v.5c.1 1 227.1 LLO v.5c.2 1 227.1 LLO v.6 1 227.1 LLO v.6c.2 1 227.1 LLO v.7 1 227.1 LLO v.7c.2 1 227.1 LLO v.8 1 227.1 LLO v.9c.1 1 227.1 LOA 1 227.1 LUT 2 227.1 MAC 1 227.1 MAC v.1c.1 1 227.1 MAC v.2c.1 1 227.1 MAL 1 227.1 MAT 1 227.1 MCC 2 227.1 MCD 1 227.1 MEE 1 227.1 MIT 2 227.1 MOO 7 227.1 MOR 3 227.1 MOU 6 227.1 MUR 2 227.1 MUR v.1c.2 1 227.1 NAS 3 227.1 NEW 2 227.1 NYG 2 227.1 NYS 1 227.1 OLS 1 227.1 OSB 1 227.1 PAI 1 227.1 PAL 1 227.1 PAT 1 227.1 PBC v.10 1 227.1 PBC v.1c.1 1 227.1 PBC v.2c.1 1 227.1 PBC v.3c.1 1 227.1 PBC v.4c.1 1 227.1 PBC v.5c.1 1 227.1 PBC v.6c.1 1 227.1 PBC v.7c.1 1 227.1 PBC v.8c.1 1 227.1 PBC v.9c.1 1 227.1 PET 1 227.1 PHI 1 227.1 PHI v.1 1 227.1 PHI v.2 1 227.1 RAT 1 227.1 RHY 1 227.1 RID 3 227.1 SAN 3 227.1 SCH 5 227.1 SCO 1 227.1 SCR 1 227.1 SEC 1 227.1 SHU 1 227.1 SPR 1 227.1 STE 2 227.1 STH 1 227.1 STO 3 227.1 STO v.1c.1 1 227.1 STO v.1c.2 1 227.1 STU 1 227.1 THO v.1c.1 1 227.1 THO v.2c.1 1 227.1 THO v.3c.1 1 227.1 THR 1 227.1 TUC 1 227.1 VIN 1 227.1 WIE 2 227.1 WIL 1 227.1 WUE 3 227.1 ZIE 1 227.104 IRO 1 227.105 SWA 1 227.106 DEI 1 227.106 GAT 1 227.106 GRE 1 227.106 MOU 1 227.106 SAB 1 227.106 SOD 1 227.107 PAU 1 227.108 WAL 1 227.12 GAM 1 TOTAL 308 From micah.roth at ucla.edu Wed Jul 24 06:14:25 2013 From: micah.roth at ucla.edu (ndroftheline) Date: Tue, 23 Jul 2013 21:14:25 -0700 (PDT) Subject: [Koha-devel] Fedora packages // including PLACK support In-Reply-To: References: Message-ID: <1374639265053-5762399.post@n5.nabble.com> Hello! I noticed there are already repository directories for Fedora 18 and 19 - awesome! I'm on Fedora 18 and trying to get Koha going. How would using this repository change the installation instructions from the default INSTALL file? Can I use the systemd service files you posted for Fedora 17 in Fedora 18? Thank you! ~Micah -- View this message in context: http://koha.1045719.n5.nabble.com/Fedora-packages-including-PLACK-support-tp5739371p5762399.html Sent from the Koha-devel mailing list archive at Nabble.com. From 5p4m at gmx.de Sat Jul 27 18:23:17 2013 From: 5p4m at gmx.de (Mirko) Date: Sat, 27 Jul 2013 18:23:17 +0200 Subject: [Koha-devel] Kohacon 2014 proposals: deadline 15 September Message-ID: <51F3F3F5.1010207@gmx.de> Dear lists, during the last IRC meeting it has been decided that 1. proposals for Kohacon 2014 have to be submitted until 15 September 2. we will vote in the first week of October So far there is one proposal (C?rdoba, Argentina). In case there won't be more submissions, C?rdoba wins by default. If you would like to host Kohacon 2014, now is the time to enter a sumbission here http://wiki.koha-community.org/wiki/KohaCon2014_Proposals Have a nice weekend, Mirko From gmc at esilibrary.com Tue Jul 30 00:48:35 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Mon, 29 Jul 2013 15:48:35 -0700 Subject: [Koha-devel] Koha security release -- July 2013 Message-ID: [Apologies for multi-posting] The Koha community is releasing a security update for all supported and recent unsupported versions of Koha. The security update is available for the following new releases: 3.12.3 3.10.9 3.8.16 3.6.12 Patches are also available for 3.2.x and 3.4.x. The security update fixes a situation where manipulation of the cookie used for retaining OPAC search history for anonymous sessions could theoretically result in the execution of arbitrary code on a Koha webserver. We are aware of no active exploits at this time. The security issue can be mitigated by turning off the EnableOpacSearchHistory system preference We recommend that all Koha users upgrade as soon as possible. If you cannot upgrade immediately, we strongly encourage you to turn off the EnableOpacSearchHistory system preference until such time as you can upgrade. Users of the Debian packages for 3.10.x and 3.12.x can get the latest release by running apt-get update followed by apt-get upgrade. Because a new dependency was added recently, it may be necessary to run apt-get dist-upgrade instead or to run apt-get install koha-common. For users of the Debian packages for 3.8.x and 3.6.x, since the Koha APT repository no longer contains those versions, .deb files are available for download and installation using dpkg -i: .deb for 3.8.16: http://download.koha-community.org/koha-common_3.08.16.1-1_all.deb .deb for 3.6.12: http://download.koha-community.org/koha-common_3.06.12.1-1_all.deb Tarballs are also available: 3.12.3: http://download.koha-community.org/koha-3.12.03.tar.gz 3.10.9: http://download.koha-community.org/koha-3.10.09.tar.gz 3.8.16: http://download.koha-community.org/koha-3.08.16.tar.gz 3.6.12: http://download.koha-community.org/old_releases/koha-3.06.12.tar.gz The patches for 3.4.x and 3.2.x can be found as the top three commits in the 3.4.x and 3.2.x branches in Koha?s Git repository. As a general note, if you are not running a version of Koha that has has a release maintainer (current 3.8.x, 3.10.x, and 3.12.x), we strongly urge you to upgrade to a supported version. Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolyn.somers at biblibre.com Wed Jul 31 10:07:14 2013 From: fridolyn.somers at biblibre.com (Fridolyn SOMERS) Date: Wed, 31 Jul 2013 10:07:14 +0200 Subject: [Koha-devel] Catalogue Statistics report - limiting by dewey number In-Reply-To: References: Message-ID: <51F8C5B2.4080500@biblibre.com> I think you should use the column 'cn_sort' of items. It contains the item callnumber stored in a special form depending on classification source (see /cgi-bin/koha/admin/classsources.pl). Regards, Le 19/07/2013 04:51, Nicholas van Oudtshoorn a ?crit : > > Greetings all! > > Got a bit of a question here. As part of our academic (re)accreditation > process, we need to provide a list of books aquired in a specific > subject area over the past year. Fantastic - the Catalogue Report should > do all that. (Well, it should do it when the patches in bug report 10608 > are applied!) > > My problem: how to restrict the report according to the dewey number of > the items. (This is, I think, the easiest way for us to show which books > relevant to a specific subject area). However, looking at the code, it > appears in catalogue_stats.pl that $has_dewey is disabled (in fact, the > comment says it doesn't work - not sure why it and its remnants remain > in both the perl and the templates???) > > So, unable to filter on dewey number, I've taken to filtering on the > koha full call number. The problem is that I want to filter on the dewey > part of the call number - not the full string. And this causes problems. > Let me demonstrate. Using the current code path, if I'm searching for > items between 227.0 and 227.15, I get 299 records (see APPENDIX A). > Changing the code to cast the call number to a float as below (which > gives me just the dewey localtion) > > if (@$filters[4]){ > @$filters[4]=~ s/\*/%/g ; > $strcalc .= " AND items.itemcallnumber >= (0+" . > $dbh->quote(@$filters[4]) .")"; > } > > if (@$filters[5]){ > @$filters[5]=~ s/\*/%/g; > $strcalc .= " AND items.itemcallnumber <= (0+" . > $dbh->quote(@$filters[5]) .")"; > } > > now gives me 308 records (see APPENDIX B) - including ones like 227 BRU > where the decimal component (227.0) is implied. > > My question (at last!): is changing the code as above the right way to > go about fixing this problem? (I realise that ideally one would want to > make it an option in the report....). > > This same issue applies to other report modules - such as the > circulation stats.... > > Any suggestions? How do other libraries deal with this? > > > God bless, > Nicholas van Oudtshoorn > IT - Perth Bible College > http://library.pbc.wa.edu.au/ > > > APPENDIX A: THE ORIGINAL CODE PATH'S OUTPUT > ---------------------------------------------------------------------------------------- > > > items.itemcallnumber / items.homebranch TOTAL > 227.02 BAR 1 > 227.02 BIR 1 > 227.02 DAV 1 > 227.02 DOD 1 > 227.02 DUN 1 > 227.02 ELL 1 > 227.02 ENG 1 > 227.02 GOM 1 > 227.02 GOO 1 > 227.02 GOR 1 > 227.02 GRI 1 > 227.02 KRU 1 > 227.02 LOA 1 > 227.02 MCR 1 > 227.02 MEY 1 > 227.02 NEY 1 > 227.02 OBR 1 > 227.02 RAM 1 > 227.02 REY 2 > 227.02 RID 1 > 227.02 ROB 1 > 227.02 SCH 3 > 227.02 SEI 1 > 227.02 SOB 1 > 227.02 STE 1 > 227.02 STR 2 > 227.02 TOI 2 > 227.02 WIL 1 > 227.02 WRI 3 > 227.02 YOU 1 > 227.02 ZIE 1 > 227.03 HAW 1 > 227.05 GAS 2 > 227.06 CAM 1 > 227.06 ELL 1 > 227.06 FOW 1 > 227.06 GRO 1 > 227.06 HAF 1 > 227.06 HAN 2 > 227.06 KEC 1 > 227.06 KRE 1 > 227.06 MAR 1 > 227.06 REA 1 > 227.06 SCR 1 > 227.06 STE 1 > 227.06 THI 1 > 227.06 WHI 1 > 227.066 BAN 2 > 227.066 DOT 1 > 227.066 HAN 1 > 227.066 REI 1 > 227.07 WES 1 > 227.08 WIL 1 > 227.08251 MUR 1 > 227.09 ARM 1 > 227.09 CON 2 > 227.09 GRO 1 > 227.09 HOW 1 > 227.09 MEI 1 > 227.09 OAK 1 > 227.09 PIN 1 > 227.09 RIC 1 > 227.09 SCH 1 > 227.091 RAM 1 > 227.092 DUN 2 > 227.092 OBR 1 > 227.092 WHI 1 > 227.1 ACH 1 > 227.1 BAR 10 > 227.1 BAR v.1 1 > 227.1 BAR v.2 1 > 227.1 BAR v.3 1 > 227.1 BAR v.4 1 > 227.1 BES 3 > 227.1 BLA 3 > 227.1 BOI 1 > 227.1 BOI v.3c.1 1 > 227.1 BOW 1 > 227.1 BRA 1 > 227.1 BRA v.6c.2 1 > 227.1 BRI 1 > 227.1 BRU 3 > 227.1 BUR 1 > 227.1 BYR 1 > 227.1 CHA 1 > 227.1 COA 1 > 227.1 COF 1 > 227.1 COS 1 > 227.1 CRA 3 > 227.1 DAV 1 > 227.1 DAW 1 > 227.1 DEH 1 > 227.1 DEW 1 > 227.1 DOD 4 > 227.1 DON 1 > 227.1 DUN v.1 1 > 227.1 DUN v.2 1 > 227.1 DYK 1 > 227.1 EDW 2 > 227.1 ELL 2 > 227.1 EPP 2 > 227.1 EPP V.1 1 > 227.1 EPP V.2 1 > 227.1 FIT 1 > 227.1 FOR 1 > 227.1 GOD v.1c.1 1 > 227.1 GOD v.2c.1 1 > 227.1 GRA 1 > 227.1 GRI 1 > 227.1 HAL 2 > 227.1 HAR 2 > 227.1 HEN 2 > 227.1 HOD 2 > 227.1 HOY 1 > 227.1 HUN 4 > 227.1 IRO 2 > 227.1 JOH 2 > 227.1 JOH v.1 1 > 227.1 JOH v.2 1 > 227.1 KAS 2 > 227.1 KEE 1 > 227.1 KEL 1 > 227.1 KIR 1 > 227.1 KRO 1 > 227.1 KRU 1 > 227.1 KUN 1 > 227.1 LEN 1 > 227.1 LLO v.11 1 > 227.1 LLO v.12 1 > 227.1 LLO v.1c.1 1 > 227.1 LLO v.2c.1 1 > 227.1 LLO v.3 1 > 227.1 LLO v.3c.2 1 > 227.1 LLO v.4 1 > 227.1 LLO v.4c.2 1 > 227.1 LLO v.5c.1 1 > 227.1 LLO v.5c.2 1 > 227.1 LLO v.6 1 > 227.1 LLO v.6c.2 1 > 227.1 LLO v.7 1 > 227.1 LLO v.7c.2 1 > 227.1 LLO v.8 1 > 227.1 LLO v.9c.1 1 > 227.1 LOA 1 > 227.1 LUT 2 > 227.1 MAC 1 > 227.1 MAC v.1c.1 1 > 227.1 MAC v.2c.1 1 > 227.1 MAL 1 > 227.1 MAT 1 > 227.1 MCC 2 > 227.1 MCD 1 > 227.1 MEE 1 > 227.1 MIT 2 > 227.1 MOO 7 > 227.1 MOR 3 > 227.1 MOU 6 > 227.1 MUR 2 > 227.1 MUR v.1c.2 1 > 227.1 NAS 3 > 227.1 NEW 2 > 227.1 NYG 2 > 227.1 NYS 1 > 227.1 OLS 1 > 227.1 OSB 1 > 227.1 PAI 1 > 227.1 PAL 1 > 227.1 PAT 1 > 227.1 PBC v.10 1 > 227.1 PBC v.1c.1 1 > 227.1 PBC v.2c.1 1 > 227.1 PBC v.3c.1 1 > 227.1 PBC v.4c.1 1 > 227.1 PBC v.5c.1 1 > 227.1 PBC v.6c.1 1 > 227.1 PBC v.7c.1 1 > 227.1 PBC v.8c.1 1 > 227.1 PBC v.9c.1 1 > 227.1 PET 1 > 227.1 PHI 1 > 227.1 PHI v.1 1 > 227.1 PHI v.2 1 > 227.1 RAT 1 > 227.1 RHY 1 > 227.1 RID 3 > 227.1 SAN 3 > 227.1 SCH 5 > 227.1 SCO 1 > 227.1 SCR 1 > 227.1 SEC 1 > 227.1 SHU 1 > 227.1 SPR 1 > 227.1 STE 2 > 227.1 STH 1 > 227.1 STO 3 > 227.1 STO v.1c.1 1 > 227.1 STO v.1c.2 1 > 227.1 STU 1 > 227.1 THO v.1c.1 1 > 227.1 THO v.2c.1 1 > 227.1 THO v.3c.1 1 > 227.1 THR 1 > 227.1 TUC 1 > 227.1 VIN 1 > 227.1 WIE 2 > 227.1 WIL 1 > 227.1 WUE 3 > 227.1 ZIE 1 > 227.104 IRO 1 > 227.105 SWA 1 > 227.106 DEI 1 > 227.106 GAT 1 > 227.106 GRE 1 > 227.106 MOU 1 > 227.106 SAB 1 > 227.106 SOD 1 > 227.107 PAU 1 > 227.108 WAL 1 > 227.12 GAM 1 > TOTAL 299 > > APPENDIX B: THE MODIFIED CODE PATH'S OUTPUT: > --------------------------------------------------------------------------------- > > items.itemcallnumber / items.homebranch TOTAL > 227 BRU 1 > 227 FAL 1 > 227 HEB 1 > 227 LAK 1 > 227 MAC 1 > 227 RIC 1 > 227 SHE 1 > 227 STE 1 > 227 WAY 1 > 227.02 BAR 1 > 227.02 BIR 1 > 227.02 DAV 1 > 227.02 DOD 1 > 227.02 DUN 1 > 227.02 ELL 1 > 227.02 ENG 1 > 227.02 GOM 1 > 227.02 GOO 1 > 227.02 GOR 1 > 227.02 GRI 1 > 227.02 KRU 1 > 227.02 LOA 1 > 227.02 MCR 1 > 227.02 MEY 1 > 227.02 NEY 1 > 227.02 OBR 1 > 227.02 RAM 1 > 227.02 REY 2 > 227.02 RID 1 > 227.02 ROB 1 > 227.02 SCH 3 > 227.02 SEI 1 > 227.02 SOB 1 > 227.02 STE 1 > 227.02 STR 2 > 227.02 TOI 2 > 227.02 WIL 1 > 227.02 WRI 3 > 227.02 YOU 1 > 227.02 ZIE 1 > 227.03 HAW 1 > 227.05 GAS 2 > 227.06 CAM 1 > 227.06 ELL 1 > 227.06 FOW 1 > 227.06 GRO 1 > 227.06 HAF 1 > 227.06 HAN 2 > 227.06 KEC 1 > 227.06 KRE 1 > 227.06 MAR 1 > 227.06 REA 1 > 227.06 SCR 1 > 227.06 STE 1 > 227.06 THI 1 > 227.06 WHI 1 > 227.066 BAN 2 > 227.066 DOT 1 > 227.066 HAN 1 > 227.066 REI 1 > 227.07 WES 1 > 227.08 WIL 1 > 227.08251 MUR 1 > 227.09 ARM 1 > 227.09 CON 2 > 227.09 GRO 1 > 227.09 HOW 1 > 227.09 MEI 1 > 227.09 OAK 1 > 227.09 PIN 1 > 227.09 RIC 1 > 227.09 SCH 1 > 227.091 RAM 1 > 227.092 DUN 2 > 227.092 OBR 1 > 227.092 WHI 1 > 227.1 ACH 1 > 227.1 BAR 10 > 227.1 BAR v.1 1 > 227.1 BAR v.2 1 > 227.1 BAR v.3 1 > 227.1 BAR v.4 1 > 227.1 BES 3 > 227.1 BLA 3 > 227.1 BOI 1 > 227.1 BOI v.3c.1 1 > 227.1 BOW 1 > 227.1 BRA 1 > 227.1 BRA v.6c.2 1 > 227.1 BRI 1 > 227.1 BRU 3 > 227.1 BUR 1 > 227.1 BYR 1 > 227.1 CHA 1 > 227.1 COA 1 > 227.1 COF 1 > 227.1 COS 1 > 227.1 CRA 3 > 227.1 DAV 1 > 227.1 DAW 1 > 227.1 DEH 1 > 227.1 DEW 1 > 227.1 DOD 4 > 227.1 DON 1 > 227.1 DUN v.1 1 > 227.1 DUN v.2 1 > 227.1 DYK 1 > 227.1 EDW 2 > 227.1 ELL 2 > 227.1 EPP 2 > 227.1 EPP V.1 1 > 227.1 EPP V.2 1 > 227.1 FIT 1 > 227.1 FOR 1 > 227.1 GOD v.1c.1 1 > 227.1 GOD v.2c.1 1 > 227.1 GRA 1 > 227.1 GRI 1 > 227.1 HAL 2 > 227.1 HAR 2 > 227.1 HEN 2 > 227.1 HOD 2 > 227.1 HOY 1 > 227.1 HUN 4 > 227.1 IRO 2 > 227.1 JOH 2 > 227.1 JOH v.1 1 > 227.1 JOH v.2 1 > 227.1 KAS 2 > 227.1 KEE 1 > 227.1 KEL 1 > 227.1 KIR 1 > 227.1 KRO 1 > 227.1 KRU 1 > 227.1 KUN 1 > 227.1 LEN 1 > 227.1 LLO v.11 1 > 227.1 LLO v.12 1 > 227.1 LLO v.1c.1 1 > 227.1 LLO v.2c.1 1 > 227.1 LLO v.3 1 > 227.1 LLO v.3c.2 1 > 227.1 LLO v.4 1 > 227.1 LLO v.4c.2 1 > 227.1 LLO v.5c.1 1 > 227.1 LLO v.5c.2 1 > 227.1 LLO v.6 1 > 227.1 LLO v.6c.2 1 > 227.1 LLO v.7 1 > 227.1 LLO v.7c.2 1 > 227.1 LLO v.8 1 > 227.1 LLO v.9c.1 1 > 227.1 LOA 1 > 227.1 LUT 2 > 227.1 MAC 1 > 227.1 MAC v.1c.1 1 > 227.1 MAC v.2c.1 1 > 227.1 MAL 1 > 227.1 MAT 1 > 227.1 MCC 2 > 227.1 MCD 1 > 227.1 MEE 1 > 227.1 MIT 2 > 227.1 MOO 7 > 227.1 MOR 3 > 227.1 MOU 6 > 227.1 MUR 2 > 227.1 MUR v.1c.2 1 > 227.1 NAS 3 > 227.1 NEW 2 > 227.1 NYG 2 > 227.1 NYS 1 > 227.1 OLS 1 > 227.1 OSB 1 > 227.1 PAI 1 > 227.1 PAL 1 > 227.1 PAT 1 > 227.1 PBC v.10 1 > 227.1 PBC v.1c.1 1 > 227.1 PBC v.2c.1 1 > 227.1 PBC v.3c.1 1 > 227.1 PBC v.4c.1 1 > 227.1 PBC v.5c.1 1 > 227.1 PBC v.6c.1 1 > 227.1 PBC v.7c.1 1 > 227.1 PBC v.8c.1 1 > 227.1 PBC v.9c.1 1 > 227.1 PET 1 > 227.1 PHI 1 > 227.1 PHI v.1 1 > 227.1 PHI v.2 1 > 227.1 RAT 1 > 227.1 RHY 1 > 227.1 RID 3 > 227.1 SAN 3 > 227.1 SCH 5 > 227.1 SCO 1 > 227.1 SCR 1 > 227.1 SEC 1 > 227.1 SHU 1 > 227.1 SPR 1 > 227.1 STE 2 > 227.1 STH 1 > 227.1 STO 3 > 227.1 STO v.1c.1 1 > 227.1 STO v.1c.2 1 > 227.1 STU 1 > 227.1 THO v.1c.1 1 > 227.1 THO v.2c.1 1 > 227.1 THO v.3c.1 1 > 227.1 THR 1 > 227.1 TUC 1 > 227.1 VIN 1 > 227.1 WIE 2 > 227.1 WIL 1 > 227.1 WUE 3 > 227.1 ZIE 1 > 227.104 IRO 1 > 227.105 SWA 1 > 227.106 DEI 1 > 227.106 GAT 1 > 227.106 GRE 1 > 227.106 MOU 1 > 227.106 SAB 1 > 227.106 SOD 1 > 227.107 PAU 1 > 227.108 WAL 1 > 227.12 GAM 1 > TOTAL 308 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ -- Fridolyn SOMERS Biblibre - P?le support fridolyn.somers at biblibre.com From fridolyn.somers at biblibre.com Wed Jul 31 10:21:11 2013 From: fridolyn.somers at biblibre.com (Fridolyn SOMERS) Date: Wed, 31 Jul 2013 10:21:11 +0200 Subject: [Koha-devel] Koha-index-daemon In-Reply-To: <1229654669.102900.1372536367646.JavaMail.tomcat@be02> References: <1229654669.102900.1372536367646.JavaMail.tomcat@be02> Message-ID: <51F8C8F7.4090500@biblibre.com> I think the koha-index-daemon needs to be dependent on MySQL server starting. I created a bug for that : Bug 10665. Le 29/06/2013 22:06, Partha Mukhopadhyay a ?crit : > Dear all > > Reporting a problem for koha-index-daemon (Koha 3.12.01 on Ubuntu 12.04): > > 1. Evertime I restart computer I need to manually start koha-index-daemon > although i've used following instructions: > > sudo ln -s /usr/share/koha/bin/koha-index-daemon-ctl.sh /etc/init.d/koha-index-daemon > sudo update-rc.d koha-index-daemon defaults > sudo service koha-index-daemon start > > 2. The log file (koha-index-daemon.err): > > 20130629 03:05:15 koha-index-daemon-koha: client (pid 2650) killed by signal 15, respawning > 20130629 03:06:46 koha-index-daemon-koha: client (pid 2682) killed by signal 15, stopping > 20130629 08:10:38 koha-index-daemon-koha: client (pid 2623) killed by signal 15, respawning > 20130629 09:51:05 koha-index-daemon-koha: client (pid 2642) killed by signal 15, stopping > 20130630 00:18:21 koha-index-daemon-koha: client (pid 3580) killed by signal 15, respawning > 20130630 00:46:04 koha-index-daemon-koha: client (pid 3599) killed by signal 15, stopping > 20130630 00:56:46 koha-index-daemon-koha: client (pid 4037) killed by signal 15, stopping > 20130630 00:56:53 koha-index-daemon-koha: client (pid 4072) killed by signal 15, respawning > 20130630 00:58:38 koha-index-daemon-koha: client (pid 4091) killed by signal 15, stopping > 20130630 01:03:42 koha-index-daemon-koha: client (pid 2610) killed by signal 15, respawning > 20130630 01:04:17 koha-index-daemon-koha: client (pid 2629) killed by signal 15, stopping > 20130630 01:06:11 koha-index-daemon-koha: client (pid 2551) killed by signal 15, respawning > 20130630 01:17:39 koha-index-daemon-koha: client (pid 2568) killed by signal 15, respawning > > 3. the output log: > > DBD::mysql::st execute failed: MySQL server has gone away at /usr/local/share/perl/5.14.2/Koha/Contrib/Tamil/IndexerDaemon.pm line 71. > DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/share/perl/5.14.2/Koha/Contrib/Tamil/IndexerDaemon.pm line 73. > DBD::mysql::st execute failed: MySQL server has gone away at /usr/local/share/perl/5.14.2/Koha/Contrib/Tamil/IndexerDaemon.pm line 71. > DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/share/perl/5.14.2/Koha/Contrib/Tamil/IndexerDaemon.pm line 73. > > when i start it manually ebverything works fine. > > Pl help.... > > Partha > > ---------------------------------------------------- > > Dr. Parthasarathi Mukhopadhyay > > Associate Prof. > > Department of Library and Information Science > > University of Kalyani (WB, India) > > ------------------------------------------ > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.org/ > -- Fridolyn SOMERS Biblibre - P?le support fridolyn.somers at biblibre.com From tomascohen at gmail.com Wed Jul 31 14:51:00 2013 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 31 Jul 2013 09:51:00 -0300 Subject: [Koha-devel] Koha-index-daemon In-Reply-To: <51F8C8F7.4090500@biblibre.com> References: <1229654669.102900.1372536367646.JavaMail.tomcat@be02> <51F8C8F7.4090500@biblibre.com> Message-ID: I'm not sure which is the best solution, because this would break the setup for people using remote DB servers. I'd fill a bug on Koha::Contrib::Tamil asking for the indexer to recover when the DB server is available again. Talk to Frederic about this. On Wed, Jul 31, 2013 at 5:21 AM, Fridolyn SOMERS < fridolyn.somers at biblibre.com> wrote: > I think the koha-index-daemon needs to be dependent on MySQL server > starting. > I created a bug for that : Bug 10665. > > Le 29/06/2013 22:06, Partha Mukhopadhyay a ?crit : > >> Dear all >> >> Reporting a problem for koha-index-daemon (Koha 3.12.01 on Ubuntu 12.04): >> >> 1. Evertime I restart computer I need to manually start koha-index-daemon >> although i've used following instructions: >> >> sudo ln -s /usr/share/koha/bin/koha-**index-daemon-ctl.sh >> /etc/init.d/koha-index-daemon >> sudo update-rc.d koha-index-daemon defaults >> sudo service koha-index-daemon start >> >> 2. The log file (koha-index-daemon.err): >> >> 20130629 03:05:15 koha-index-daemon-koha: client (pid 2650) killed by >> signal 15, respawning >> 20130629 03:06:46 koha-index-daemon-koha: client (pid 2682) killed by >> signal 15, stopping >> 20130629 08:10:38 koha-index-daemon-koha: client (pid 2623) killed by >> signal 15, respawning >> 20130629 09:51:05 koha-index-daemon-koha: client (pid 2642) killed by >> signal 15, stopping >> 20130630 00:18:21 koha-index-daemon-koha: client (pid 3580) killed by >> signal 15, respawning >> 20130630 00:46:04 koha-index-daemon-koha: client (pid 3599) killed by >> signal 15, stopping >> 20130630 00:56:46 koha-index-daemon-koha: client (pid 4037) killed by >> signal 15, stopping >> 20130630 00:56:53 koha-index-daemon-koha: client (pid 4072) killed by >> signal 15, respawning >> 20130630 00:58:38 koha-index-daemon-koha: client (pid 4091) killed by >> signal 15, stopping >> 20130630 01:03:42 koha-index-daemon-koha: client (pid 2610) killed by >> signal 15, respawning >> 20130630 01:04:17 koha-index-daemon-koha: client (pid 2629) killed by >> signal 15, stopping >> 20130630 01:06:11 koha-index-daemon-koha: client (pid 2551) killed by >> signal 15, respawning >> 20130630 01:17:39 koha-index-daemon-koha: client (pid 2568) killed by >> signal 15, respawning >> >> 3. the output log: >> >> DBD::mysql::st execute failed: MySQL server has gone away at >> /usr/local/share/perl/5.14.2/**Koha/Contrib/Tamil/**IndexerDaemon.pm >> line 71. >> DBD::mysql::st fetchrow failed: fetch() without execute() at >> /usr/local/share/perl/5.14.2/**Koha/Contrib/Tamil/**IndexerDaemon.pm >> line 73. >> DBD::mysql::st execute failed: MySQL server has gone away at >> /usr/local/share/perl/5.14.2/**Koha/Contrib/Tamil/**IndexerDaemon.pm >> line 71. >> DBD::mysql::st fetchrow failed: fetch() without execute() at >> /usr/local/share/perl/5.14.2/**Koha/Contrib/Tamil/**IndexerDaemon.pm >> line 73. >> >> when i start it manually ebverything works fine. >> >> Pl help.... >> >> Partha >> >> ------------------------------**---------------------- >> >> Dr. Parthasarathi Mukhopadhyay >> >> Associate Prof. >> >> Department of Library and Information Science >> >> University of Kalyani (WB, India) >> >> ------------------------------**------------ >> >> >> >> ______________________________**_________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-**community.org >> http://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-devel >> website : http://www.koha-community.org/ >> git : http://git.koha-community.org/ >> bugs : http://bugs.koha-community.**org/ >> >> > -- > Fridolyn SOMERS > Biblibre - P?le support > fridolyn.somers at biblibre.com > > ______________________________**_________________ > Koha-devel mailing list > Koha-devel at lists.koha-**community.org > http://lists.koha-community.**org/cgi-bin/mailman/listinfo/**koha-devel > website : http://www.koha-community.org/ > git : http://git.koha-community.org/ > bugs : http://bugs.koha-community.**org/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hbraum at nekls.org Wed Jul 31 21:33:09 2013 From: hbraum at nekls.org (Heather Braum (NEKLS)) Date: Wed, 31 Jul 2013 14:33:09 -0500 Subject: [Koha-devel] Permission vs System preference Message-ID: We are interested at some point in a development that would hide the "Edit items in batch"; "Delete items in batch"; and "Delete all items" options in the Edit menu of the detail.pl page through either a user permission or a system preference. It was suggested I contact the developers list to see what community developers think about this as a permission vs system preference. In our consortial environment, these are not good features to have available to anyone. Right now we have these options hidden through some hardcoding, but of course this has to be added manually after every upgrade by our support vendor. Any thoughts/input would be greatly appreciated. Thanks, Heather Braum Digital and Technical Services Librarian Northeast Kansas Library System hbraum at nekls.org "The illiterate of the 21st century will not be those cannot read and write, but those who cannot learn, unlearn, and relearn." ~Alvin Toffler, *Rethinking the Future* -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmc at esilibrary.com Wed Jul 31 21:43:11 2013 From: gmc at esilibrary.com (Galen Charlton) Date: Wed, 31 Jul 2013 12:43:11 -0700 Subject: [Koha-devel] Permission vs System preference In-Reply-To: References: Message-ID: Hi, On Wed, Jul 31, 2013 at 12:33 PM, Heather Braum (NEKLS) wrote: > We are interested at some point in a development that would hide the "Edit > items in batch"; "Delete items in batch"; and "Delete all items" options > in the Edit menu of the detail.pl page through either a user permission > or a system preference. It was suggested I contact the developers list to > see what community developers think about this as a permission vs system > preference. > I'm in favor of permissions (and also a little confused) because ... two of those menu options are already protected by permissions, specifically tools/items_batchdel and tools/items_batchmod. There is no permission (other than the general permission that grants the ability to edit items) guarding the 'Delete all items' permission, but I think it would be reasonable to add one or two, perhaps along the lines of: editcatalogue/delete_items editcatalogue/delete_all_items Regards, Galen -- Galen Charlton Manager of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc at esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgkriegel at gmail.com Wed Jul 31 22:28:23 2013 From: bgkriegel at gmail.com (Bernardo Gonzalez Kriegel) Date: Wed, 31 Jul 2013 17:28:23 -0300 Subject: [Koha-devel] Permission vs System preference In-Reply-To: References: Message-ID: On Wed, Jul 31, 2013 at 4:43 PM, Galen Charlton wrote: > Hi, > > On Wed, Jul 31, 2013 at 12:33 PM, Heather Braum (NEKLS) wrote: > >> We are interested at some point in a development that would hide the "Edit >> items in batch"; "Delete items in batch"; and "Delete all items" options >> in the Edit menu of the detail.pl page through either a user permission >> or a system preference. It was suggested I contact the developers list to >> see what community developers think about this as a permission vs system >> preference. >> > > I'm in favor of permissions (and also a little confused) because ... two > of those menu options are already protected by permissions, specifically > tools/items_batchdel and tools/items_batchmod. > > There is no permission (other than the general permission that grants the > ability to edit items) guarding the 'Delete all items' permission, but I > think it would be reasonable to add one or two, perhaps along the lines of: > > editcatalogue/delete_items > editcatalogue/delete_all_items > > As Galen points a real solution is to have permissions, but as a workaround you could try to hide those options using intranetuserjs system preference, with this code $(document).ready(function(){ var itemlinks = $("a:contains('Edit items in batch'),a:contains('Delete items in a batch'),a:contains('Delete all items')"); $(itemlinks).hide(); }); As this value is stored in the database, you don't need to change anything after an upgrade, unless the text in the options change, then you will only need to update the syspref. Only a workaround. Regards, Bernardo -- Bernardo Gonzalez Kriegel bgkriegel at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: