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

[Bug 32118] New: Clarify expansion/embed modifiers
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '23

24 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32118 Bug ID: 32118 Summary: Clarify expansion/embed modifiers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com CC: tomascohen(a)gmail.com With bug 26635 we add a new additive function to the embed header options.. +av_expand.. this is a special case in that it's not just pulling in a related object, but also setting a flag to expand coded values and embed them within their own structure. We also have +relation_count.. to add a single field in a parent structure to just return the 'count' of a relation.. I think we should use :relation_count for this case? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 31582] New: With UseACQFrameworkForBiblioRecords 942$c doesn't display the itemtype pull-down
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '23

24 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31582 Bug ID: 31582 Summary: With UseACQFrameworkForBiblioRecords 942$c doesn't display the itemtype pull-down 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When using UseACQFrameworkForBiblioRecords, the itemtype pull down for 942$c doesn't show up correctly. To test: * Activate UseACQFrameworkForBiblioRecords in system preferences * Create an ACQ framework or edit the existing one, adding 942$c mapped to bibioitems.itemtype * Add a new order using the 'from a new empty record' option * Verify 942c shows, but as a freetext input field -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 28488] New: Javascript error in self-checkout (__ is not defined)
by bugzilla-daemon＠bugs.koha-community.org 24 Apr '23

24 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28488 Bug ID: 28488 Summary: Javascript error in self-checkout (__ is not defined) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org datatables_20.1200050.js:32 Uncaught ReferenceError: __ is not defined at datatables_20.1200050.js:32 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 29598] New: Add a preference for default borrower's notice language
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '23

23 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29598 Bug ID: 29598 Summary: Add a preference for default borrower's notice language 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: 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 Notice language for a new borrower via staff interface defaults to language of the staff interface user. In the OPAC self registration does not list the field and the value will be set to the database default called ... 'default'. Would be nice if we could make that more consistent. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 24167] New: We should support installation on Debian 10
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '23

23 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24167 Bug ID: 24167 Summary: We should support installation on Debian 10 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net Debian 10 has been stable for a little while now, and Debian 8 is nearing end of life. We really should be supporting Debian 10 now. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 31349] New: Add option to not update items.permenent_location when editing items.location
by bugzilla-daemon＠bugs.koha-community.org 23 Apr '23

23 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31349 Bug ID: 31349 Summary: Add option to not update items.permenent_location when editing items.location Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Generally, when one edits the shelving location (items.location) of an item, Koha also updates the permanent shelving location (items.permanent_location) to match. However, some libraries prefer to make it possible to edit the location without updating the permanent location. This allows one to set an item to a temporary location that automatically clears at checkin using the UpdateItemLocationOnCheckin syspref. That setup currently relies upon editing frameworks to make permanent location an editable field. That setup has proven fragile, as shown in bug 27837, bug 28832, bug 30909, and bug 31187. I suggest adding a more specific mechanism for this workflow in hopes that it will remain more stable and usable. In the item edit and item batch mod screens, we could put a checkbox next to the field for shelving location. The checkbox is labeled "Update permanent shelving location" and is checked by default. If one un-checks it, that edit will only update shelving location, not permanent location. The checkbox could be hidden with CSS if one doesn't want to use this feature. Or, if folks prefer, we could create a system preference to show/hide it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 30949] New: Error 500 in z3950_search.pl
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30949 Bug ID: 30949 Summary: Error 500 in z3950_search.pl Change sponsored?: --- Product: Koha Version: 22.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: egpetridis(a)yahoo.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 135974 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=135974&action=e… koha intranet error I wonder how may one debug errors 500 in z3950_search.pl, especially when searching against multiple targets. Searching for ISSN 1061-2688 in the following targets (among many others) host: webcat.lib.unc.edu port: 210 DB: innopac host: afton.lib.unc.edu port: 210 DB: INNOPAC I get the following error: Home Error 500 An error has occurred! Error 500 This message may have been caused by any of the following reasons: You made use of an external link to an item that is no longer available You followed an outdated link e.g. from a search engine or a bookmark You tried to access a page that needs authentication An internal link in the client is broken and the page does not exist What's next? Use top menu bar to navigate to another part of Koha. To report a broken link or any other issue, please contact the Koha administrator. Send email Error logs to be uploaded. Please don't focus on the server mentioned in them, as I located the servers above in previous tries but decided to file a bug report on subsequent searches that produced said error. In different previous searches I've encountered the same problem while searching against targets host: NLS.ALMA.EXLIBRISGROUP.COM port: 210 DB: 44NLS_INST (https://www.nls.uk/catalogues/z39-50/) host: ELIBRARY.MEL.ORG port: 210 DB: INNOPAC for example. Again, these are merely the targets I had managed to narrow down in the past. I noticed that tag 915 is mentioned in the logs (...Field 915 must have at least one subfield...), whereas no such tag is defined in standard koha frameworks such as BKS and SER. Could this be the culprit, data that koha doesn't expect to receive? Those very targets work fine when queried for different books/magazines, so it must be something contained in specific results. The error may also have to do with the fact that all Z39.50 servers defined in my installation have "Del952.xsl,Del9LinksExcept952.xsl" in the "XSLT File(s) for transforming results" field. Both XSLT files are stock, as provided in a packages installation. Some 10 years ago I had made the same question, but got nowhere. https://lists.katipo.co.nz/public/koha/2012-August/033847.html -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 32180] New: ERM - Mandatory fields don't have the 'required' class on the label
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32180 Bug ID: 32180 Summary: ERM - Mandatory fields don't have the 'required' class on the label Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 32030 At least not all of them, it's inconsistent - https://snipboard.io/pIRQBl.jpg Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32030 [Bug 32030] Electronic resource management (ERM) -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 27188] New: Show current class in plugins home
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27188 Bug ID: 27188 Summary: Show current class in plugins home Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org In plugins home, when searching on a specific class, you see the table but no reminder which class is displayed. Only when there are no results you see it in message. I propose to show it in H1 title and remove it from no results message. Sort of what is asked in Bug 16391. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 31076] New: Bug 22605 breaks date of publication range search
by bugzilla-daemon＠bugs.koha-community.org 21 Apr '23

21 Apr '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31076 Bug ID: 31076 Summary: Bug 22605 breaks date of publication range search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com Bug 22605 changed in staff interface the date of publication limit : - $limit_yr = "yr,st-numeric=$params->{'limit-yr'}"; + $limit_yr = "yr,st-numeric:$params->{'limit-yr'}"; This breaks the range search on date of publication which is a special case in QueryBuilder : https://git.koha-community.org/Koha-community/Koha/src/commit/6c315c164dbcf… Maybe juste allow ":" or "=" : my ($date) = ( $l =~ /^yr,st-numeric[=:](.*)$/ ); -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 25