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

datatables management in TT
by Fridolyn SOMERS 20 Sep '13

20 Sep '13

Hie, Looking at datatables in templates, I notices there are two ways it is managed. In some pages of acquisition and in OPAC, the include datatables.inc (containing JS links and translatable strings) is used + the css : <link rel="stylesheet" type="text/css" href="[% themelang %]/css/datatables.css" /> [% INCLUDE 'datatables.inc' %] In more cases, this include is not used and datatables-strings.inc is used for translatable strings : <link rel="stylesheet" type="text/css" href="[% themelang %]/css/datatables.css" /> <script type="text/javascript" src="[% themelang %]/lib/jquery/plugins/jquery.dataTables.min.js"></script> [% INCLUDE 'datatables-strings.inc' %] <script type="text/javascript" src="[% themelang %]/js/datatables.js"> Wouldn't it be better to always use one include containing everything ? I think adding the CSS to existing datatables.inc can make the point. -- Fridolyn SOMERS Biblibre - Pôle support fridolyn.somers(a)biblibre.com

3 5

Advice about tax handling : bug 10461
by Mathieu Saby 20 Sep '13

20 Sep '13

Hello Lyon 3 made a patch for fixing tax handling in Acq home page. I want this patch, and I tried to test it, but all the preferences regarding taxes in Koha (list price / invoice price / include / does not include tax) are driving me crazy >:o I think the pach is wrong, but I am not sure... Could someone take a look (I made a detail test, you can look at my results and say if it is normal or not) and tell us whether the behavior after the patch is pushed is correct or not? Bug 10461 - tax not taken in to account in the acq budget summaries http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10461 Regards, M. Saby -- Mathieu Saby Service d'Informatique Documentaire Service Commun de la Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

1 0

KohaCon, arrivals & departures
by Paul Poulain 20 Sep '13

20 Sep '13

Hello, Chris has started a wiki page with arrivals & departures times for attendees. Feel free to add your name here: http://wiki.koha-community.org/wiki/Kohacon13/Arrivals -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

1 0

Search result
by kazi 19 Sep '13

19 Sep '13

Dear Community, I have got this trouble in koha-3.12.03 : Error: Can't call method "raw" on an undefined value at /usr/share/koha/lib/C4/Search.pm line 490. It was working nice when I installed, but after few weeks when I search I got that error. To solve this problem I upgraded it on koha 3.12.04.Still the problem remains. How it can be solved pls. With regards, Kazi -- View this message in context: http://koha.1045719.n5.nabble.com/Search-result-tp5768589.html Sent from the Koha-devel mailing list archive at Nabble.com.

2 1

Install Solr on debian wheezy for Koha
by Zeno Tajoli 19 Sep '13

19 Sep '13

Hi to all, I'm testing the install of Sorl on debian wheezy to use it for Koha. I want use packages as much as possible. Reading the docs and same links to drupal I decide to install those packages: sudo apt-get install openjdk-6-jre sudo apt-get install solr-common solr-jetty jetty It don't install the package 'javacc' as you can read here: https://drupal.org/node/967628 What is it your experience ? Do you think that the package 'javacc' is mandatory ? Cheers Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

2 1

RFC: authorities search autocomplete behaviour
by Tomas Cohen Arazi 19 Sep '13

19 Sep '13

Hi, a quick question, based on your experience: once the autocomplete feature in authorities search (cataloguing) retreived several results, the user is expected to click on one of them if it is what he/she was looking for. What should the behaviour be?: a) The clicked authority record should be left in the search field (current) so the user fills some other search fields and then clicks 'Search' button. b) The clicked authority record is shown below so the user can review it and choose it if applicable. c) The clicked authority record is directly chosen for linking and the pop up window closes. Thanks in advance. To+

2 1

How to create a message box with 3 buttons in Koha?
by Mathieu Saby 19 Sep '13

19 Sep '13

