May 2021 - Koha-bugs - lists.koha-community.org

[Bug 24512] New: Should be able to have 'hidden'/'administrative' branches
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '21

08 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24512 Bug ID: 24512 Summary: Should be able to have 'hidden'/'administrative' branches 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Some libraries have branches that are not for the public, or are used for statistics etc. It would be nice to be able to define a branch as 'hidden' in administration and make sure it is not shown in opac dropdowns for search etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 28360] New: Link to make article reqests should display on detail page when user is not logged in
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '21

08 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28360 Bug ID: 28360 Summary: Link to make article reqests should display on detail page when user is not logged in Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I feel like this is a possible regression as it still works from the result list. I the result list the link to make article requests is always displayed, triggering the login screen, when the user is not logged in yet. On the detail page this link has disappeared on the right side if the user is not logged in (tested it latest 20.11) -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 28022] New: MARC subfield 9 not honoring visibility
by bugzilla-daemon＠bugs.koha-community.org 08 Nov '21

08 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28022 Bug ID: 28022 Summary: MARC subfield 9 not honoring visibility Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It is not possible to hide eg field 600 (and several more) in the editor, because addbiblio.pl line 346 implements a special case (based on bug 2206, according to a code comment there): If there is a subfield '9' and a subfield 'a', and subfield 'a' has an 'authtypecode' set, a 'marc_value' is set, which seems to always force the display of the field (and subfield), even though none of the 'visibility' checkboxes (and esp not "Editor") are set. The special case seems to ignore 'visibility' / 'hidden' completely. I don't know enough about Koha/MARC internals to assess if this is intended behavior, but I would find it more sane if the condition would be changed to actually use the value of the Editor-checkbox. The only other way I found to actually disable / hide field 600 was to remove the authtypecode from 600.a, which seems a bit harsh. After reading more code in addbiblio.pl I see that this special case is implemented in several places. So I assume / fear this is intended behavior, and the correct "solution" is to in face remove the authtypecode? Greetings, Thomas Klausner -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 28143] New: @INC filled with duplicates of opachtdocs and intrahtdocs
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '21

06 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28143 Bug ID: 28143 Summary: @INC filled with duplicates of opachtdocs and intrahtdocs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Steps to reproduce: 1. Have a $KOHA_CONF with at least 2 'pluginsdir' entries. You need at least one plugin with a 'tool', 'report', or 'configure' method. This will be useful to trigger the loading of Koha::Plugins::Handler. The KitchenSink module is perfect for that. 2. Start starman with only 1 worker (not necessary but it's easier to reproduce the problem that way) 3. Load staff client home page multiple times 4. Run the plugin method of your choice 5. Go to the About page, you should see the template directories in "Perl @INC" The problem is located in C4::Templates::badtemplatecheck, which push 'opachtdocs' and 'intrahtdocs' config entries directly into the 'pluginsdir' key of global variable $context -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 28303] New: Having multiple pluginsdir causes plugin_upload to try to write to the opac-tmpl folder
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '21

06 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28303 Bug ID: 28303 Summary: Having multiple pluginsdir causes plugin_upload to try to write to the opac-tmpl folder Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: michael.hafen(a)washk12.org QA Contact: testopia(a)bugs.koha-community.org With multiple pluginsdir settings in koha-conf.xml, C4/Template::badtemplatecheck changes the config, causing plugins-upload to try to unpack plugins to the opac-tmpl folder which badtemplatecheck unshifts into the pluginsdir array in config. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 27823] New: List upcoming steps during installation process
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '21

05 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27823 Bug ID: 27823 Summary: List upcoming steps during installation process Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 117457 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=117457&action=e… Screenshot of the proposed change I think it would be nice for the user installing Koha to be able to see what the upcoming steps were. See attached. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 26326] New: Add Koha Objects for Record Import Matches
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '21

05 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26326 Bug ID: 26326 Summary: Add Koha Objects for Record Import Matches Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 47

[Bug 25883] New: Show transfer on checkin screen
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '21

05 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25883 Bug ID: 25883 Summary: Show transfer on checkin screen Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com When an item generates an automatic transfer at checkin, there's nothing on the checkin screen to indicate that the transfer has generated. Following bug 23129, the holding branch shows the library where the item was checked in, rather than the library the item is going to. That's a good an accurate change, but means we don't have any way to see the transfer. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 36

[Bug 28417] New: Authen::CAS::Client always loaded even in CAS in not in used
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '21

05 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28417 Bug ID: 28417 Summary: Authen::CAS::Client always loaded even in CAS in not in used Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart+koha(a)gmail.com Reporter: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Blocks: 28410 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28410 [Bug 28410] Reduce memory footprint -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 27375] New: Set YAML file settings in .editorconfig
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '21

05 Nov '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27375 Bug ID: 27375 Summary: Set YAML file settings in .editorconfig Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Developer documentation Assignee: koha-bugs(a)lists.koha-community.org Reporter: johanna.raisa(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org >From Bug 12545 >> It'd be usefull to have a .editorconfig [1] file, that enforces some of our >> coding guidelines, in the source tree top level. >> >> Those developers that have their editors configured to honour the file, will >> benefit. Those that wouldn't use it, won't get bothered by the addition. So, a >> harmless addition that would benefit those that are interested. >> >> There are plugins for several major editors: >> - Emacs >> - Vim >> - SublimeText >> - and so on... >> >> [1] http://editorconfig.org/ We have been using 2 space indentation and single quotes with YAML files. Editors which are using the .editorconfig file will change these when editing the files. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9