November 2022 - Koha-bugs - lists.koha-community.org

[Bug 30493] New: Pending archived suggestions appear on intranet home page
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30493 Bug ID: 30493 Summary: Pending archived suggestions appear on intranet home page 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: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org If suggestions are archived before their status is changed to something other than "Pending", they still appear on the intranet home page and the acquisitions home page as suggestions to be managed. 1. Go to Acquisitions > Suggestions 2. Click on New purchase suggestion 3. Fill in the form (title only is fine) 4. Click on Submit your suggestion 5. Go to the home page (click the Koha logo) --> Notice it says that there is 1 pending suggestion 6. Go to Acquisitions --> Notice it says that there is 1 pending suggestion 7. Go to Suggestions 8. Click on the up arrow to the right of the Edit button and choose Archive --> There are no more pending suggestions 9. Go to the home page (click the Koha logo) --> Notice it says that there is 1 pending suggestion 10. Go to Acquisitions --> Notice it says that there is 1 pending suggestion -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 30715] New: Terminology: Logs should use should use staff interface and not intranet for the inrerface
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30715 Bug ID: 30715 Summary: Terminology: Logs should use should use staff interface and not intranet for the inrerface Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Transaction logs Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org When logs are enabled and an action is performed in the staff interface, it is displayed in the log interface column as "Intranet". This should be displayed as "Staff interface", as per the terminology guidelines: https://wiki.koha-community.org/wiki/Terminology#I To reproduce: 1. Any action logged by the staff interface should show this in the log viewer. 2. Example: . Enable logs for cataloging (enabled by default in koha-testing-docker) (CataloguingLog system preference). . For a record, change the shelving location for any item to something else. . Check the logs (Tools > Additional tools > Log viewer then Submit). . The interface column shows that the change was made in the "Intranet". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 30372] New: Patron self registration: Extended patron attributes are emptied on submit when mandatory field isn't filled in
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30372 Bug ID: 30372 Summary: Patron self registration: Extended patron attributes are emptied on submit when mandatory field isn't filled in Change sponsored?: --- Product: Koha Version: master 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 Testing bug 30120 I noticed that when you lave a mandatory extended patron attribute (or possibly another mandatory field) empty, all values already entered in extended attributes will be removed when clicking submit. To test: - Activate patron self registration without email verification - Create several patron attributes as visible and editable in the OPAC, make one mandatory - Register as a new patron from the OPAC - Fill in all required fields but the extended attribute - Submit - Verify that the contents of the other extended attribute fields have been removed and you are forced to re-enter -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 27198] New: Sync marc21-retrieval-info-auth-dom.xml with retrieval-info-auth-dom.xml
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27198 Bug ID: 27198 Summary: Sync marc21-retrieval-info-auth-dom.xml with retrieval-info-auth-dom.xml Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au ./debian/templates/marc21-retrieval-info-auth-dom.xml is out-dated and should be synchronized with ./etc/zebradb/retrieval-info-auth-dom.xml The main issue is that the XML retrieval syntax is wrong which prevents a person from using the Zebra special retrieval elements documented at https://software.indexdata.com/zebra/doc/special-retrieval.html -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 25835] New: Include Overdue Report (under Circulation Module) as a Staff Permission
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25835 Bug ID: 25835 Summary: Include Overdue Report (under Circulation Module) as a Staff Permission Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently, when setting up permission for staff, the report for Overdue reports portion of the Circulation module, is only partially included in staff permission. There is a permission that allows staff to run the Overdue report )Execute overdue items report (overdues_report)) - but this does prohibit the Overdue report from displaying on circulation page, but the Overdue with Fines does display. It would more helpful, if this permission included both reports or add another permission to allow libraries to include/exclude this other report. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 28012] New: Error on Saving new numbering pattern
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28012 Bug ID: 28012 Summary: Error on Saving new numbering pattern 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: christian.stelzenmueller(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I got an error after klicking on the Save button for saving a new numbering pattern. 1. go to the serials module 2. click on manage numbering patterns in the left hand navigation 3. add a pattern 4. Fill in the fields 5. Filling in the Numbering formula field leads to an error after saving. Leaving the numbering formula field blank, no error occurs, but the new pattern won't be saved it seems First lines of error trace: C4::Serials::Numberpattern::AddSubscriptionNumberpattern(): DBI Exception: DBD::mysql::st execute failed: Incorrect integer value: '' for column `koha_christian8`.`subscription_numberpatterns`.`displayorder` at row 1 [for Statement "INSERT INTO subscription_numberpatterns(label,description,numberingmethod,displayorder,label1,label2,label3,add1,add2,add3,every1,every2,every3,setto1,setto2,setto3,whenmorethan1,whenmorethan2,whenmorethan3,numbering1,numbering2,numbering3) VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)" with ParamValues: 0="blablub", 1="blablubdescription", 2="{X}, H. {Y} {Z} ", 3="", 4="Jahr", 5="Jahrgang", 6="Heft", 7="1", 8="1", 9="1", 10="12", 11="6", 12="1", 13="1", 14="1", 15="1", 16="9999", 17="9999", 18="6", 19="", 20="", 21=""] at /kohadevbox/koha/serials/subscription-numberpatterns.pl line 62 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 31297] New: Cannot add new subscription patterns from edit subscription page
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31297 Bug ID: 31297 Summary: Cannot add new subscription patterns from edit subscription page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding a new subscription pattern from the edit subscription page, nothing happens when clicking on the bug. But we can see the following error from the API request: XHRGEThttp://localhost:8081/cgi-bin/koha/serials/create-numberpattern.pl?patternname=Test season with month&numberingmethod={X} {Y} {Z}&label1=Season&label2=Year&label3=Month&add1=1&add2=1&add3=1&every1=1&every2=4&every3=4&setto1=0&setto2=1&setto3=0&numbering1=season&numbering3=monthname&whenmorethan1=3&whenmorethan2=99999&whenmorethan3=11&locale=spa [HTTP/1.1 500 Internal Server Error 27ms] C4::Serials::Numberpattern::AddSubscriptionNumberpattern(): DBI Exception: DBD::mysql::st execute failed: Field 'description' doesn't have a default value at /kohadevbox/koha/serials/create-numberpattern.pl line 58 description is a field in the database, that can only be filled from the administration page for numbering patterns, but not from this screen. This has always been the case. Could this by a strict SQL error? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 25

[Bug 32312] New: Complete database column descriptions for serials module in guided reports
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32312 Bug ID: 32312 Summary: Complete database column descriptions for serials module in guided reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Depends on: 29695 There are entries missing for the statistics table. How to test: * Add a new guided report * Select module serials * Verify that statistics is missing some descriptions, only showing the database value Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29695 [Bug 29695] Centralize columns' descriptions -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 32305] New: Backround worker doesn't check jobs receive from rabbitmq are in 'new' state.
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32305 Bug ID: 32305 Summary: Backround worker doesn't check jobs receive from rabbitmq are in 'new' state. 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: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org How to reproduce : 1) stop rabbitmq and koha-worker services. 2) start koha-worker , without rabbitmq it's polling the database. 3) start rabbitmq, koha-worker is not connecting to it. 4) submit a job. A new row is add to background_jobs table and the job is enqueued in rabbitmq. 5) the job is processed by koha-worker from the database. 6) restart koha-worker, this time connection to rabbitmq succeeded 7) koha-worker receive job message from rabbitmq and rerun it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 67

[Bug 27153] New: ElasticSearch should search keywords apostrophe blind
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27153 Bug ID: 27153 Summary: ElasticSearch should search keywords apostrophe blind Change sponsored?: --- Product: Koha Version: 20.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.field(a)ptfs-europe.com We are often asked why keyword searches don't ignore apostrophes. If you searched for "carries war" on Google, the first hits that come up are for Carrie's War by Nina Bawden. If you do a keyword search in Koha for "carries war" you get 0 hits. If you search for "carrie's war" you will find copies of this book. Koha with ElasticSearch should search apostrophe-blind (ignore the apostrophe). This was a perennial problem with zebra. In zebra you had to change words-icu.xml to ignore apostrophes. We should deliver an ES index_config.yaml that handles this scenario. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 81