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

[Bug 23766] New: Allow MARC record importer to handle large batches without causing memory issues
by bugzilla-daemon＠bugs.koha-community.org 09 Dec '23

09 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23766 Bug ID: 23766 Summary: Allow MARC record importer to handle large batches without causing memory issues 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Right now, no matter how large a marc batch file is, the marc record stager loads all the records into memory ( see http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=C4/ImportBatch.pm… ). We should break this up and process chunks of records at a time to keep the memory footprint low for servers without enough RAM to handle this memory load. My proposal is to modify process_batch in stage_file to loop over the records processing X number of records at a time. X should be configurable via a syspref. In addition, this will require modifying C4::ImporBatch::RecordsFromMARCXMLFile to accept an offset and a count such that it will start at the offset and return the given count of records. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 23629] New: Retain search results until staff close window
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23629 Bug ID: 23629 Summary: Retain search results until staff close window Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When searching for MARC records to import, often more than one search result is relevant to the work at hand. When a staff member clicks on import for one result the pop up window automatically closes, meaning that the search has to be undertaken again. This can be annoying and frustrating for cataloguers. For example adding records for a new course in early years education will have a lot of resources with similar titles. It's annoying to do a search, see that half a dozen of the results are on your list, and then have to repeat the search 6 times to get all the titles. It would be good to be able to work from the one result list until the next search is performed or the staff member closes the pop-up window. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 23572] New: Regression: Bug 18878 - Improve item form display / labels too far from input fields
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23572 Bug ID: 23572 Summary: Regression: Bug 18878 - Improve item form display / labels too far from input fields Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Depends on: 18878 Bug 18887 changed the item form so that the labels aligned to the right, being closer to the input field and easier to read. In 18.11.x this is no longer the case. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18878 [Bug 18878] Improve item form display / labels too far from input fields -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 23550] New: Not possible to add multiple patron restrictions in memberentry.pl
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23550 Bug ID: 23550 Summary: Not possible to add multiple patron restrictions in memberentry.pl Change sponsored?: --- Product: Koha Version: unspecified 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 When editing a patron record in memberentry.pl, you have a link to "Add manual restriction", but after you click and add, there is no link to add another. You have to save and edit again, or you can add multiple restrictions straight from circulation.pl or moremember.pl. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23501] New: Drag-and-drop hold reordering in the staff client
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23501 Bug ID: 23501 Summary: Drag-and-drop hold reordering in the staff client Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Blocks: 16421 It would be nice to be able to use drag-and-drop to reorder holds in the staff client. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16421 [Bug 16421] Move hold edit actions into dropdown menu -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 23498] New: Broken links to bibs when placing holds on multiple records and a hold exists on at least one record
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '23

08 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23498 Bug ID: 23498 Summary: Broken links to bibs when placing holds on multiple records and a hold exists on at least one record Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: jrobb(a)sekls.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 92441 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=92441&action=ed… Screenshot of broken link When placing holds on multiple records at once from a list of search results in the staff client, if one of the selected records already has a hold, the "Confirm Holds" page where you choose a patron will list each record and the existing holds. The links to the bib records on that page are incomplete. To replicate the issue: 1. Run a search that gives multiple results 2. Place an individual hold on the first record 3. Repeat the search 4. Use the check boxes to select 2 or more records, including the record with a hold 5. Click 'Place Hold' at the top of the results 6. The next page should have a box to search for the patron, and list out the records you selected and any holds on those records. Hover over the title of the record and notice that the URL for each is lacking a bib number at the end. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

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