November 2024 - Koha-bugs - lists.koha-community.org

[Bug 29678] New: Can't use exteral URL for XSLT stylesheet
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29678 Bug ID: 29678 Summary: Can't use exteral URL for XSLT stylesheet Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org If I try to specify an external URL as an XSLT stylesheet it doesn't work. In the error logs I see messages like this: [2021/12/10 12:37:50] [WARN] XSLT::Base: Could not create file parser context for file "https://path/to/MARC21slim2intranetResults.xsl": No such file or directory at /kohadevbox/koha/Koha/XSLT/Base.pm line 330. I have verified that the .xsl file is accessible and that internal links (to MARC21slimUtils.xsl for instance) are valid too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 37223] New: Deleting the last item in a label batch needs to redirect to ?op=new
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37223 Bug ID: 37223 Summary: Deleting the last item in a label batch needs to redirect to ?op=new Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: phil(a)chetcolibrary.org QA Contact: testopia(a)bugs.koha-community.org When you delete the last item in a label batch, it effectively deletes the batch, but leaves you with an add form which still retains the batch_id. That means that if someone else creates a new batch before you add another item to "your" empty list, their batch will take that same batch_id, and when you add your item you will add it to their list. Steps to reproduce: 1. Cataloging - Label creator - New label batch 2. Add any item to the batch 3. In the list of items in the batch, click delete 4. Different browser, log in as a user at a different branch 5. Cataloging - Label creator - New label batch 6. Add any item to the batch 7. Back to the original browser, add any item to the "empty" batch 8. You now have a batch with two items in it when you only added one 9. Try to solve your confusion by going to Manage - label batches, maybe you added it to the wrong batch? Wups, no, there are no batches to manage, because now that batch you added an item to is owned by a different branch and you can't manage it to remove your accidental add. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 20581] New: Allow manual selection of custom ILL request statuses
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '25

13 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20581 Bug ID: 20581 Summary: Allow manual selection of custom ILL request statuses Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Currently the displayed status of any given ILL request is strictly prescribed by where it is in the workflow, as defined in the ILL module. While this gives an accurate indication of the current status of a request, it does not allow for any local variation in the displayed status, which can be limiting for the end user. This bug proposes adding the ability for the admin, via a syspref, to define a custom set of request statuses, which can be selected for display by the manager of an ILL request. These statuses work alongside the existing "workflow" status that an ILL request has and will, if selected, override *for display* the status of that request. This proposal will allow the ILL module to continue to strictly prescribe and manage the workflow of requests, but will also allow the end user some flexibility in the display of a given request's status -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 245

[Bug 27255] New: Authorized values does not allow you to provide a description for the category
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '25

12 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27255 Bug ID: 27255 Summary: Authorized values does not allow you to provide a description for the category Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I am noticing that AV has descriptions for the categories that come with Koha, but when you create a category, you are not allowed to provide a description. This is probably an oversight, but I think it would be great if we could add descriptions to new or existing categories. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 25999] New: Renewal due date not being honoured for items with holds
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '25

12 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25999 Bug ID: 25999 Summary: Renewal due date not being honoured for items with holds Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hc(a)interleaf.ie QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Bug 7088 added the ability to override renewals for items that have holds by adding the "AllowRenewalOnHoldOverride" syspref. When this sys. pref. is enabled and the "Override renewal restrictions" option is ticked on the checkouts table on a patron account and then an "on hold" item is selected in the renewal column the "On hold due date" box appears. This allows a renewal date to be applied to items with holds on them. For the most part, it works except in one scenario: A new date is selected in the "Renewal due date" box. This also populates the "On hold due date" box. The content in the "On hold due date" box is deleted. The selected items are renewed. The due date for the items with holds reverts to the parameters set for the patron category/item type combination in the fine and circulation rules. According to bug 7088 the item should be "renewed by falling back to the "Renewal due date" value if a value is not specified in the "On hold due date" input box"" Has anyone else had this issue? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 26135] New: MARCItemFieldsToOrder should use "location" rather than "loc"
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '25

12 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26135 Bug ID: 26135 Summary: MARCItemFieldsToOrder should use "location" rather than "loc" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com In the syspref description for MARCItemFieldsToOrder, one is instructed to enter database field names. However, the syspref requires one to use "LOC" rather than the field name "location" for shelving location. We should use "location" here. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 27492] New: Need ability to define hold pickup branches per patron category
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '25

12 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27492 Bug ID: 27492 Summary: Need ability to define hold pickup branches per patron category Change sponsored?: --- Product: Koha Version: 20.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: minna.kivinen(a)hamk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Need possibility to define hold pick up branches per patron category. Case example: our university library is open for all, but we have a lot self service hours when only faculty staff or students have access to library. Our main campus library has most service hours and we would like to define that patrons having category "other" could only choose main library as their pickup place. (although they are able to make a hold to all of our collection at any campus). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 29749] New: Clean up OpacStarRatings
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '25

11 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29749 Bug ID: 29749 Summary: Clean up OpacStarRatings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org While working on Bug 29280 I noticed there is some different code related to OpacStarRatings that could be consolidated a bit. OPAC pages that include OpacStarRatings are: -OPAC detail -OPAC user summary -OPAC reading history -OPAC results Sometimes a logged in user can interact with the ratings (OPAC detail, user summary, reading history ) Other times they cannot ( results ) A bit of cleanup here can make it easier to implement OPACStarRatigs elsewhere, like on the list displays in Bug 29280. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 26610] New: Add 'NULL' option to report value dropdowns
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '25

11 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26610 Bug ID: 26610 Summary: Add 'NULL' option to report value dropdowns Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Sometimes you may want to have a report optionally limit to an itemtype or branch etc. Sometimes you may want to pick NULL from that dropdown. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 33534] New: catalog New record An error has occurred! Error 500
by bugzilla-daemon＠bugs.koha-community.org 11 Feb '25

11 Feb '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33534 Bug ID: 33534 Summary: catalog New record An error has occurred! Error 500 Change sponsored?: --- Product: Koha Version: 22.11 Hardware: PC OS: Linux Status: NEW Severity: major Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: jenni.neenan(a)defence.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl I had just logged in to Koha ready to begin work. While cataloguing a new item, I tried to search for an item using Z39.50 protocol and received the following: An error has occurred! Error 500. I then tried to open a "New record" to add the item manually and received the same message. When I search for an item I can locate resources already added to our catalogue, however when I try to open the record to edit it I received again: An error has occurred! Error 500" However, I can access the new item feature on another PC. I am also able to conduct a search using Z39.50. How can I gain access to the full cataloguing module again on our master PC. Can someone help me to determine what has gone wrong and suggest a solution? Your assistance in this issue is much appreciated. Thank-you. Jenni -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10