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

[Bug 21087] New: Patron's password is hashed twice when the object is saved
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '24

28 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21087 Bug ID: 21087 Summary: Patron's password is hashed twice when the object is saved Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20287 When a patron is edited (reading the code at least using patron batch modification), the password is lost. Prior to bug 20287 ModMember took the $hash of modification, and '****' was a trick to not update the password (when coming from memberentry). The same trick has been reused for the move of ModMember to Koha::Patron->store, but then the following code will modify the password of the patron: my $password = 'password'; $patron->password($password)->store; $patron->surname('xxx')->store; => User is not longer able to login with 'password' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20287 [Bug 20287] Move AddMember and ModMember to Koha::Patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 18213] New: Add language facets to Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '24

27 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18213 Bug ID: 18213 Summary: Add language facets to Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 23352] New: Set serial issue default values when creating a subscription in serials/subscription-add.pl
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '24

27 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23352 Bug ID: 23352 Summary: Set serial issue default values when creating a subscription in serials/subscription-add.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To speed up the process of receiving serial issues libraries should be able to set default serial issue values for the subscription when they create the subscription. Currently, it is possible for librarians to set default values for 952 MARC fields in the bibliographic frameworks but that would set blanket default values for all subscriptions. As different subscriptions are likely to have different 952 MARC field values it would be useful for libraries to set default values which are only applied to the serial issue items created for a specific subscription. The default values they should be able to set when creating the subscription (in serials/subscription-add.pl) are: * Collection code * Subscription full cost Then when a serial issue is received from the two above values the following 952 subfields will be pre-populated: * 952$8 Collection Code - Pulled in from default set in serials/subscription-add.pl * 952$b Current location - Set to the currently logged in library branch * 952$d Date acquired - This will be pre-populated upon page load rather than when you click on the text input field as is the current behaviour * 952$h Serial Enumeration/ chronology - This will be pre-populated from the subscription numbering pattern * 952$v Cost, replacement price - This will be pre-populated from the calculation of the subscription full cost/number of issues This would only leave the librarian to input 952$p (barcode) and 952$a (permanent location), speeding up the cataloguing process of receiving serials. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 82

[Bug 26352] New: Add plugin hooks to transform patron barcodes
by bugzilla-daemon＠bugs.koha-community.org 26 Mar '24

26 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26352 Bug ID: 26352 Summary: Add plugin hooks to transform patron barcodes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Moved from bug 25712 Some of our partners have unusual barcode requirements that have required us to transform scanned barcodes using javascript. This is not the most reliable method. It would make more sense to have Koha transform the barcodes on the backend using a plugin. We should add hooks to transform and generate new item and patron barcodes. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 61

[Bug 16654] New: The output from reports/cat_issues_top.pl is not proper CSV
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '24

25 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16654 Bug ID: 16654 Summary: The output from reports/cat_issues_top.pl is not proper CSV Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The output from reports/cat_issues_top.pl is *NOT* csv; it is DSV (delimiter separated values) with the option of using commas as delimiters... and the delimiters aren't properly escaped. To illustrate the point 1/ Check out an item whose title contains a comma. 2/ Go to Home [34m~@� Reports [34m~@� Most-circulated items 3/ Select a date range containing today's date 4/ Select the "To a file" radio button, and use comma (,) as the delimiter. 5/ Click Submit Open the file in the spreadsheet program of your choice. Note that the title containing the comma spans two columns, because it was not properly quoted. If the report is going to use CSV as a file extension, it should be exported using Text::CSV_XS, which properly handles CSV export. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 17216] New: Add a new table to store authorized value categories
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '24

22 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17216 Bug ID: 17216 Summary: Add a new table to store authorized value categories 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(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Blocks: 15799 The way we manage authorized values is not consistent: Some are present in the DB, others are not (see bug 15799 comment 4 for more details). Worse, most of the time the FK does not exist (and datatype is not consistent: varchar 32 vs 20, 16,...). To help cleaning up this area, a new table to store authorized value categories would be helpful. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15799 [Bug 15799] Move authorised values related code into Koha::AuthorisedValues - part 2 -- You are receiving this mail because: You are watching all bug changes.

1 148

[Bug 23969] New: Add library to public lists
by bugzilla-daemon＠bugs.koha-community.org 21 Mar '24

21 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23969 Bug ID: 23969 Summary: Add library to public lists Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: baselibrary.consortium(a)nhs.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We would like to add a column and sort by library name, or separate tabs for each library on the public lists on the OPAC. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 20630] New: An attempt at multitenancy with Mojolicious
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20630 Bug ID: 20630 Summary: An attempt at multitenancy with Mojolicious 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 Depends on: 20582 There seems to be some concerns about the capability for Koha to be multitenant in a persistent environment, in particular with Mojolicious. This bug will try to address those concerns. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20582 [Bug 20582] Turn Koha into a Mojolicious application -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 25228] New: Patron messaging preferences clearing if duplicate warning
by bugzilla-daemon＠bugs.koha-community.org 20 Mar '24

20 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25228 Bug ID: 25228 Summary: Patron messaging preferences clearing if duplicate warning Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Patrons Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 18595 Same as bug 5161 for messaging preferences. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18595 [Bug 18595] Move C4::Members::Messaging to Koha namespace -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 23540] New: Gender 'N' is not translatable
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '24

18 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23540 Bug ID: 23540 Summary: Gender 'N' is not translatable Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: pasi.kallinen(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org Patrons of type 'I' (institution) automatically get their sex/gender set to 'N' (which is short for "None"), but the 'N' is not translatable and actually shows up in the patron details page. Relevant code in memberentrygen.tt: [% IF ( I ) %]<input type="hidden" name="sex" value="N" />[% END %] The template code for showing the gender text should be unified into single included file, instead of spread over multiple places like: koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember.tt: [% IF ( patron.sex == 'F' ) %]Female[% ELSIF ( patron.sex == 'M' ) %]Male[% ELSE %][% patron.sex | html %][% END %] koha-tmpl/intranet-tmpl/prog/en/modules/members/moremember-brief.tt: [% IF ( patron.sex ) %]<li><span class="label">Gender:</span>[% IF ( patron.sex == 'F' ) %]Female[% ELSIF ( patron.sex == 'M' ) %]Male[% ELSE %][% patron.sex | html %][% END %]</li>[% END %] -- You are receiving this mail because: You are watching all bug changes.

1 2