October 2023 - Koha-bugs - lists.koha-community.org

[Bug 33262] New: When an ordered record is deleted, we lose all information on what was ordered
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '24

18 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33262 Bug ID: 33262 Summary: When an ordered record is deleted, we lose all information on what was ordered Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: blocker 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 CC: clemens.tubach(a)kit.edu, michaela.sieber(a)kit.edu Blocks: 10758 I am moving this out from bug 10758 that was filed for the display issue. But that is actually only the symptom, while we are actually facing a data loss issue. Libraries need to be able to account for the money they spent even after the items and records have been removed from their collection. At the moment we lose the connection between order and bibliographic record when the record is deleted: -- -- Table structure for table `aqorders` -- DROP TABLE IF EXISTS `aqorders`; /*!40101 SET @saved_cs_client = @@character_set_client */; /*!40101 SET character_set_client = utf8 */; CREATE TABLE `aqorders` ( `ordernumber` int(11) NOT NULL AUTO_INCREMENT COMMENT 'primary key and unique identifier assigned by Koha to each line', `biblionumber` int(11) DEFAULT NULL COMMENT 'links the order to the biblio being ordered (biblio.biblionumber)', [...] CONSTRAINT `aqorders_ibfk_2` FOREIGN KEY (`biblionumber`) REFERENCES `biblio` (`biblionumber`) ON DELETE SET NULL ON UPDATE CASCADE, We do have the information about the deleted record and the items, but we need to preserve the link between order and deleted record in some way. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10758 [Bug 10758] Show bibliographic information of deleted records in acquisitions -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 47

[Bug 27679] New: The notices and slips management area should be moved to 'Administration'
by bugzilla-daemon＠bugs.koha-community.org 18 Mar '24

18 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27679 Bug ID: 27679 Summary: The notices and slips management area should be moved to 'Administration' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org As the title says, the Notics and Slips "tool" isn't really a tool.. it's a system administration task.. so it should live under administration. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 20657] New: Globally enable PRE_CHOMP and POST_CHOMP in Template Toolkit configuration
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '24

17 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20657 Bug ID: 20657 Summary: Globally enable PRE_CHOMP and POST_CHOMP in Template Toolkit configuration 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: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org As it currently stands, the HTML output by Template Toolkit includes whitespace anywhere there was a template tag. For example, this is a portion of the generated source of the staff client home page: 1 2 3 4 <!DOCTYPE html> 5  6 7 8 9 10 <html lang="en"> 11 <head> 12 13 <title>Koha staff client</title> Developer tools report: 26.69 KB / 5.83 KB transferred In contrast, this what the same content looks like with PRE_CHOMP and POST_CHOMP enabled: 1 <!DOCTYPE html> 2  3 <html lang="en"><head> 4 <title>Koha staff client</title> Developer tools report: 23.29 KB / 5.65 KB transferred In the samples I looked at this change did not make the HTML source significantly more difficult to read. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23

[Bug 19548] New: Search Result Second page not available
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '24

17 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19548 Bug ID: 19548 Summary: Search Result Second page not available Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: rainer.stowasser(a)zamg.ac.at QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl With the SRU/Z39.50 search using a quotation mark has the interesting effect that the first page of a result is displayed but a second page is not available. Looking at the pl source it seems that quotation marks are used and escaped for the first page but not for a second recall. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 31567] New: Onboarding stuck at "Cardnumber or Userid may already exist"
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '24

