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

[Bug 25887] New: Filtering funds by library resets to empty in library pull down
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25887 Bug ID: 25887 Summary: Filtering funds by library resets to empty in library pull down 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When filtering funds by library, the pull down for libraries resets to "empty" when the page is reloaded, although the filter criteria is visible in the URL. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 25852] New: If a layout is edited, the Layout Type will revert to Barcode
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25852 Bug ID: 25852 Summary: If a layout is edited, the Layout Type will revert to Barcode Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org If a label is set to have the layout as Barcode/Biblio - and edits are made, the layout type will change to just Barcode. To Recreate: 1. Create a layout type for Barcode/Biblio 2. Choose fields to print and size of font. 3. Save and Exit. 4. Test print this label and realize that font is too large. 5. Edit existing Layout and change font. 6. Save and then see that the layout type is now set to Barcode. This is extremely confusing and frustrating since one might not notice that the type has changed and prepared to print a sheet of labels and they are now wrong as they are only creating barcode labels instead of barcode/biblio labels. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 25599] New: Allow use of cataloguing placeholders when ACQ framework is used creating new record (UseACQFrameworkForBiblioRecords)
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25599 Bug ID: 25599 Summary: Allow use of cataloguing placeholders when ACQ framework is used creating new record (UseACQFrameworkForBiblioRecords) 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 There is a feature in the cataloguing where you can enter a placeholder in the default value of the framework that will then be replaced by a value on editing the record. At the moment we support: <<DD>> - 2 digit day of month <<MM>> - 2 digit number of month <<YYYY>> - 4 digit year <<USER>> - user adding the record And bug 24134 intends to add another useful one: <<YY>>. We should support this functionality when the ACQ framework is used within the cataloguing module as it can be helpful to set things like the date in 008 correctly. To test: - modify the default value for 008@ or another subfield in the ACQ framework using one or more of the placeholders above - activate UseACQFrameworkForBiblioRecords - create a basket - create an order from a new record - verify the values have not been replaced - create a new record from the ACQ framework in the normal editor - verify it works well there and values are replaced -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 25982] New: OPAC shelves RSS link output is html not xml
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '20

20 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25982 Bug ID: 25982 Summary: OPAC shelves RSS link output is html not xml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: didier.gautheron(a)biblibre.com Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Unlike opac-search.pl opac-shelves.pl output header is text/html not text/xml and it seems to confuse some RSS readers. cf 2009 git commit b04f432857617c6a7b3333863e34420103321ea1 for opac-search Test plan: 1) have books entered 2) log in create a list 3) add books to list 4) display list in OPAC 5) click the RSS link button. -- output is displayed as html text 6) apply patch 7) repeat steps 4&5 -- output is displayed as xml tree -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 15436] MARC21: Use semicolon between series name and volume information
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '20

19 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15436 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david(a)davidnind.com --- Comment #13 from David Nind <david(a)davidnind.com> --- Hi Katrin. I had a go at this, but don't feel confident enough to sign it off given my limited understanding of MARC21 nuances! Things I noticed: 1. For Scéla mucce Meic Dathó, (mentioned in comment 9): after the patch it displays as Mediaeval and modern Irish series ; vol. VI | <== there is a | and no . after the VI 2. For Scarlet and black (also mentioned in comment 9): I noticed no change after the patch was applied 3. For the example in the test plan: that displayed as expected (First series | Second series ; 1 | Third series ; 1) David Nind -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25499] New: Fund code column is empty when closing a budget
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '20

19 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25499 Bug ID: 25499 Summary: Fund code column is empty when closing a budget Change sponsored?: --- Product: Koha Version: unspecified 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 closing a budget, the fund code is missing from the table showing the number of unreceived orders for each fund. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 24379] New: Borrowers Login Attempts is NULL
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '20

19 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24379 Bug ID: 24379 Summary: Borrowers Login Attempts is NULL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: nick(a)bywatersolutions.com Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When a patron registers for a new account, their loginattempt value is NULL and not zero. This is a change since 18.11. Since this value is NULL, a patron cannot reset their password due to this NULL value. -- You are receiving this mail because: You are watching all bug changes.

