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

[Bug 23454] New: Fine for the previous overdue may get overwritten by the next one
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '23

09 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23454 Bug ID: 23454 Summary: Fine for the previous overdue may get overwritten by the next one Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: hemantharao.kr(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The fine for the previous overdue is getting overwritten by the next one in Koha version 18.11 in case of renewal with overdue, this is happening even after updating bug fix patch no. 17135. Please help me out with this error. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 22018] New: Add an option to 'AllowEarlyRenewal' to enable users to renew before the autorenew date
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22018 Bug ID: 22018 Summary: Add an option to 'AllowEarlyRenewal' to enable users to renew before the autorenew 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- There are occasions where a patron may want to manually renew an item before the date on which an autorenewal would take place; for example, if they are going on holiday they may wish to renew all their items before they leave to prevent them accruing fines whilst away. Autorenewals can be blocked by a hold having been placed on an item, and if this hold was placed after the original patron had left for their holiday but before the autorenewal date then the patron has no option but to start accruing a fine. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 24

[Bug 29438] New: Importing a record with an ISBN13 with no ISBN10 counterpart does not save the ISBN
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29438 Bug ID: 29438 Summary: Importing a record with an ISBN13 with no ISBN10 counterpart does not save the ISBN Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When importing a record we call 'NormalizeISBN' This routine returns nothing when an ISBN13 cannot be converted to an ISBN10 - we should have a fallback to return the original value -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 33673] New: Global system preferences - change to just system preferences
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '23

07 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33673 Bug ID: 33673 Summary: Global system preferences - change to just system preferences Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Day-to-day, we normally just refer to "system preferences" rather than "global system preferences". I don't think there is any clear distinction between "Global system preferences" and "System preferences", or any need to have the "Global". This would mean changing Administration > Global system preferences to just "System preferences". -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 31361] New: Button batch operations disappears when alias is used for itemnumber of biblionumber
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '23

07 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31361 Bug ID: 31361 Summary: Button batch operations disappears when alias is used for itemnumber of biblionumber Change sponsored?: --- Product: Koha Version: 21.11 Hardware: All OS: Windows Status: NEW Severity: normal Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: j.m.koopmans(a)saxion.nl QA Contact: testopia(a)bugs.koha-community.org Created attachment 139128 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=139128&action=e… screenshot report result with batch modification button When running a SQL-report and using an alias for itemnumber or biblionumber in SELECT, the button for 'Batch operations with 20 visible records' disappears. Using an alias for other columns is no problem. Example SQL with button: SELECT items.itemnumber,items.barcode,items.notforloan as Status,biblio.title,items.ccode as Itemtype FROM items LEFT JOIN biblioitems on (items.biblioitemnumber=biblioitems.biblioitemnumber) LEFT JOIN biblio on (biblioitems.biblionumber=biblio.biblionumber) WHERE items.homebranch=<<homebranch|branches>> AND items.itype=<<itype|itemtypes>> AND items.notforloan=<<notforloan>> ORDER BY items.itemnumber asc Changing it to 'SELECT items.itemnumber as Itemnr, etc.' removes the button and the ability for batch processing. The same thing occurs when using an alias for biblionumber in a report. Example SQL with button: SELECT CONCAT ('<a href=\"/cgi-bin/koha/catalogue/detail.pl?biblionumber=',biblio.biblionumber,'\" target=new>',biblio.title,' </a>') as Titel, items.biblionumber,biblio.datecreated as Datum FROM items LEFT JOIN biblioitems on (items.biblioitemnumber=biblioitems.biblioitemnumber) LEFT JOIN biblio on (biblioitems.biblionumber=biblio.biblionumber) where date (datecreated) BETWEEN <<From date|date>> AND <<To date|date>> ORDER BY biblio.datecreated desc Changing 'items.biblionumber to items.biblionumber as Biblionr' removes the button. Also tested it in version 20.11 with the same results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 29291] New: Self Registration e-mail verification is not stored in notices
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29291 Bug ID: 29291 Summary: Self Registration e-mail verification is not stored in notices 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be great if the self registration e-mail verification was stored in the notifications. Any password that might be in the message could be masked in storage. Or the message itself could be masked. We would at least have a record of the attempt. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 25654] New: Making the Contact Section / Guarantor Section separate from the Contact details of the patron would be less confusing
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25654 Bug ID: 25654 Summary: Making the Contact Section / Guarantor Section separate from the Contact details of the patron would be less confusing Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 105490 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=105490&action=e… differences With the recent change of the Guarantors in Koha, the Contact section of the Patron Detail page (when editing) is confusing. Prior to 19.11, the Contact section was created for the Contact details of the Patron, phone, email, fax. Now in 19.11, the Guarantor (Non-Koha) has been added to the contact section, causing questions if this is the Guarantor's contact information or the primary patron's contact information. It would be nice if there could be a separation of the two areas in the Koha patrons form (memberentry.pl) Attaching an image of the before 19.11 and 19.11 contact section. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 32613] New: Can we add 'autocompletion' to our SQL reports editor?
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32613 Bug ID: 32613 Summary: Can we add 'autocompletion' to our SQL reports editor? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org We're using CodeMirror for the SQL reports editor.. I wonder if there's a plugin or configuration option for that which supports basic autocompletion, similar to what is found on https://sqliteonline.com/, that we can impliment for Koha? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 40

