June 2025 - Koha-bugs - lists.koha-community.org

[Bug 33169] New: Improve vue breadcrubms and left-hand menu
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33169 Bug ID: 33169 Summary: Improve vue breadcrubms and left-hand menu Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: agustinmoyano(a)theke.io QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Jonathan made a great vue component in bug 32030 to build the breadcrumbs from vue-routes, but I believe it can be improved. With this implementation, I believe it will be a little cleaner to define the routes, and besides that, we can use the same definition to build the left-hand side menu. Now if you want to add a new option, there is only one place to modify (the routes definition) and everything else will be built around it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 75

[Bug 34990] New: Backgroundjob->enqueue does not send persistent header
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34990 Bug ID: 34990 Summary: Backgroundjob->enqueue does not send persistent header 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Restarting RabbitMQ will make us loose all pending messages (jobs) in the default or long_tasks queue. Although we have a database fallback, this might be a problem when e.g. replacing/restarting a container while the workers did not yet read all messages or were down already, and the restart would activate Rabbit first. Note that this scenario places RabbitMQ in the same container; it surely would be better to put it in its own container. But also in that scenario we can loose messages if we do not add a persistent flag. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 32395] New: Why do we send job's params to the broker
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32395 Bug ID: 32395 Summary: Why do we send job's params to the broker Change sponsored?: --- Product: Koha Version: unspecified 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: jonathan.druart+koha(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: dcook(a)prosentient.com.au, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)ptfs-europe.com, tomascohen(a)gmail.com We are: - Building the parameters - Insert a job and its parameters in DB - Send a message to the broken with the parameters - Retrieve the message from the worker - Process the job using the parameter from the broker Why don't we simply pass the job_id to the broker, then retrieve the parameters from the DB in the worker? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[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

[Bug 36875] SQL injection in additional content pages
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36875 Bug 36875 depends on bug 31383, which changed state. Bug 31383 Summary: Additional contents: We need a parent and child table https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31383 What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to main |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35153] New: Convert IntranetmainUserblock system preference to additional contents
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35153 Bug ID: 35153 Summary: Convert IntranetmainUserblock system preference to additional contents Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, testopia(a)bugs.koha-community.org Depends on: 31383, 35152 Blocks: 26050 Building on 22318, the IntranetmainUserblock system preference should be converted to an HTML customization option. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26050 [Bug 26050] [OMNIBUS] Convert system preferences to HTML customizations https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31383 [Bug 31383] Additional contents: We need a parent and child table https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35152 [Bug 35152] Convert RoutingListNote system preference to additional contents -- You are receiving this mail because: You are watching all bug changes.

1 25

[Bug 35136] New: Error during database update after Bug 31383
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35136 Bug ID: 35136 Summary: Error during database update after Bug 31383 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: aleisha(a)catalyst.net.nz, dcook(a)prosentient.com.au, jonathan.druart+koha(a)gmail.com, kyle(a)bywatersolutions.com, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)ptfs-europe.com, nick(a)bywatersolutions.com, oleonard(a)myacpl.org, tomascohen(a)gmail.com Depends on: 31383 I've run across a case where the database upgrade in Bug 31383 triggers an error. The error is: ERROR - {UNKNOWN}: Not a HASH reference at /kohadevbox/koha/installer/data/mysql/db_revs/230600041.pl line 130. at /kohadevbox/koha/C4/Installer.pm line 741 I noticed that the error didn't happen if I deleted the 'ISSUESLIP' notice before running the upgrade, and that the error only happened with my custom testing database, not the default Koha testing data. Comparing the contents of ISSUESLIP in my data and in the default, I see this difference: In my data: <p style="margin-bottom: 1px; margin-top: 1px"><<additional_contents.new>></p> In the default data: <p style="margin-bottom: 1px; margin-top: 1px"><<additional_contents.content>></p> I'm not sure where the difference comes in, or how common this case might be in the wild. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31383 [Bug 31383] Additional contents: We need a parent and child table -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 35063] New: Convert SelfCheckInMainUserBlock system preference to HTML customization
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35063 Bug ID: 35063 Summary: Convert SelfCheckInMainUserBlock system preference to HTML customization Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 26050 Building on 22318, the SelfCheckInMainUserBlock system preference should be converted to an HTML customization option. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26050 [Bug 26050] [OMNIBUS] Convert system preferences to HTML customizations -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 34894] New: Convert OpacSuppressionMessage system preference to HTML customization
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34894 Bug ID: 34894 Summary: Convert OpacSuppressionMessage system preference to HTML customization Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: testopia(a)bugs.koha-community.org Blocks: 26050 Building on 22318, the OpacSuppressionMessage system preference should be converted to an HTML customization option. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26050 [Bug 26050] [OMNIBUS] Convert system preferences to HTML customizations -- You are receiving this mail because: You are watching all bug changes.

1 36