September 2018 - Koha-bugs - lists.koha-community.org

[Bug 11373] Add a "cash register" feature to the fine payment form
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11373 --- Comment #44 from Josef Moravec <josef.moravec(a)gmail.com> --- (In reply to Josef Moravec from comment #43) > (In reply to Blou from comment #41) > > Fixed the rest, but for the padding in the button, we'll need to find > > another solution since an <input> under a class="dialog message" will show > > like that. Not sure why the staff.css specifies that padding, but clearly > > having a confirm button in a message dialog is not the standard Koha way. > > That is because you should have icon on that button - try to add a > class="approve" to button. And add the icon itself like this: <i class="fa fa-fw fa-check"></i> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11373] Add a "cash register" feature to the fine payment form
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11373 Josef Moravec <josef.moravec(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia(a)bugs.koha-communit |josef.moravec(a)gmail.com |y.org | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11373] Add a "cash register" feature to the fine payment form
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11373 --- Comment #43 from Josef Moravec <josef.moravec(a)gmail.com> --- (In reply to Blou from comment #41) > Fixed the rest, but for the padding in the button, we'll need to find > another solution since an <input> under a class="dialog message" will show > like that. Not sure why the staff.css specifies that padding, but clearly > having a confirm button in a message dialog is not the standard Koha way. That is because you should have icon on that button - try to add a class="approve" to button. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 10060] Self Checkout module does not honour circ control
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10060 --- Comment #8 from Oliver Behnke <oliver.behnke(a)aei.mpg.de> --- (In reply to Katrin Fischer from comment #6) > Could using a separate self-check user for each branch solve the problem? Katrin, is this already possible or are you suggesting a new feature? I'd love to try that if it's already supported but I don't see how. Cheers -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 13640] Holds To Pull List includes items unreserveable items
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13640 --- Comment #9 from Magnus Enger <magnus(a)libriotech.no> --- I think I managed to take the 'Default holds policy by item type' into account in this report: SELECT min(reservedate) as l_reservedate, reserves.reserve_id, reserves.borrowernumber as borrowernumber, GROUP_CONCAT(DISTINCT items.holdingbranch ORDER BY items.itemnumber SEPARATOR '|') l_holdingbranch, reserves.biblionumber, reserves.branchcode as l_branch, reserves.itemnumber, items.holdingbranch, items.homebranch, GROUP_CONCAT(DISTINCT items.itype ORDER BY items.itemnumber SEPARATOR '|') l_item_type, GROUP_CONCAT(DISTINCT items.location ORDER BY items.itemnumber SEPARATOR '|') l_location, GROUP_CONCAT(DISTINCT items.itemcallnumber ORDER BY items.itemnumber SEPARATOR '<br/>') l_itemcallnumber, GROUP_CONCAT(DISTINCT items.enumchron ORDER BY items.itemnumber SEPARATOR '<br/>') l_enumchron, GROUP_CONCAT(DISTINCT items.copynumber ORDER BY items.itemnumber SEPARATOR '<br/>') l_copynumber, biblio.title, biblio.author, count(DISTINCT items.itemnumber) as icount, count(DISTINCT reserves.borrowernumber) as rcount, borrowers.firstname, borrowers.surname FROM reserves LEFT JOIN items ON items.biblionumber=reserves.biblionumber LEFT JOIN biblio ON reserves.biblionumber=biblio.biblionumber LEFT JOIN biblioitems ON biblio.biblionumber=biblioitems.biblionumber LEFT JOIN branchtransfers ON items.itemnumber=branchtransfers.itemnumber LEFT JOIN issues ON items.itemnumber=issues.itemnumber LEFT JOIN borrowers ON reserves.borrowernumber=borrowers.borrowernumber LEFT JOIN default_branch_item_rules ON items.itype=default_branch_item_rules.itemtype WHERE reserves.found IS NULL AND (reserves.itemnumber IS NULL OR reserves.itemnumber = items.itemnumber) AND items.itemnumber NOT IN (SELECT itemnumber FROM branchtransfers where datearrived IS NULL) AND items.itemnumber NOT IN (select itemnumber FROM reserves where found IS NOT NULL) AND issues.itemnumber IS NULL AND reserves.priority <> 0 AND reserves.suspend = 0 AND notforloan = 0 AND damaged = 0 AND itemlost = 0 AND withdrawn = 0 AND default_branch_item_rules.holdallowed != 0 GROUP BY reserves.biblionumber ORDER BY biblio.title What is changed compared to the "Holds to pull" SQL are these two lines: - LEFT JOIN default_branch_item_rules ON items.itype=default_branch_item_rules.itemtype - AND default_branch_item_rules.holdallowed != 0 However, default_branch_item_rules.holdallowed is of the "bit" type: http://schema.koha-community.org/18_05/tables/default_branch_item_rules.html I gotta confess I'm not familiar with that. Any special tricks to consider? When I look in the database, the value of that column is 0 or 2. Why not a boolean "0 or 1" value? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 20806] New: Column settings issues for holdshistory-table
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20806 Bug ID: 20806 Summary: Column settings issues for holdshistory-table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com There is 2 display issues with the table "Holds history" tab : - no change when modifying "Column settings > Patrons > (id=holdshistory-table)". I don't know if it is linked, but the <table id> on the tab is "table_holdshistory". - column "Item type" is always empty -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 20079] New: Display stack trace for development installations
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20079 Bug ID: 20079 Summary: Display stack trace for development installations Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Starman -E should be development instead of deployment for dev installs -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 13640] Holds To Pull List includes items unreserveable items
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13640 --- Comment #8 from Magnus Enger <magnus(a)libriotech.no> --- (In reply to Katrin Fischer from comment #6) > Hm, I don't think we need more configuration options - we need the report to > use the ones we have correctly. ...but I can't convince myself 100% that it will work. For example, inter library loans. When you start an ILL request you want to put a hold on the item, so there is a connection between the patron and the record/item. So if you use an itemtype for ILL that itemtype must be "holdable". At the same time the item will not be on loan, and so it will look like an "on the shelf hold" to the Holds to pull report, I think? Not sure I can see all the consequences, there might be ways to work around this, but perhaps something to consider when the time comes. BTW, this is the SQL that generates the holds to pull report: http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=circ/pendingreser… -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 12502] Add columns for note, order number and ISBN to late orders page
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12502 --- Comment #19 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- It would be great if this could be rebased. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 13640] Holds To Pull List includes items unreserveable items
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '18

21 Sep '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13640 --- Comment #7 from Magnus Enger <magnus(a)libriotech.no> --- Yeah, probably a good idea! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0