[Bug 27096] New: Add option to message_queue to exclude specific letter codes
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27096 Bug ID: 27096 Summary: Add option to message_queue to exclude specific letter codes 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 25097 Bug 25907 allows one to set process_message_queue to only send notices with the specified letter codes. In some cases, it'd be hand to invert that and list notices to be excluded. So an exclude-list rather than an include-list. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25097 [Bug 25097] Add option to message_queue to allow for only specific sending notices -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 21769] New: koha-restore file-exists
by bugzilla-daemon＠bugs.koha-community.org 06 Dec '23

06 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21769 Bug ID: 21769 Summary: koha-restore file-exists Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: Heinrich.Hartl(a)email.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz I have two virtual servers. vm-prod is running the production, vm-dev was created long ago as clone from vm-prod. Update procedures are always first tried using vm-dev and only then applied to vm-prod. So there is a lot of similarity between these two vm's. vm-prod and vm-dev are ubuntu 14.4 LTS, koha 16.11. I did hhl@koha-VM-dev:~ > sudo koha-remove library [sudo] password for hhl: Removing Koha instance library Stopping Zebra server for library * Stopping Koha indexing daemon for library [ OK ] * Restarting web server apache2 [ OK ] sudo koha-restore library-2018-10-25.sql.gz library-2018-10-25.tar.gz hhl@koha-VM-dev:~ > sudo koha-restore library-2018-10-25.sql.gz library-2018-10-25.tar.gz [sudo] password for hhl: ERROR: File exists: /var/lib/koha/library/ ERROR: File exists: /var/lib/koha/library/authorities/ ERROR: File exists: /var/lib/koha/library/authorities/register/ ERROR: File exists: /var/lib/koha/library/authorities/key/ ERROR: File exists: /var/lib/koha/library/authorities/tmp/ ERROR: File exists: /var/lib/koha/library/authorities/shadow/ ERROR: File exists: /var/lib/koha/library/biblios/ ERROR: File exists: /var/lib/koha/library/biblios/register/ ERROR: File exists: /var/lib/koha/library/biblios/register/sort100-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/dict-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort23-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/recdA-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort29-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambC-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort143-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort58-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort40-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambD-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort19-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambA-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort68-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/recdB-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort139-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort44-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/isambB-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort6-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/reci-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort11-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/gmatch-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort94-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort36-0.mf ERROR: File exists: /var/lib/koha/library/biblios/register/sort202-0.mf ERROR: File exists: /var/lib/koha/library/biblios/key/ ERROR: File exists: /var/lib/koha/library/biblios/tmp/ ERROR: File exists: /var/lib/koha/library/biblios/shadow/ ERROR: File exists: /var/lib/koha/library/plugins/ ERROR: File exists: /var/lib/koha/library/uploads/ ERROR 1396 (HY000) at line 1: Operation DROP USER failed for 'koha_library'@'%' Warning: You passed -x which is already the default and is now deprecated item-level_itypes set but no itemtype set for item (64339) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64342) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64334) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64344) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64348) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64343) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (65556) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64341) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64352) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64892) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (65581) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64337) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64338) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (64596) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. item-level_itypes set but no itemtype set for item (61258) at /usr/share/koha/lib/Koha/Schema/Result/Item.pm line 698. * Restarting web server apache2 [Fri Nov 02 15:16:48.516017 2018] [core:warn] [pid 19897] AH00111: Config variable ${instance} is not defined [Fri Nov 02 15:16:48.516171 2018] [core:warn] [pid 19897] AH00111: Config variable ${instance} is not defined [ OK ] hhl@koha-VM-dev:~ > I am confused - an error should stop a procedure I am pleased - the koha instance on vm-dev subsequently was running, a few simple tests succeeded I am afraid - there may be some serious malfunction not to be detected easily Where can a find an explanation for above messages? Are there activities required to resolve problems? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4