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

[Bug 17979] New: Fatal error when searching from addbooks.pl due to ISBN flaw
by bugzilla-daemon＠bugs.koha-community.org 23 Nov '21

23 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17979 Bug ID: 17979 Summary: Fatal error when searching from addbooks.pl due to ISBN flaw Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org If you're doing a "Cataloging Search" from /cgi-bin/koha/cataloguing/addbooks.pl, and you type in "1st to die", you'll see the following: DBD::mysql::st execute failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '' at line 5 at /<koha>/lib/C4/Breeding.pm line 107 The reason is that the string is 10 characters long and contains a digit, so Koha thinks it's an ISBN. But when it tries to normalize it, it fails, and instead Koha generates no data for the WHERE clause and then the SQL statement fails because it contains a WHERE without the actual clause. The code: if ($query) { # fill isbn or title, depending on what has been entered #u must do check on isbn because u can find number in beginning of title #check is on isbn legnth 13 for new isbn and 10 for old isbn my ( $title, $isbn ); if ($query=~/\d/) { my $clean_query = $query; $clean_query =~ s/-//g; # remove hyphens my $querylength = length $clean_query; if ( $querylength == 13 || $querylength == 10 ) { $isbn = $query; } } if (!$isbn) { $title = $query; } ( $countbr, @resultsbr ) = BreedingSearch( $title, $isbn ); } -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 17423] New: patronimage.pl permission is too restrictive
by bugzilla-daemon＠bugs.koha-community.org 22 Nov '21

22 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17423 Bug ID: 17423 Summary: patronimage.pl permission is too restrictive Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 14566 added the permission "borrowers" on patronimage.pl. This perm is too restrictive because circulation pages also uses this page. I propose to simply use "catalogue" perm. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 16885] New: koha-stop-zebra should be more sure of stopping zebrasrv
by bugzilla-daemon＠bugs.koha-community.org 18 Nov '21

18 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885 Bug ID: 16885 Summary: koha-stop-zebra should be more sure of stopping zebrasrv Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The koha-stop-zebra command can finish without ensuring that zebrasrv is actually stopped. In particular, if there is an active query running when daemon --stop is run, the following state of affairs will occur until the query finishes or times out: - the child zebrasrv processing the query continues to run - the parent zebrasrv process becomes a zombie - the daemon(1) process continues to run -- and doesn't delete the lock file until the children go away. This is particularly problematic when a koha-stop-zebra is followed by a koha-start-zebra in quick succession, as happens during a logrotate. This is because while zebrasrv is in the half-stopped, half-started stop, the lock file still exists... and koha-start-zebra will see it and believe that zebrasrv is still running. When the query holding the child zebrasrv process finishes, the instance is left with no running Zebra. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 17981] New: Add the ability to preview generated notice templates
by bugzilla-daemon＠bugs.koha-community.org 16 Nov '21

16 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17981 Bug ID: 17981 Summary: Add the ability to preview generated notice templates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Notices Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 17961 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17961 [Bug 17961] TT syntax for notices - Prove we have an equivalent for our historical custom syntax -- You are receiving this mail because: You are watching all bug changes.

1 96

[Bug 16872] New: You should not be allowed to deleted a record with open orders attached
by bugzilla-daemon＠bugs.koha-community.org 15 Nov '21

15 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16872 Bug ID: 16872 Summary: You should not be allowed to deleted a record with open orders attached Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 10869 and Bug 10758 try to deal with the fallout from deleting a record with an order attached. I think, rather than fixing the order end we should prevent the deletion of the record in the first place to avoid causing an issue. This case also affects EDI ordering as item cannot be received when a title has been deleted -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 17314] New: REST API: Add API route to create, list and delete a purchase suggestion
by bugzilla-daemon＠bugs.koha-community.org 11 Nov '21

11 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17314 Bug ID: 17314 Summary: REST API: Add API route to create, list and delete a purchase suggestion Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: mail(a)jkozlovsky.cz QA Contact: testopia(a)bugs.koha-community.org It would be nice to have an API for creating a purchase suggestion. It would be used for instance in VuFind. Proposed implementation: To create: POST /suggestions/{borrowernumber} Incoming data: { title (required) author copyrightdate isbn publishercode collectiontitle place itemtype patronreason note negcap } Outcoming data: 200 OK / 403 Forbidden / 409 Conflict (when already exists the proposal) { error status } To list: GET /suggestions/{borrowernumber} Outcoming data: list of suggestions To delete: DELETE /suggestions/{borrowernumber}/{suggestion_id} Outcoming data: 204 No Content (successful deletion) / 403 Forbidden / 404 Not Found -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 135

[Bug 16467] New: Discharge requests pending count should appear on patrons home page
by bugzilla-daemon＠bugs.koha-community.org 10 Nov '21

10 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16467 Bug ID: 16467 Summary: Discharge requests pending count should appear on patrons home page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently the "Discharge requests pending" count appears only on the staff client home page. Like the count of patrons requesting modification, the discharge request count should also appear on the patrons home page (members-home.pl). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 16446] New: Allow librarians to add borrowers to lists by borrowernumber or cardnumber
by bugzilla-daemon＠bugs.koha-community.org 22 Oct '21

22 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16446 Bug ID: 16446 Summary: Allow librarians to add borrowers to lists by borrowernumber or cardnumber Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: gmcharlt(a)gmail.com Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be nice to be able to add borrowers to lists based on a supplied list of cardnumbers or borrowernumbers (that they could get from a report, for example). -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 17328] New: Koha fixes for Mysql 5.7
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '21

19 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17328 Bug ID: 17328 Summary: Koha fixes for Mysql 5.7 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I'm accruing many little issues. while running the code. I'll put the patches in, at least to document them. If the powers-that-be decide to fix in differently, all the same to me. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 15883] New: Upgrade jQuery from v1.7.2 in the staff client
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '21

15 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15883 Bug ID: 15883 Summary: Upgrade jQuery from v1.7.2 in the staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 14546 In order to upgrade Bootstrap in the staff client we first need to upgrade jQuery. After discussing it some in IRC (http://irc.koha-community.org/koha/2016-02-22#i_1791968) this is the plan I'm working on right now: An initial patch will start by adding the basis for upgrades: 1. Add a new version of doc-head-close.inc which includes new version of jQuery and jQueryUI. That include file will be named doc-head-close-jquery.1.12.0.inc to reflect the version of jQuery it uses. 2. Add the 1.12.0 version of jQuery, naming the file jquery-1.12.0.min.js 3. Add the latest version of jQueryUI, 1.11.4, naming the files jquery-ui-1.11.4.js and jquery-ui-1.11.4.min.css. Subsequent patches can take a page-by-page approach to the upgrade, dropping in the new include file and making any upgrades necessary to Javascript on that page. As compatibility issues are discovered, affected JS files can be re-created with updated file names to reflect the jQuery version, as in "basket-jquery-1.12.0.js" Disadvantages to this method: 1. It's possible some patches will have to touch both doc-head-close.inc and doc-head-close-jquery.1.12.0.inc. However that file changes fairly seldom. 2. git history getting lost between files. Can it be done so that the new include file keeps the history of doc-head-close.inc and doc-head-close.inc is created as if it is the new file? Eventually it could be removed. I would like to hear opinions and suggestions about this. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14546 [Bug 14546] Make staff client use Bootstrap -- You are receiving this mail because: You are watching all bug changes.

1 51