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

[Bug 19521] New: Partial fine payment is not working with comma decimal separator
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19521 Bug ID: 19521 Summary: Partial fine payment is not working with comma decimal separator Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using comma as decimal separator, if you modify the sum to pay in the "Collect from patron" field, the sum is wrongly converted. say you have 15,50 € as initial amount you modify to pay only 5,50 € and you get 550.00 €. Then of course, you get an alert saying that the sum must be equal or inferior to initial one. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 22

[Bug 22752] New: Show next available or item specific hold types in opac-user.pl#opac-user-holds
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22752 Bug ID: 22752 Summary: Show next available or item specific hold types in opac-user.pl#opac-user-holds Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- When a patron is viewing the holds they've placed in opac-user.pl#opac-user-holds, it does not show the user if they have requested a specific item or the next available item. The patron should be given the ability to see this information, in case they incorrectly placed a hold. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 23537] New: Overdrive won't show complete results if the Overdrive object doesn't have a primaryCreator
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23537 Bug ID: 23537 Summary: Overdrive won't show complete results if the Overdrive object doesn't have a primaryCreator 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: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Overdrive won't show complete results if the Overdrive object doesn't have a primaryCreator Some items from overdrive, such as magazines, don't have a primaryCreator in their object. When Koha gets a result like this, the overdrive search won't show any results after the first to have this condition, because it's trying to push an undefined property. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 22527] New: Web installer links to wrong database manual when database user doesn't have required privileges
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22527 Bug ID: 22527 Summary: Web installer links to wrong database manual when database user doesn't have required privileges Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Target Milestone: --- To reproduce: 1. Use MySQL or MariaDB for your Koha installation 2. Create an empty database and point $KOHA_CONF to this database name. 3. Grant SELECT privilege to your database user, e.g. grant select on koha3.* to 'koha'@'%' identified by 'koha'; 4. Go to step 2 of web installer where it checks database connection 5. Observe the following message User koha doesn't have enough privilege on database koha. Ask for or make a change in the user's privileges. User koha must have USAGE, INSERT, UPDATE, DELETE, DROP and CREATE privileges on database koha2. Need help? See manual for PostgreSQL 6. Note "See manual for PostgreSQL" is wrong. Should be "See manual for MySQL". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 22816] New: OPAC detail holdings table doesn't fill it's div
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22816 Bug ID: 22816 Summary: OPAC detail holdings table doesn't fill it's div Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- it could fit better, so let's make it so. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 19849] New: Rebase of bug 16621 partially reverted bug 12509
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19849 Bug ID: 19849 Summary: Rebase of bug 16621 partially reverted bug 12509 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Causing a string to become untranslatable again. This is the first attachment that reverted the relevant part of bug 16621 See the first part of the diff. https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=53252&action=di… -- You are receiving this mail because: You are watching all bug changes.

1 18

[Bug 20915] New: Use date --iso-8601 instead of date +%Y-%m-%d to be more readable an crontab friendly
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20915 Bug ID: 20915 Summary: Use date --iso-8601 instead of date +%Y-%m-%d to be more readable an crontab friendly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor.grousset(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Because in crontab you have to write date '+\%Y-\%m-\%d' -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 22559] New: OPAC Forgotten password functionality not working
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22559 Bug ID: 22559 Summary: OPAC Forgotten password functionality not working Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Trying to reset a password using the forgotten password OPAC functionality seems to fail with one of a couple of messages: Can't call method "catch" without a package or object reference at /home/vagrant/kohaclone/opac/opac-password-recovery.pl line 158 or Can't call method "isa" on an undefined value at /home/vagrant/kohaclone/opac/opac-password-recovery.pl line 159 This seems to happen after commit f822dee088b86edecd5d5c73718ad9f8a04c0664 To reproduce: Enable OpacResetPassword Create a borrower with a username and password Go to the OPAC, try to reset the password (I always get the reset link out of the message_queue in the database rather than worry about receiving the actual email. You do you.) Go to the link provided. Attempt to set a password, this should fail. -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 17215] New: Cardnumbers of patrons created using LDAP Replication not using autoMemberNum if configured
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17215 Bug ID: 17215 Summary: Cardnumbers of patrons created using LDAP Replication not using autoMemberNum if configured 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: ldjamison(a)marywood.edu QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using LDAP and leveraging the 'replicate' flag, patrons who are replicated have their cardnumber assigned equal to their LDAP username. This is an inconsistency when the 'autoMemberNum' System Preference is set to 'Do'. When 'autoMemberNum' is set to 'Don't' then replicate should act as it currently does. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 24608] New: Allow modification of checkout due date
by bugzilla-daemon＠bugs.koha-community.org 25 Jul '24

25 Jul '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24608 Bug ID: 24608 Summary: Allow modification of checkout due date Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently it is not possible to modify a checkout's due date. This bug proposes to allow such an action. It is only proposed to allow modification of a due date *forward* at this stage as moving a due date backwards may involve additional complication that will require further thought. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 70