June 2017 - Koha-bugs - lists.koha-community.org

[Bug 16292] New: Allowtoomanyoverride - Don't allow does not give any message
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16292 Bug ID: 16292 Summary: Allowtoomanyoverride - Don't allow does not give any message Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Dear team, When trying to issue more than the limit of items it stops issuing books, but the koha does not show any message/warning - this happens when Allowtoomanyoverride is Don't allow. When Allowtoomanyoverride is allow, it gives me a warning message do you wan't to override or issue. I feel system should tell that the limit reached. If this is not a system issue and I missed some system settings, please help me in setting the system preferences correctly. Iam using koha 3.22.05. Regards Suresh Kumar -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 17105] New: Do not see checkouts in the table of circulation.pl
by bugzilla-daemon＠bugs.koha-community.org 20 Nov '19

20 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17105 Bug ID: 17105 Summary: Do not see checkouts in the table of circulation.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Saw this problem under 3.22 (but could probably have been master too): Circulation page lists a number of checkouts. But clicking Show checkouts does not list them in the table. What happened? This javascript error occurred: Sunday not defined. Comes from includes/calendar.inc. And should be a zero. (As value for the preference CalendarFirstDayOfWeek.) After toggling this preference a few times, I could not reproduce the problem anymore under 3.22 (Plack+memcache). Probably a cache problem somehow. Note that dbrev 3.21.00.015 moved the old value of Sunday to 0. Just leaving this note here some time for future troubleshooting. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 17131] New: Zebra index for Title is too broad
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '19

18 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17131 Bug ID: 17131 Summary: Zebra index for Title is too broad Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 54482 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=54482&action=ed… Test file One of the zebra index definitions in marc21/biblios/biblio-koha-indexdefs.xml for Title includes the entire 245 tag:  <index_data_field tag="245"> <target_index>Title:w</target_index> <target_index>Title:p</target_index> </index_data_field> Since 245$c can contain Author, this means that author names will show up in Title searches. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 18723] New: Dot not recognized as decimal separator
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18723 Bug ID: 18723 Summary: Dot not recognized as decimal separator Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org Since we work on 16.11, we can't use dot when we receive orders but only comma (for example : a price 11.25€ will be changed in 1125,00€ after receiving the order). It seems linked to syspref "Currencyformat" because the behaviour is different when we change it from FR to US format (a price 15,43€ will be changed in 15,430.00€). When we worked on 3.20 until this april, we could use both dot and comma when receiving books. This is quite disturbing for staff users because a dot is required when adding an order to a basket, whereas a comma must be used when receiving the book but there is no warning like it exist in the basket. I don't know if it's a similar problem to the "Bug 18186 - Amounts with decimal comma instead of decimal dot breaking payments" about the circulation module. We also work with plack, but even without it, we still have this bug. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 74

[Bug 17359] New: Patron import results use wrong encoding
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '19

15 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17359 Bug ID: 17359 Summary: Patron import results use wrong encoding Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: mirko(a)abunchofthings.net QA Contact: testopia(a)bugs.koha-community.org When using the patron import tool, the summary at the end uses wrong character encoding. Upload a csv with a few fields and include some ü ö ä. To trigger an error, not providing a surname in the file should work, or a non numeric cardnumber. You will see broken Umlauts on the results page. (The imported data is ok, only the summary is not) -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 15732] New: Remove accountno column from accountlines
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '19

07 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15732 Bug ID: 15732 Summary: Remove accountno column from accountlines Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org How that we have accountlines_id, accountno is superfluous. We should remove it. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 18587] New: LDAP: update_local is entirely untested!
by bugzilla-daemon＠bugs.koha-community.org 07 Nov '19

07 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18587 Bug ID: 18587 Summary: LDAP: update_local is entirely untested! Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P3 Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org, gmcharlt(a)gmail.com, hblancoca(a)gmail.com, katrin.fischer(a)bsz-bw.de, martin.renvoize(a)ptfs-europe.com, mtj(a)kohaaloha.com, oliver.bock(a)aei.mpg.de, tomascohen(a)gmail.com Depends on: 14625 The update_local routine inside C4/Auth_with_ldap.pm is entirely untested :(. Reading the code, there are assumptions within it that don't hold true either. For instance, it is assumed that the routine always returns 'cardnumber', when in fact, it can return 'undef' or an integer specifying the number of rows updated by the procedure.. which should only ever be '1'. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14625 [Bug 14625] LDAP: mapped ExtendedPatronAttributes cause error when updated on authentication -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 16580] New: Explain the link between the autoBarcode preference and the cataloging plugin
by bugzilla-daemon＠bugs.koha-community.org 02 Nov '19

02 Nov '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16580 Bug ID: 16580 Summary: Explain the link between the autoBarcode preference and the cataloging plugin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl If you have the 'barcode.pl' plugin enabled for the barcode field in your MARC framework, but the 'autoBarcode' preference is turned off, the plugin will appear to be active but won't do anything. I think there ought to be text explaining the connection, to be shown both on the system preference itself and when the barcode plugin is selected during framework editing. Or is there a time when one does something without the other? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 18001] New: LocalHoldsPriority can cause multiple holds queue lines for same hold request
by bugzilla-daemon＠bugs.koha-community.org 31 Oct '19

31 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18001 Bug ID: 18001 Summary: LocalHoldsPriority can cause multiple holds queue lines for same hold request Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If LocalHoldsPriority is enabled, and a record level request has more than one item that could fill that hold, there is a possibility that a holds queue row will be generated for the request for each of the available items! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 20

[Bug 18322] New: Add facets for ccode to zebra
by bugzilla-daemon＠bugs.koha-community.org 30 Oct '19

30 Oct '19

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18322 Bug ID: 18322 Summary: Add facets for ccode to zebra Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: brendan(a)bywatersolutions.com, jonathan.druart(a)bugs.koha-community.org, katrin.fischer(a)bsz-bw.de, marjorie.barry-vila(a)ccsr.qc.ca, nick(a)bywatersolutions.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 17169, 18068 Blocks: 18235 If we're going to add it for elasticsearch, it ought to also be there for zebra ;) Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17169 [Bug 17169] Add facets for ccode to elasticsearch https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18068 [Bug 18068] Elasticsearch (ES): Location and (home|holding)branch facets mixed https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18235 [Bug 18235] Elastic search - Configurable facets -- You are receiving this mail because: You are watching all bug changes.

1 52