October 2020 - Koha-bugs - lists.koha-community.org

[Bug 16941] New: Can not add new patron in staff client
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16941 Bug ID: 16941 Summary: Can not add new patron in staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It is no longer possible to add a patron in staff client. To reproduce: - Go to staff client Home > Patron - New patron - Choose a category and fill form, submit Result: Form reloads, patron data are not saved. Note: Duplicate or edit an existing patron works, adding a patron from OPAC works. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 18727] New: System preferences AcqItemSetSubfieldsWhen* loose part of values because of double quotes
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18727 Bug ID: 18727 Summary: System preferences AcqItemSetSubfieldsWhen* loose part of values because of double quotes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org The system preferences AcqItemSetSubfieldsWhenReceiptIsCancelled and AcqItemSetSubfieldsWhenReceived loose part of their values because of double quotes. To recreate: - Go to Home > Administration > System preferences , then tab Acquisitions - Enter values to both system preferences like proposed in the example (o=5|a="bar foo" and o=5|a="foo bar") - Save - Click on tab Acquisitions to reload - Result: Both preferences show a value of: o=5|a= (parts with double quotes are truncated) -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 23431] New: having Date of birth in PatronSelfModificationBorrowerUnwantedField causes DOB to be nullified
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23431 Bug ID: 23431 Summary: having Date of birth in PatronSelfModificationBorrowerUnwantedField causes DOB to be nullified Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Similar to bug 23151, if DOB is a field removed by PatronSelfModificationBorrowerUnwantedField, the date of birth gets nullified when the changes are submitted. To replicate: Turn on OPACPatronDetails put dateofbirth in PatronSelfModificationBorrowerUnwantedField Have a patron with a set date of birth Attempt any modification on that patron through the OPAC The date of birth will be one of the fields changed for that borrower when you check it in the OPAC. A work around is to remove dateofbirth from PatronSelfModificationBorrowerUnwantedField and hide the field from that form, if that is desired, with jquery; something like $("#opac-patron-update #memberentry_identity > ol:nth-child(2) > li:nth-child(3)").hide(); Note that it is .hide() and not .remove(). .remove() will cause the same behaviour as DOB being in PatronSelfModificationBorrowerUnwantedField. -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 22664] New: Link basket name and basket group name instead of just the number in order search results
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22664 Bug ID: 22664 Summary: Link basket name and basket group name instead of just the number in order search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Currently the link is only on the number, that can be hard to see and hard to click. I propose to link the name as well. Example: Basket name (1) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 21587] New: Patrons to notify on receiving doesn't work on new order creation, only on modification
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21587 Bug ID: 21587 Summary: Patrons to notify on receiving doesn't work on new order creation, only on modification 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: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Reproduced in 17.11 and the current master == Severity reasons == This is loss of information which is likely to get unnoticed. == Test plan == 1. have/create a active budget 2. have/create a fund 3. have/create a vendor with minimal info 4. create a basket with minimal info 5. add an order line to the basket Add a user in "To notify on receiving" 6. Modify the order 7. The patrons isn't here. This is the bug 8. Add a user in "To notify on receiving" 9. Save 10. Modify the order 11. The patron is here now -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 24494] New: 00-valid-xml.t shouldn't check node_modules
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24494 Bug ID: 24494 Summary: 00-valid-xml.t shouldn't check node_modules Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: victor(a)tuxayo.net QA Contact: testopia(a)bugs.koha-community.org node_modules exists when generating the CSS from the SCSS with yarn. And it contains invalid XML file. Which shouldn't be validated by Koha's test suite. ./node_modules/json-schema/draft-zyp-json-schema-03.xml ./node_modules/json-schema/draft-zyp-json-schema-04.xml -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 22576] New: OPAC password change text changes
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22576 Bug ID: 22576 Summary: OPAC password change text changes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- A borrower changing their password from the logged in password change functionality might see some awkward text messages, specifically: - "Return to your record" after changing the password, I propose "Return to my account" (since that's what the borrower probably wants to do). - "Submit changes" to change the password should be "Change password" just to be really clear about what is going to happen when the button is clicked. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 20623] New: PDF export of a basket group fails when an item as an itemtype is not in the itemtype table
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20623 Bug ID: 20623 Summary: PDF export of a basket group fails when an item as an itemtype is not in the itemtype table Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Does it matter? Yes, using authorized values like ccode to populate the itemtypes of the biblioitems (instead of the itemtype table) can lead to such data. Or importing records with invalid itemtype codes. Koha doesn't do enough checks to at least warn about these issues. == Reproduce == 1. have/create a budget 2. have/create a fund 3. have/create a vendor with minimal info 4. create a basket with minimal info 5. add a item to the basket 6. go to the basket. URL should be /cgi-bin/koha/acqui/basket.pl?basketno=XXXXX 7. close this basket 8. create a basket group with the basket - your vendor page => Basket groups - create basket group - (tick the "close this basket group" check box) 9. go to the basket group your vendor page => Basket groups => Closed 10. export as PDF, it should work, keep the page opened 11. find the itemtype code of item in the basket 12. delete it with the following SQL[1] (directly or use sql reports) replace with the relevant type code DELETE from itemtypes where itemtype = "BOOK"; 13. reexport the basket as PDF 14. It should fail (internal server error) [1] Or you can find a more realistic way to have a biblioitem whose itemtype is not in the itemtype table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 31

[Bug 20084] New: Patron card creator: layout: Industrial2of5 broken with "Invalid Characters" error
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20084 Bug ID: 20084 Summary: Patron card creator: layout: Industrial2of5 broken with "Invalid Characters" error Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org ## Reproduction ## This is an oversimplification of a full patron card setup used in production. 1. Create a batch with 1 patron 2. Create a layout and set the name "Print card number as barcode" "Barcode type:" to "Code 39" 3. Create a card template without filling anything 4. Export the batch using the layout and template 5. You should have a white page with a barcode This show that this setup isn't completely bogus (although Code 39 is the only type working) 6. Export the batch 7. You should have a white page with a barcode And no errors in the relevant log file 8. Layout: set "Barcode type:" to Industrial2of5 9. Export the batch 10. You should have a white page with no barcode And errors in the relevant log file "Invalid Characters" ## Going further ## COOP2of5 fails also with the same error TODO: Fix at the same time or open another bug -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 22616] New: updating error text messages
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22616 Bug ID: 22616 Summary: updating error text messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- There were multiple error messages in the staff client that had slightly awkward text, for example: "This patron does not exist" should be "Patron not found." "This $thing does not exist" should be "$thing not found." "Find another $thing?" should be "Return to search." "You are not allowed to see the information of this patron" should be "This account cannot view requested patron information" - this change makes it less personal, and might remind a person to check another account or to ask a supervisor if access is really required. I say this because it's not always the *person* who can't see a patron record, but the account that is currently logged in. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10