17 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31567 Bug ID: 31567 Summary: Onboarding stuck at "Cardnumber or Userid may already exist" Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I'm installing Koha 22.05.04-1 on Ubuntu 20.04.5, using the Debian packages. When I got to the "create a user" part of the onboarding I entered some made up user data and tried to save. This gave the message "The patron has not been created! Cardnumber or Userid may already exist." Tried with another cardnumber and userid, but got the same message. Checked the logs and saw this: ==> /var/log/koha/koha/intranet-error.log <== [Thu Sep 15 09:09:38.507240 2022] [cgi:error] [pid x] [client x.x.x.x:x] AH01215: {UNKNOWN}: Can't open /var/log/koha/koha/opac-error.log (Permission denied) at /usr/share/perl5/Log/Log4perl/Appender/File.pm line 151. at /usr/share/koha/lib/Koha/Patron.pm line 362: /usr/share/koha/intranet/cgi-bin/installer/onboarding.pl, referer: http://koha.example.com/cgi-bin/koha/installer/onboarding.pl Checked the permissions of the logs files: $ sudo ls -l /var/log/koha/koha/* -rw-r--r-- 1 koha-koha koha-koha 0 Sep 14 10:08 /var/log/koha/koha/indexer-error.log -rw-r--r-- 1 koha-koha koha-koha 3884632 Sep 15 08:43 /var/log/koha/koha/indexer-output.log -rw-r--r-- 1 root root 259998 Sep 15 09:09 /var/log/koha/koha/intranet-error.log -rw-r--r-- 1 root root 5465262 Sep 14 16:33 /var/log/koha/koha/opac-error.log -rw-rw-r-- 1 koha-koha koha-koha 0 Sep 15 06:25 /var/log/koha/koha/plack-api-error.log -rw-rw-r-- 1 koha-koha koha-koha 0 Sep 15 06:25 /var/log/koha/koha/plack-intranet-error.log -rw-rw-r-- 1 koha-koha koha-koha 0 Sep 15 06:25 /var/log/koha/koha/plack-opac-error.log -rw-rw-r-- 1 koha-koha koha-koha 0 Sep 15 06:25 /var/log/koha/koha/sip.log -rw-r--r-- 1 koha-koha koha-koha 0 Sep 14 10:08 /var/log/koha/koha/worker-error.log -rw-r--r-- 1 koha-koha koha-koha 258 Sep 14 10:08 /var/log/koha/koha/worker-output.log -rw-rw-r-- 1 koha-koha koha-koha 0 Sep 15 06:25 /var/log/koha/koha/z3950-error.log -rw-r--r-- 1 koha-koha koha-koha 0 Sep 14 10:08 /var/log/koha/koha/zebra-error.log -rw-r--r-- 1 koha-koha koha-koha 0 Sep 14 10:08 /var/log/koha/koha/zebra-output.log Changed the ownership of all logs: $ sudo chown koha-koha:koha-koha /var/log/koha/koha/* And now I could add the patron without any problems. Two problems here: - The ownership of the logs - The error message pointing in the wrong direction -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31729] New: Enable automatic filesystem refresh in Plack
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '24

15 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31729 Bug ID: 31729 Summary: Enable automatic filesystem refresh in Plack 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: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org this patch adds an automatic filesystem refresh in Plack, patch uses the following module... https://metacpan.org/pod/Plack::Middleware::Refresh to test: 1/ start ktd 2/ add warn to about.pl file, loadpage, observe no output in log :( 3/ apply patch to /etc/koha/plack.psgi 4/ restart plack 5/ add warn to about.pl file, loadpage, observe output in log :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 73

[Bug 29531] New: CanBookBeRenewed is inconsistent when checking AllowRenewalIfOtherItemsAvailable
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '24

15 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29531 Bug ID: 29531 Summary: CanBookBeRenewed is inconsistent when checking AllowRenewalIfOtherItemsAvailable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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 In working on bug 29483 it was found that the logic of CanBookBeRenewed can be flawed when relating to AllowRenewalIfOtherItemsAvailable At checkin we call 'CheckReserves' to find holds on the current item and will fill only holds that obey hold 'policies' - but we will also fill a hold that violates the 'rules' To recreate: 1 - Set circ rules to allow 5 holds for All/All 2 - Set an itemtype level circ rule to allow 0 holds 3 - Place a title level hold on a record with an item of that type and one of another type 4 - Note while placing hold that you cannot select the item of that type 5 - Check in the item with that type - the hold is trapped - ignore it for now 6 - Check out the other item to a patron 7 - Note the renew column in checkouts says 'On hold' 8 - Set AllowRenewalIfOtherItemsAvailable to 'Allow' 9 - Note the renew column still says 'On hold' despite the fact that that item will fill the existing hold -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 26482] New: Add macros ability to basic editor
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '24

15 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26482 Bug ID: 26482 Summary: Add macros ability to basic editor Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl With the enhancements to macro functionality, it would be really nice to be able to use macros in the basic editor too. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 24192] New: Show host record items in basket/shelves
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '24

14 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24192 Bug ID: 24192 Summary: Show host record items in basket/shelves Change 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 If EasyAnalyticalRecords is enabled, and if record has no items, display host record items in baskets and lists (staff interface only) Also, show items.enumchron in both pages -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 32381] New: Koha should be able to receive and record reasons for failed SMS notices
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '24

14 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32381 Bug ID: 32381 Summary: Koha should be able to receive and record reasons for failed SMS notices 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: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org When a third-party SMS-sending service fails to send a notice and returns a reason for the failure, there is apparently no way for that reason to get passed into Koha and recorded in message_queue.failure_code. I gather this is a limitation based on the SMS::Send drivers. For example, if a library is using Twilio to send their SMS notices and a patron unsubscribes to library texts via Twilio, all future SMS notices generated in Koha will fail to send. In the staff interface, they show "NO_NOTES" in message_queue.failure_code. The error logs on the server show "Attempt to send to unsubscribed recipient at /usr/share/perl5/SMS/Send.pm line=270." It would be quite useful if the Koha interface could show staff why the notice didn't send. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6