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

[Bug 28131] New: Allow subscriptions to be linked to existing orders
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '22

26 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28131 Bug ID: 28131 Summary: Allow subscriptions to be linked to existing orders Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment the workflow for subscription orders is a little "backwards": You have to create a subscription first, before you can create an order for it. It would be nice, if we could also do it the other way around: - Create an order for a serial record in your database, maybe using - When the first issue is delivered, use it to create your subscription and link it to the order This would not also help to streamline the acq process for new subscriptions, it would also be very handy to be able to link older orders to subscriptions that have been created before the feature was available in its current form. Or for migration data. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 26559] New: koha-create fails to upgrade database
by bugzilla-daemon＠bugs.koha-community.org 26 Sep '22

26 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26559 Bug ID: 26559 Summary: koha-create fails to upgrade database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com When I run koha-create, with DEFAULTSQL set to the path of an existing database dump, I get an error when it tries to upgrade the database: $ sudo koha-create --create-db --letsencrypt --configfile student.conf mykoha staff user password is '***' but keep that secret Upgrading database schema for mykoha DBI connect('database=koha_mykoha;host=localhost;port=3306','koha_mykoha',...) failed: Access denied for user 'koha_mykoha'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1517. DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: Access denied for user 'koha_mykoha'@'localhost' (using password: YES) at /usr/share/perl5/DBIx/Class/Storage/DBI.pm line 1520. at /usr/share/koha/lib/Koha/Database.pm line 116 After this, the Apache config file is created at /etc/apache2/sites-available/mykoha.conf, but the symlink at /etc/apache2/sites-enabled/mykoha.conf is not created. I can run koha-mysql and get access to the database, where the data from DEFAULTSQL has been loaded. If I comment out line 734 of koha-create: koha-upgrade-schema "$name" things run as expected, and the Apache config symlink is created. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 29310] New: Add timestamp, updated_on to aqbooksellers
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29310 Bug ID: 29310 Summary: Add timestamp, updated_on to aqbooksellers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org At the moment there is no way to tell when a vendor has been added or last updated. This would be helpful in some cases and we could mimick the fields we have on other tables here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 30752] New: Show hint on Library transfer limits admin page, when UseBranchTransferLimits is inactive
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30752 Bug ID: 30752 Summary: Show hint on Library transfer limits admin page, when UseBranchTransferLimits is inactive 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, michaela.sieber(a)kit.edu Library transfer rules won't be used, when UseBranchTransferLimits is not set to "Enforce". This can be easily missed. On the Transport cost matrix admin page, we show a nice hint about the feature not being active. We should add the same kind of hint for the library transfers. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 23301] New: Borrower messaging preferences lost when duplicating patron and changing category
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23301 Bug ID: 23301 Summary: Borrower messaging preferences lost when duplicating patron and changing category Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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 To test: - Create a patron and set their messaging preferences to something other than the defaults - Duplicate the patron - Note that their messaging preferences have been maintained - Before saving the new patron, change their category - Note that their messaging preferences reset to the default for their new category -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 24023] New: Add ability to create bundles of items
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24023 Bug ID: 24023 Summary: Add ability to create bundles of items Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This will add the ability to link items to a bibliographic record, making it a bundle of items. This bibliographic record can have item on its own, making it possible to reserve and check out bundles of items like a normal item. Items that are attached to a bundle will have their withdrawn status set, making them impossible to reserve or checkout individually. -- You are receiving this mail because: You are watching all bug changes.

1 45

[Bug 28364] New: koha-z3950-responder breaks because of log4perl.conf permissions
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28364 Bug ID: 28364 Summary: koha-z3950-responder breaks because of log4perl.conf permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com To reproduce: 1. Create a Koha instance: $ koha-create --create-db test 2. Initiate all the things 3. Enable and start the z3950 responder $ koha-z3950-responder --enable test $ koha-z3950-responder --start test 4. Try doing some search: $ yaz-client localhost:2100 => FAIL: you get: Connecting...OK. Sent initrequest. Target closed connection Z> quit See you later, alligator. => FAIL: No warning or anything on the logs 5. Stop the daemon $ koha-z3950-responder --stop test 6. Run it manually: $ PERL5LIB=/usr/share/koha/lib KOHA_CONF=/etc/koha/sites/test/koha-conf.xml /usr/bin/perl /usr/share/koha/bin/z3950_responder.pl -c /etc/koha/sites/test/z3950 -u test-koha -p /var/run/koha/test/z3950-responder.pid -d test-koha-z3950 7. Repeat the 4, on a separate terminal (no daemon mode this time) => FAIL: You get: Cannot open /etc/koha/sites/test/log4perl.conf (Permission denied) at /usr/share/perl5/Log/Log4perl/Config/BaseConfigurator.pm line 51. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 21375] New: NCIP service for Koha
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21375 Bug ID: 21375 Summary: NCIP service for Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: amitddng135(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org NCIP service for Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 30497] New: Constraint old_reserves_ibfk_4 should be SET NULL instead of CASCADE
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30497 Bug ID: 30497 Summary: Constraint old_reserves_ibfk_4 should be SET NULL instead of CASCADE Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org kohastructure defines it as SET NULL but this upgrade 'decided' differently: $DBversion = "3.23.00.055"; ALTER TABLE old_reserves ADD CONSTRAINT `old_reserves_ibfk_4` FOREIGN KEY (`itemtype`) REFERENCES `itemtypes` (`itemtype`) ON DELETE CASCADE ON UPDATE CASCADE; I think we should go for SET NULL here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 30490] New: Should deleting a parent itemtype be CASCADING?
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30490 Bug ID: 30490 Summary: Should deleting a parent itemtype be CASCADING? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This is a sync issue between schema and upgrades. MASTER structure: CONSTRAINT `itemtypes_ibfk_1` FOREIGN KEY (`parent_type`) REFERENCES `itemtypes` (`itemtype`) ON DELETE CASCADE ON UPDATE CASCADE $DBversion = '20.06.00.022'; ALTER TABLE itemtypes ADD CONSTRAINT itemtypes_ibfk_1 FOREIGN KEY (parent_type) REFERENCES itemtypes (itemtype) NOTE: When you do not add CASCADE, you fallback to RESTRICT ! Main question is now: Which is right? Should the delete be cascading or not? I would opt for RESTRICT here. A pragmatical choice too; deleting item types will normally not be done so much :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16