September 2021 - Koha-bugs - lists.koha-community.org

[Bug 23480] New: Check out screen (circulation.pl)
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23480 Bug ID: 23480 Summary: Check out screen (circulation.pl) 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Wondering why we have a column for renewal and a column for check in? Couldn't we: * Have a single check box? You can't renew and check in. * Put renewal information in the due date or checked out on column? * Have either multiple action buttons or a single selectable action button? I guess, theoretically, one could renew and check in at the same time with the current setup. I'm wondering if anyone actually does this? I would personally find it confusing, and I would be nervous about doing both at the same time. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

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

08 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 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 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

[Bug 16959] New: E-mail alerts for saved searches
by bugzilla-daemon＠bugs.koha-community.org 05 Dec '23

05 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16959 Bug ID: 16959 Summary: E-mail alerts for saved searches 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org It would be nice if Koha allowed to send e-mails to patrons when a new record is created for a saved search. Examples: - New records are added within a specific call number range - New records where the title contains certain words It should be possible to set this up individually per patron. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 22384] New: Make the title of an ILL clickable
by bugzilla-daemon＠bugs.koha-community.org 04 Dec '23

04 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22384 Bug ID: 22384 Summary: Make the title of an ILL clickable Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no Target Milestone: --- Today we have one column with the unclickable title of an ILL item and one column with the clickable biblionumber. It would be potentially less confusing if the title was clickable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 27667] New: Display the number of non-indexed records
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27667 Bug ID: 27667 Summary: Display the number of non-indexed records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr On "About Koha" page are displayed the numbers of indexed biblios and authorities with ES. It could be great if we could have comparison with the number of records in the database to display the number of non-indexed datas. We could have on the same page something like : Indices: koha_robin_biblios (count: 834999 on 1056480 = 221481 missing) Or on the "System information" tab with the other "Data problems". -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 26639] New: Turn auto_savepoint ON
by bugzilla-daemon＠bugs.koha-community.org 01 Dec '23

01 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26639 Bug ID: 26639 Summary: Turn auto_savepoint ON Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: major Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org We have been adding transactions a lot lately, and we have just found that we are expecting a behaviour that is not the one we have. Take a look at the code posted on bug 26518 comment 7. If we turn auto_savepoint on, we will get the behaviour we expect. This patch has been initially attach on bug 21684 comment 2, but then dropped. See also https://metacpan.org/pod/distribution/DBIx-Class/lib/DBIx/Class/Manual/Cook… -- You are receiving this mail because: You are watching all bug changes.

1 32