January 2024 - Koha-bugs - lists.koha-community.org

[Bug 9567] Favorite reports per user
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9567 --- Comment #7 from Christopher Brannon <cbrannon(a)cdalibrary.org> --- (In reply to Cab Vinton from comment #2) > Here's a temporary workaround -- Use MySQL's comment syntax & a unique > string within the body of the report to identify favorite reports (initials, > passphrase, etc.) > > For example: > > /* JTG */ > > /* JTG FMV */ > > /* rugbytuna */ One major reason this doesn't work well is that it requires either everyone to have editing capabilities to mark a report as their favorite, or some poor editor person has to be the schmuck to do it for them. This work around works for me, but not for everyone else. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35680] New: YAML system preferences cause error if syspref data is not YAML string
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '24

03 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35680 Bug ID: 35680 Summary: YAML system preferences cause error if syspref data is not YAML string 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org If a YAML preference has a string instead of the expected format, it'll cause an error - tested with RisExportAdditionalFields and ILLModuleDisclaimerByType but I'm sure others may cause this too. To reproduce: 1) Add 'string' to RisExportAdditionalFields sys pref 2) Visit RIS export link: /cgi-bin/koha/opac-export.pl?op=export&bib=262&format=ris 3) Notice the error Can't use string ("string") as a HASH ref while "strict refs" in use at /kohadevbox/koha/C4/Ris.pm line 132 Not critical, but ideally an error like this should not happen in the event that a system preference has wrong data in it. Adding bug 33431 as "See also" even though it's not the cause of the issue - as the test plans info there may also help here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 33640] New: Adding new item group from item additem.pl does nothing
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33640 Bug ID: 33640 Summary: Adding new item group from item additem.pl does nothing 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: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl To recreate: 1 - Browse to details page for a record 2 - Create or ensure the record has item group(s) 3 - Click New->New item 4. At the bottom of the page in the under Add to item group click the 'Options:' dropdown and select 'Create new item group'. 5. Add a name and click add item. 6. No item group is created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 19616] New: Formatted Contents Note (Marc 21 505), subfield g isn' t visible in the OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19616 Bug ID: 19616 Summary: Formatted Contents Note (Marc 21 505), subfield g isn't visible in the OPAC Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: verolencinas(a)yahoo.com.ar QA Contact: testopia(a)bugs.koha-community.org The 505 field in Marc 21, Formatted Contents Note, includes subfield g "Miscellaneous information". According to the Marc 21 format for bibliographic data, it is used to record "volume, part, page numbering or other extent information such as dates". If you use it in Koha, this information isn't visible in the OPAC. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 35675] New: Marc 505 extra punctuation at the end of the data
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35675 Bug ID: 35675 Summary: Marc 505 extra punctuation at the end of the data 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: iming(a)rosewoodfarm.com.au QA Contact: testopia(a)bugs.koha-community.org Created attachment 160379 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=160379&action=e… Screen example with a red circle Extra punctuation appended to the end of Marc 505 tag. This appears on the staff catalogue and OPAC. See screenshot attached. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 29905] New: Superlibrarians should be able to delete any patron messages
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29905 Bug ID: 29905 Summary: Superlibrarians should be able to delete any patron messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com Superlibrarians are generally exempted from branch limits, they should be able to delete a message on a patron account left by any library regardless of AllowAllMessageDeletion syspref setting -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 35679] New: dateofbirthrequired column from categories table should be renamed
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35679 Bug ID: 35679 Summary: dateofbirthrequired column from categories table should be renamed 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: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org git grep dateofbirthrequired The column dateofbirthrequired in the categories table has a confusing name. It sort of implies a boolean (i.e. whether date of birth is required or not), but it's actually utilized as a lower age limit check in the business logic. The column's comment states "the minimum age required for the patron category" which is how the data in this column is utilized. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25467] New: Improve performance of ViewPolicy filter
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25467 Bug ID: 25467 Summary: Improve performance of ViewPolicy filter 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 Rather than looping through every field of every record, it might be better to determine which fields must be hidden, then deal only with those? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 34686] New: reserves_id should be linked in tmp_holdsqueue
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34686 Bug ID: 34686 Summary: reserves_id should be linked in tmp_holdsqueue 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: michaela.sieber(a)kit.edu QA Contact: testopia(a)bugs.koha-community.org It would be helpful to have the reserves_id linked in the tmp_holdsqueue lines -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 24261] New: Google openID Authethication drops requested url
by bugzilla-daemon＠bugs.koha-community.org 02 Jan '24

02 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24261 Bug ID: 24261 Summary: Google openID Authethication drops requested url Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Authentication Assignee: koha-bugs(a)lists.koha-community.org Reporter: mihai.bojonca(a)tcmi.edu QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Hi everyone, i think this is a bug, we have setup access to catalog after login, we use 2 authentication methods, username and password or google openid, when a patron opens a direct link to an item and authenticates with username and password they get to the item itself however with openid they get redirected to the opac main page -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5