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

[Bug 21972] New: Record matching rule for authorities only works for first 20 authority records
by bugzilla-daemon＠bugs.koha-community.org 11 Jun '24

11 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21972 Bug ID: 21972 Summary: Record matching rule for authorities only works for first 20 authority records Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: simon.hohl(a)dainst.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 82955 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=82955&action=ed… MARC File containing geographical authority data The summary is already my first interpretation, the following is happening: I am trying trying to import some custom authority data (see attached mrc file) and have defined a matching rule accordingly: Match threshold: 1000 Record type: Authority record Match point 1: Search index: indentifier-standard Score: 500 Tag: 024 Subfields: a Offset/Length: 0 Match point 2: Search index: indentifier-standard Score: 500 Tag: 024 Subfields: 2 Offset/Length: 0 While using the command line interface (staging + commit) to automatically update authority data, I noticed that the number of successfully matched records was far too low. As a strict test I then did the following: 1. Import the data using the bulkimport script 2. Upload the same data in the staging Interface 3. See which records match and which do not, in order to find a pattern in those who fail. The only pattern I encountered was the following: Only the (initially) first 20 imported records are actually matched. Meaning only authorities with ID 1 to 20 are successfully matched with the staged import, everything else stands as "No Match". I tried this with different sets of place data, still the same result. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 23187] New: Koha::Objects supports find_or_create without passing through the Koha::Object store method
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '24

10 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23187 Bug ID: 23187 Summary: Koha::Objects supports find_or_create without passing through the Koha::Object store method Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P1 - high Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: dcook(a)prosentient.com.au, jonathan.druart(a)bugs.koha-community.org, koha-bugs(a)lists.koha-community.org, kyle(a)bywatersolutions.com, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)ptfs-europe.com, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com Depends on: 21761 Blocks: 23185 Target Milestone: --- +++ This bug was initially created as a clone of Bug #21761 +++ If we're adding triggers at the code level all over the place by overloading the store method we need to never ever let dbic handle it.. by allowing directly passing data to dbic's find_or_create method in Koha::Objects we are exposing ourselves to places in the codebase skipping the store triggers. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21761 [Bug 21761] Koha::Object supports passing through 'update' which means we can side step 'set' + 'store' https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23185 [Bug 23185] Koha::Objects supports passing through 'update' which means we can side step 'set' + 'store' -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. You are watching all bug changes.

1 8

[Bug 20826] New: Error during initial setup
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '24

10 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20826 Bug ID: 20826 Summary: Error during initial setup Change sponsored?: --- Product: Koha Version: master Hardware: PC OS: Linux Status: NEW Severity: blocker Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mrushizha(a)outlook.com QA Contact: testopia(a)bugs.koha-community.org I am new to both Linux and Koha. I have been trying to install Koha on a new installation of Ubuntu Linux 16.04.4 LTS Desktop 32-bit. I ran the following preparation commands without any problem: sudo apt-get update sudo apt-get upgrade sudo echo deb http://debian.koha-community.org/koha stable main | sudo tee /etc/apt/sources.list.d/koha.list sudo wget -O- http://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - sudo apt-get update sudo apt-get upgrade sudo apt-get clean I ran the install command and I never got passed it: sudo apt-get install koha-common All I am getting is the following: diasha@DIASHA-UBUNTU:~$ sudo apt-get install koha-common [sudo] password for diasha: Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: koha-common : Depends: libnet-oauth2-authorizationserver-perl but it is not going to be installed E: Unable to correct problems, you have held broken packages. I have Googled this and and I also did a clean re-installation of Ubuntu and tried to install Koha to no avail. I am looking forward to your response. Regards, Michael -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 34

[Bug 22462] New: Crash in patron card printing
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '24

