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

[Bug 19735] New: Move Perl deps definitions into a cpanfile
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '21

01 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19735 Bug ID: 19735 Summary: Move Perl deps definitions into a cpanfile Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org cpanfile is a format for describing CPAN dependencies for Perl applications. It is more concise - thus easier to read and maintain - than C4::Installer::PerlDependencies, and allows to describe requirements more accurately (using version ranges or features for instance). Additionally it can be read by tools such as cpanm or carton for an easy way to install dependencies on non-Debian-based systems. For more information on cpanfile, see http://search.cpan.org/~miyagawa/Module-CPANfile-1.1002/lib/cpanfile.pod -- You are receiving this mail because: You are watching all bug changes.

1 79

[Bug 24997] New: Test to ensure mappings.yaml is in the correct order
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '21

01 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24997 Bug ID: 24997 Summary: Test to ensure mappings.yaml is in the correct order 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: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org With the script introduced by bug 23204, we have the mappings.yaml that is generated using the data in DB. When the yaml file is modified, we must ensure that the script will generate exactly the same contain. A test needs to be written. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 16547] New: Can't place item level hold directly from search results screen
by bugzilla-daemon＠bugs.koha-community.org 01 Mar '21

01 Mar '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16547 Bug ID: 16547 Summary: Can't place item level hold directly from search results screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If you search for an item that brings up a list of results, checking the check box and clicking the 'Place Hold' button allows you to place a hold -- but after you've selected the patron, you can only place biblio level holds -- the section of the 'Confirm Holds' page which usually shows to allow item level holds is not displayed. This is most easily demonstrated on the bywater demo machine [usernam and password are both koha]. Search for Harry Potter: http://intranet.bywatersolutions.com/cgi-bin/koha/catalogue/search.pl?q=har… Click the check-box for the first search result ( Harry Potter and the Chamber of Secrets [videorecording] ... ) Click the 'Place hold' button, which will take you to the 'Confirm hold' screen (http://intranet.bywatersolutions.com/cgi-bin/koha/reserve/request.pl?biblio…) Enter card number 55. This takes you to a second 'Confirm hold' screen, showing a hold for 'Harry Potter and the Chamber of Secrets' for patron Bilbo Baggins (55)... no item information is viewable. (http://intranet.bywatersolutions.com/cgi-bin/koha/reserve/request.pl?biblio…) By contrast, If I start at http://intranet.bywatersolutions.com/cgi-bin/koha/catalogue/search.pl?q=har…, and click in to the first result page to see the details: http://intranet.bywatersolutions.com/cgi-bin/koha/catalogue/detail.pl?bibli… Then click 'place hold' from the details screen, I am taken to http://intranet.bywatersolutions.com/cgi-bin/koha/reserve/request.pl?biblio… Entering card number 55 at that point takes me to http://intranet.bywatersolutions.com/cgi-bin/koha/reserve/request.pl?biblio… ... but this time item level information *is* available, and an item level hold can be placed. Steps to replicate on your system: 1/ Search for an item with more than one search result 2/ Select an item, click 'Place hold' 3/ Enter a patron card number 4/ Note that item level holds are not available. 5/ Run the search again 6/ Click the title to see the detail page on the same bib. 7/ Enter the same patron card number 8/ Items now show on the page, and an item level hold can be placed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 21053] New: editing 008 field with a hash overwrites data
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '21

26 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21053 Bug ID: 21053 Summary: editing 008 field with a hash overwrites data Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bernard.scaife(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 76786 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=76786&action=ed… 008 screenshots Entering a hash (#) at any position in 008 field of a bib record causes all subsequent data in field to be overwritten with default values when record is saved. To reproduce: 1. Find and edit a bib record which has an 008 which differs from the default values for the MARC framework 2. Choose 008 helper 3. Add # in any position before the end of the field noting the current values of the data 4. Save record 5. Edit record and select 008 helper 6. Review characters after # and note changes See attached example screenshots -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 25735] New: Add distinct classes for clear history (.clearsh) links on OPAC
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '21

26 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25735 Bug ID: 25735 Summary: Add distinct classes for clear history (.clearsh) links on OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org As of 19.11 the OPAC navbar has a nice dropdown for logged in users that includes search history and a clearsh link which clears you history. clearsh also exists on the navbar for unauthenticated users. These two clearsh buttons have a very similar HTML structure and it makes it almost impossible to style the two links independently. Some libraries will want to style the background and text colors of each of these clearsh links independent of one another. It would be easy to give each one its own class to make this easy. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 24525] New: Hide SIP payment types from the Point of Sale page
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '21

25 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24525 Bug ID: 24525 Summary: Hide SIP payment types from the Point of Sale page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Bug 24339 adds the SIP2 payment_types to the default installed values for the payment type authorized values and also hides these values from appearing in the select boxes in paycollect.. however, the new Point of Sale screen was missed. This bug will take care of removing the SIP payment type from the payment type select options on the point of sale screen. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 25475] New: upload.pl should provide a "Copy link" option
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '21

25 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25475 Bug ID: 25475 Summary: upload.pl should provide a "Copy link" option Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org It's really difficult to use /cgi-bin/koha/tools/upload.pl to upload arbitrary files. If we had a "Copy link" button, it would make it easier to upload files and then use them in content/news sections. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 24036] New: UpdateNotForLoanStatusOnCheckin preference requires space after colon (specify in manual)
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '21

25 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24036 Bug ID: 24036 Summary: UpdateNotForLoanStatusOnCheckin preference requires space after colon (specify in manual) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org As stated in bug #17480, the system preference UpdateNotForLoanStatusOnCheckin requires a specific syntax in order to work. While there is discussion on a possible validation, it would be best to specify it in the manual in the mean time. Other sysprefs require YAML syntax, I haven't checked if the manual specifies it: - BibtexExportAdditionalFields - MarcFieldsToOrder - MarcItemFieldsToOrder - OpacHiddenItems - RisExportAdditionalFields - UpdateItemLocationOnCheckin - UpdateItemWhenLostFromHoldList -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 24108] New: Advanced Editor: Save .mrc save with a configurable value
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '21

25 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24108 Bug ID: 24108 Summary: Advanced Editor: Save .mrc save with a configurable value 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: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When saving a file as .mrc in the Advanced Editor, please add an identifier to the name of the file. Either: *Koha Number *Control Number (our preference, but we understand not everyone uses this) Bonus if it is configurable (default can be Koha Number) Currently the file is saved as "record.mrc" which does no one any good at all. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 71

[Bug 24037] New: Koha manual missing System Preference documentation for GDPR
by bugzilla-daemon＠bugs.koha-community.org 25 Feb '21

25 Feb '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24037 Bug ID: 24037 Summary: Koha manual missing System Preference documentation for GDPR Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org With the new system preference in 19.05 that works with GDPR, it was brought to our attention that the original system preference GDPR_policy is not in the 18.11 manual. It is in the 19.05 manual. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2