Hello I would like to work on Bug 7791 "Deleting basket should not delete all existing orders without warning" My idea : If there are non cancelled orders in the baskets, create a js popup alert giving the choice between : - Cancel (do NOT supress the basket) - Supress the basket and all the orders within - Supress the basket and all the orders within AND all the records if possible But I don't know the best way for creating a popup with 3 choices according to Koha guidelines (maybe jquery "dialog" box?). All examples I found are "confirm" boxes with only 2 buttons. Could you tell me how you would do that, or an example of a template with currently 3 buttons in a js popup ? Regards, Mathieu -- Mathieu Saby Service d'Informatique Documentaire Service Commun de la Documentation Université Rennes 2 Téléphone : 02 99 14 12 65 Courriel : mathieu.saby(a)univ-rennes2.fr

2 3

2013-09-23 Global bug squashing day - come join the fun!
by Magnus Enger 19 Sep '13

19 Sep '13

Dear Community! Some of the dates in Galen's RM proposal* are drawing dangerously near: 25 September 2013: feature slush** 3 October 2013: feature freeze 31 October 2013: string freeze 21 November 2013: release of 3.14.0 That's right, feature slush is just a few days away. And we have something of a queue of things that would be cool to have in 3.14: http://dashboard.koha-community.org/ So let's join forces and knock those numbers way down, on Monday 23rd: http://wiki.koha-community.org/wiki/2013-09-23_Global_bug_squashing_day That page should give you some clues about things you can do, but if you are unsure about how you can contribute, don't hesitate to jump on the IRC and ask for help: http://koha-community.org/get-involved/irc/ And rumour has it there will be a QA Sprint immediately the GBSD, but Katrin will have to fil in the details of that. Have fun! Magnus * See http://wiki.koha-community.org/wiki/Proposal_for_RM_3_14_gmcharlt ** Excerpt from the last general IRC meeting: <cait> gmcharlt: can you define feature slush a little? want to prevent any misunderstandings if possible :) <gmcharlt> cait: feature slush -- any new features that have hit passed QA by that date will be included in 3.14, assuming they don't raise signfiicant QA concerns on my part <gmcharlt> new features that have /not/ hit passed QA by feature slush are more liable to be left for the next release; if you want something that misses slush to make it in, you'll need to advocate for it <thd> Why does slush have the name slush? <gmcharlt> a partial freeze, of course

2 1

About "I'm just a bot" on bugzilla
by Paul Poulain 18 Sep '13

18 Sep '13

Hello koha-devel, I see that many patches are now automatically marked as "patch doesn't apply", automatically. If I'm not wrong, it's Chris C. that setup this bot. Useful job. 2 questions: * Has this been discussed/announced somewhere ? Not on koha-devel, somewhere else ? * the script is marking as "patch does not apply" patches have a conflict. Does it mark as such patches that only have an updatedatabase/sysprefs.sql conflict ? Those conflicts happends on every updatedatabase push, it would be a pain to have to rebase them on every push. 2 options to fix this: - push the new updatedb, that has been tested a lot, is passed QA for a while (bug 7167) - Prevent updatedatabase/sysprefs.sql conflicts from resulting in a "patch does not apply" status -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

2 2

Extended attributes, making them generic ?
by Paul Poulain 18 Sep '13

18 Sep '13

Hi Koha-devel, We've a customer that is asking for new -probably specific- fields in the subscription. For example, what they called: "subscription origin". I was wondering if a good way to do that would be to transform our "borrowers attributes" to become "extended attributes". Those extended attributes being managed as patron, subscription, acquisition,... attributes. What it means : * changing the table name ! (now, it's borrowers_attributes and borrowers_attribute_types) * removing foreign keys to borrowers table. * add a field "scope" (or similar name), that would be borrower, subscription, acquisition, ... * update all the code to handle this "scope" field. For example, borrower_attributes.borrowernumber would become "extended_attributes.externalid", pointing to the borrowernumber, the subscriptionid or the ordernumber. What do you think of the idea ? (I don't promize that, even if everybody says it's a wonderful idea, we will do it) -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

4 3