1 38

[Bug 14957] Write protecting MARC fields based on source of import
by bugzilla-daemon＠bugs.koha-community.org 19 Sep '20

19 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14957 David Nind <david(a)davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Patch doesn't apply --- Comment #220 from David Nind <david(a)davidnind.com> --- Patch(es) no longer apply on latest master 8-( : root@kohadevbox:koha(bz14957)$ git bz apply 14957 Bug 14957 - Write protecting MARC fields based on source of import 100052 - Bug 14957: DO NOT PUSH Schema changes 109955 - Bug 14957: Merge rules system for merging of MARC records 109956 - Bug 14957: Make preset labels translatable 109957 - Bug 14957: Adjust paging option for new version of datatables 109958 - Bug 14957: Fix rule javascript validation issue 109959 - Bug 14957: Change YUI layout to to Boostrap 109960 - Bug 14957: Remove prefetch of removed relationship 109961 - Bug 14957: Add icons for confirmation dialog and set preset based on actions configuration 109962 - Bug 14957: Replace filter value with label if one exists 109963 - Bug 14957: Remove usage of deleted Koha::MarcMergeRulesModules Apply? [(y)es, (n)o, (i)nteractive] y Applying: Bug 14957: DO NOT PUSH Schema changes Applying: Bug 14957: Merge rules system for merging of MARC records Using index info to reconstruct a base tree... M cataloguing/addbiblio.pl M installer/data/mysql/kohastructure.sql M installer/data/mysql/sysprefs.sql M koha-tmpl/intranet-tmpl/prog/en/includes/permissions.inc M koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/cataloguing.pref M koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tt M misc/migration_tools/bulkmarcimport.pl M tools/batch_record_modification.pl Falling back to patching base and 3-way merge... Auto-merging tools/batch_record_modification.pl Auto-merging misc/migration_tools/bulkmarcimport.pl Auto-merging koha-tmpl/intranet-tmpl/prog/en/modules/cataloguing/addbiblio.tt Auto-merging koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/cataloguing.pref CONFLICT (content): Merge conflict in koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/cataloguing.pref Auto-merging koha-tmpl/intranet-tmpl/prog/en/includes/permissions.inc Auto-merging installer/data/mysql/sysprefs.sql Auto-merging installer/data/mysql/kohastructure.sql Auto-merging cataloguing/addbiblio.pl error: Failed to merge in the changes. Patch failed at 0001 Bug 14957: Merge rules system for merging of MARC records The copy of the patch that failed is found in: .git/rebase-apply/patch When you have resolved this problem run "git bz apply --continue". If you would prefer to skip this patch, instead run "git bz apply --skip". To restore the original branch and stop patching run "git bz apply --abort". Patch left in /tmp/Bug-14957-Merge-rules-system-for-merging-of-MARC-r-KugWDA.patch -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 23086] New: Search for collection is broken
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '20

18 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23086 Bug ID: 23086 Summary: Search for collection is broken Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de Target Milestone: --- We have seen this issue in a 17.11 installation, but not in a newer 18.11. I believe that Zebra version and using/not using ICU might play a role here. When looking into it, we were able to fix the issue removing the lines adding quotes to the search in Search.pm: http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/Search.pm;h=41… The quotes appear to be the issue, as a simple search using mc-ccode: without quotes works. This problem has also been reported on the mailing list: https://lists.katipo.co.nz/pipermail/koha/2019-June/053081.html Setting to major as this effects a major feature in the OPAC. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 33

[Bug 10569] Course reserves do not show on OPAC detail page if OpacSeparateHoldings is in effect
by bugzilla-daemon＠bugs.koha-community.org 18 Sep '20

18 Sep '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10569 --- Comment #2 from Rogan Hamby <rogan.hamby(a)gmail.com> --- all right, I had a brain failure and didn't grok that the ticket was about the course reserves column in the details column, I can confirm the current behavior is still as reported -- You are receiving this mail because: You are watching all bug changes.

1 0