10 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22462 Bug ID: 22462 Summary: Crash in patron card printing Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: christian.stelzenmueller(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Patron card printing: Layout: the entered text in a text field is longer then the possible page height, page width, card height and card width in the template. Result: when running a batch, the created pdf can't be opened, and Koha doesn't respond. It also seems to end in an infinite loop. It also happens if all values in the template are saved with the default values "0". Template: page height: 50 mm page width: 20 mm card heigh: 50 mmm card width: 20 mm Layout: Textfield Text: Libraries are great -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 22497] New: '0' width can lead to an infinite loop.
by bugzilla-daemon＠bugs.koha-community.org 10 Jun '24

10 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22497 Bug ID: 22497 Summary: '0' width can lead to an infinite loop. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- > > "Aha... it's the parentheses which are the problem. They're being interpreted as > > regex metacharacters and not literal values!" > > We noticed that there seems to be an infinite loop if the template has some > or all entries with "0" in it (like in default when creating a new > template). Could this be the same cause? Sorry, I just realized that you were referring to the template rather than the layout. Yes, it would be a related problem, but a separate issue. If 'label_width' is 0, then $self->{'width'} will be 0. That means that this condition will be triggered: if (($string_width + $text_attribs->{'llx'}) > $self->{'width'}) And because $self->{'width'} is 0, then the following condition would never feasibly be triggered: if (($string_width + $text_attribs->{'llx'}) < $self->{'width'}) And this condition is the only thing that can stop the infinite loop. Really the line wrapping code looks like it would benefit from a re-write. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 21508] New: lost item phrase is repeated on pay fines page, when a patron is charged after an item is changed to lost
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '24

08 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21508 Bug ID: 21508 Summary: lost item phrase is repeated on pay fines page, when a patron is charged after an item is changed to lost Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org The preference system WhenLostChargeReplacementFee = charge On the tab fines, pay fines (/members/pay.pl), when a patron is charged automatically because an item he has borrowed is changed to lost status, the test repeats "lost iem" twice in the column description : Lost item , Lost Item + Title -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21507] New: Decimal separators issues in patrons payments/fines, simplified
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '24

08 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21507 Bug ID: 21507 Summary: Decimal separators issues in patrons payments/fines, simplified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr This is a reboot of bug 12310 with simpler specs. kidclamp and paul_p discussed about it at the KohaCon and they would push for simpler requirements than the ones that I got at the 2018 march hackfest. And after some discussions on #koha, it seems that it should be acceptable :) == Specs == - allow only one separator, the one from CurrencyFormat - if some libraries really need supporting multiple ones, it should be another patch, don't hesitate to open a bug to talk about this - do not handle thousands separator - block form submission if the format is wrong == resources: some of the latest IRC discussions == http://irc.koha-community.org/koha/2018-10-05#i_2078324 http://irc.koha-community.org/koha/2018-10-05#i_2078377 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41

[Bug 20819] New: GDPR: Add a consent field for processing personal data
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '24

06 Jun '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20819 Bug ID: 20819 Summary: GDPR: Add a consent field for processing personal data Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com See 18081 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 106

[Bug 17810] New: Add a button to navigate between notices
by bugzilla-daemon＠bugs.koha-community.org 31 May '24

31 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17810 Bug ID: 17810 Summary: Add a button to navigate between notices 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: alexandre.breton(a)ccsr.qc.ca QA Contact: testopia(a)bugs.koha-community.org Created attachment 58404 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=58404&action=ed… The small window in the upper left circled in red It will be interessting to have the option to navigate directly between notices (previous/next). The option already exist in catalog module. Maybe, it can be added into another module ? 1)From the start, go to lists 2)Take "public list" and enter a search 3)Select any notice to have all his details on screen 4)Observe that you cannot reach another notice of your search without making "previous page" After some searches here, the patch doesn't seems to exist for that. Thanks, Alexandre from CCSR -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 20358] New: Add unitprice_tax_included on report spent.pl
by bugzilla-daemon＠bugs.koha-community.org 31 May '24

31 May '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20358 Bug ID: 20358 Summary: Add unitprice_tax_included on report spent.pl 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: marjorie.barry-vila(a)collecto.ca QA Contact: testopia(a)bugs.koha-community.org Hi, On acqui/spent.pl, it would be nice to have a new column for unitprice_tax_included. Regards, Marjorie -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2