April 2024 - Koha-bugs - lists.koha-community.org

[Bug 35960] XSS in staff login form
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '24

03 Apr '24

1 0

[Bug 24879] Add missing authentication checks
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '24

03 Apr '24

1 0

[Bug 36501] New: purchase suggestions
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '24

03 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36501 Bug ID: 36501 Summary: purchase suggestions Change sponsored?: --- Product: Project Infrastructure Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Bugzilla Assignee: jonathan.druart(a)gmail.com Reporter: sistemak.medialab(a)tabakalera.eus Hello, We have instaled Koha 23.05 and I am realized that the patrons can´t follow their purchase suggestions from the Opac. It can make a suggestions but yhen the user can´t follow from the Opac profile the state of the suggestion. Do anybody know something about that? Thanks! -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 35591] New: bulkmarcimport.pl overwrites data if controlnumber eq authid
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '24

03 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35591 Bug ID: 35591 Summary: bulkmarcimport.pl overwrites data if controlnumber eq authid Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: domm(a)plix.at QA Contact: testopia(a)bugs.koha-community.org We had a lot of auth_header (~700.000). Then we decided to import a lot more (10.000.000). We used --update together with a match-rule (based on 024) to prevent duplicates. Which all worked well. Until... We discovered that ~30k of our old auths where overwritten with "random" data (some other auths). What used to be "Graz" was now "Centro Editoriale Valtortiano". After a bit of panic we were able to restore our old auths from a backup. But what happend? The problem is that eg "Graz" had authid=777317. But "Valtortiano" has 001=00777317X. If you squint a bit (and ignore the leading 0s and the X at the end) that's the same number! And it seems that C4::AuthoritiesMarc::GuessAuthId($record) returns the value of 001, which somehow causes the confusion. I'm not entirely sure yet, where the X is stripped, but the effect is that auth-record 777317 is overwritten. An easy fix would be to add a new command line param to bulkmarcimport to either disable the call to GuessAuthId (which keeps with backwards compat, but makes it easy for other people to also run into this problem); or to only call GuessAuthId if the new param is set (saver, but changes behaviour) If you agree that this is a problem, I can prepare a patch. If we did something stupid, please enlighten us! -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 15

[Bug 33604] New: Show both article_title and title in ILL module and OPAC
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33604 Bug ID: 33604 Summary: Show both article_title and title in ILL module and OPAC 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: katrin.fischer(a)bsz-bw.de CC: pedro.amorim(a)ptfs-europe.com The ILL module will sometimes show the article title as title when one exists. This has led to quite some confusion. We should always show both, the article title and the title of the item the article is from (source). One place this is missing is the detail pages of ILL requests in OPAC and staff interface. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 9762] Log circulation overrides
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9762 --- Comment #17 from Matthias Le Gac <matthias.le-gac(a)inlibro.com> --- Created attachment 164302 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=164302&action=e… Bug 9762: Change how to pass the param issueconfirmed To test: --After each step, a message will be displayed in the action_logs table and in Tools > Log viewer -- Circulation -- Checking out 1) Check out an item that is age-restricted (AgeRestrictionOverride syspref) 2) Check out an item that has a “not for loan” status (AllowNotForLoanOverride syspref) 3) Check out an item that has a “lost” status (IssueLostItem syspref) 4) Check out an item to a patron who has reached the checkout limit (AllowTooManyOverride syspref) 5) Check out an item to a patron who is not allowed to borrow this item type 6) Check out an item to a patron who has unpaid fines (AllFinesNeedOverride and/or AllowFineOverride + noissuescharge sysprefs) 7) Check out an item on hold for someone else 8) Check out an item on hold ready for pickup by someone else 9) Check out an item already checked out to someone else (AutoReturnCheckedOutItems syspref) 10) Check out to a patron who has restrictions Circulation -- Checking in 11) Ignore a hold upon check in 12) Ignore a hold and transfer upon check in Circulation – Renewing 13) Renew an item on hold for someone else (AllowRenewalOnHoldOverride syspref) 14) Renew an item that has reached the maximum number of renewals (AllowRenewalLimitOverride syspref) Holds 15) Place a hold for a patron who is not allowed to place this item type on hold (AllowHoldPolicyOverride syspref) 16) Place a hold for a patron who has reached the maximum number of holds 17) Place an item-level hold when rules dictate that this is not allowed (In circulation rules put "On shelf holds allowed" to "If any unavailable") Current status: Failed QA -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 36425] New: koha-run-backups deletes old backup files based on number of hours since modification - not date of modification
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36425 Bug ID: 36425 Summary: koha-run-backups deletes old backup files based on number of hours since modification - not date of modification 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Our Koha partner libraries are all configured to pass koha-run-backups with the --days 2 parameter. Therefore, theoretically, any old backup files modified on a date two days ago will be deleted. However, since bug 30627 was pushed to 23.05.x and 23.11.x, we have noticed for our larger Koha instances (which run koha-run-backups for a long time each morning) the .tar.gz file from two days ago is often not deleted. This is because the .tar.gz file is not exactly 48+ hours old when the koha-run-backups runs the find command to identify old files to remove: https://github.com/Koha-Community/Koha/blob/286fc8e9833d55d694955849e4050d2… Often the .tar.gz file will be 47.9 hours old and therefore not deleted. The find command should switch to checking the modification date, to ensure all files created X days ago are deleted. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25439] New: [Omnibus] Prepare Koha to ElasticSearch 7 - ES7
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25439 Bug ID: 25439 Summary: [Omnibus] Prepare Koha to ElasticSearch 7 - ES7 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net ES6 will be end of life when the version 8 will come out[1]. there is no alpha of version 8 so we have at least half a year[2] before that happens. [1] https://www.elastic.co/support/eol [2] https://discuss.elastic.co/t/elasticsearch-8-release-date/202759/2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 26274] New: Expose cash register cashup summaries via an API route.
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26274 Bug ID: 26274 Summary: Expose cash register cashup summaries via an API route. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com Depends on: 26172 Blocks: 26272, 26273 It would be useful to expose cashup summaries via an API endpoint to allow for displaying this data in various area's around Koha on demand. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26172 [Bug 26172] Add a cashup summary view https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26272 [Bug 26272] Allow cashup summaries to be displayed from the library summary page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26273 [Bug 26273] Expose cashup summary historyfor a cash register -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[Bug 14959] Support for Library Communications Framework (LCF)
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14959 Chris Rowlands <chris.rowlands6(a)nhs.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chris.rowlands6(a)nhs.net -- You are receiving this mail because: You are watching all bug changes.

1 0