June 2025 - Koha-bugs - lists.koha-community.org

[Bug 31143] New: We should attempt to fix/identify all cases where '0000-00-00' may still remain in the database
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31143 Bug ID: 31143 Summary: We should attempt to fix/identify all cases where '0000-00-00' may still remain in the database Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org With the move to more and more of Koha using the REST API's and our rest API's being suitably strict about date formats, we need to retrospectively correct occurrences of 0000-00-00 dates appear in database fields system wide. I've had enough occurrences of bad data still in the database after a number of upgrade and it biting me in the UI that I think we should now look at introducing a script to either bulk fix these or at the least identify them and warn they will cause serious issues going forward. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 127

[Bug 38788] New: Fix '0000-00-00' issue on database
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38788 Bug ID: 38788 Summary: Fix '0000-00-00' issue on database Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: adifbbk1(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Continuation of the thread from https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31143#c90 I have mysql version 8.0.40-0ubuntu0.24.04.1 setup in the remote azure machine. The infrastructure is setup such that there are 2 VMs, one acting as Koha application server and another acting as MySQL database server. MySQL server does not have koha installed but the credentials are setup such that application server has access to it. I am getting errors while running fix_invalid_dates.pl file. DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Incorrect TIMESTAMP value: '0000-00-00' at ./fix_invalid_dates.pl line 65 The line 65 contains this line: my $invalid_dates = $rs->search( { $column => '0000-00-00' } )->count; It is very obvious that the mysql database throws sanity errors when there are errors in database. To attempt fixing it, I added these lines on top: # Disable strict mode for this session $schema->storage->dbh_do( sub { my ($storage, $dbh) = @_; $dbh->do("SET SESSION sql_mode = ''"); # Disables all kinds of checks in mysql for the whole script session } ); These seemingly did nothing. After running cli tool, it didn't return any response. Especially when I try searching names of old patrons, it throws error "month out of range" (there is possibility that the "borrowers" table is not properly cleaned using that script) What worked for me is below command when running mysql as root user: UPDATE borrowers SET lastseen = NULL WHERE CAST(lastseen AS CHAR) = '0000-00-00 00:00:00'; -- 6000+ rows changed UPDATE borrowers SET date_renewed = NULL WHERE CAST(date_renewed AS CHAR) = '0000-00-00'; -- 3000+ rows changed UPDATE categories SET enrolmentperioddate = NULL WHERE CAST(enrolmentperioddate AS CHAR) = '0000-00-00'; -- 4 rows changed Please suggest me if there are other tables having same issue too so that I can manually fix it using mysql. I manually created and run the fix_invalid_dates.pl file using koha-shell in koha 23.11 (which was originally not backported) but I don't think the script file not working properly is version-related issue at all. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 35490] New: Remove GetMarcItem from C4::Biblio
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35490 Bug ID: 35490 Summary: Remove GetMarcItem from C4::Biblio Change sponsored?: --- Product: Koha Version: master 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: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 35955] New CSRF token generated everytime we need one
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35955 Wainui Witika-Park <wainuiwitikapark(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wainuiwitikapark(a)catalyst.n | |et.nz Status|Pushed to oldstable |RESOLVED Resolution|--- |FIXED --- Comment #16 from Wainui Witika-Park <wainuiwitikapark(a)catalyst.net.nz> --- Not backporting to 22.11 unless requested -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 34478] Full CSRF protection
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34478 Bug 34478 depends on bug 35955, which changed state. Bug 35955 Summary: New CSRF token generated everytime we need one https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35955 What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to oldstable |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 35379] New: 'searchfield' parameter name misleading when translating
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35379 Bug ID: 35379 Summary: 'searchfield' parameter name misleading when translating Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In this file: koha-tmpl/intranet-tmpl/prog/en/modules/admin/systempreferences.tt this would read better tx("Modify system preference '{searchfield}'", { searchfield = searchfield }) if the parameter was renamed to system_preference like the in the rest of the file. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 36792] New: limit POSIX imports
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36792 Bug ID: 36792 Summary: limit POSIX imports Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: januszop(a)gmail.com Reporter: januszop(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: katrin.fischer(a)bsz-bw.de, m.de.rooy(a)rijksmuseum.nl A Marcel's QA patch to Bug 36552 added use POSIX; in two spots. In https://metacpan.org/pod/POSIX we read: CAVEATS Everything is exported by default (with a handful of exceptions). This is an unfortunate backwards compatibility feature and its use is strongly discouraged. You should either prevent the exporting (by saying use POSIX ();, as usual) and then use fully qualified names (e.g. POSIX::SEEK_END), or give an explicit import list. If you do neither and opt for the default (as in use POSIX;), you will import hundreds and hundreds of symbols into your namespace. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 35582] New: Advanced search languages should be listed with selected UI language descriptions shown first if available
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35582 Bug ID: 35582 Summary: Advanced search languages should be listed with selected UI language descriptions shown first if available Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: lmstrand(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Languages are being showed by their localized name first in the advanced search language limit dropdowns and the user's intranet language selection's description follows next (or defaults to English). It's hard to select the language you want from the list if the languages' descriptions are written in the way they are written in the country the language is being used, Suomi (Finnish) or ལྷ་སའི་སྐད་ (Standard Tibetan) for example. They should be listed by the language description that matches the user's selected language in the intranet first and then the local name, like Finnish (Suomi), Standard Tibetan (ལྷ་སའི་སྐད)་ if the intranet language selection is English for example. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 28

[Bug 36605] New: TrackLastPatronActivity for SIP should track both patron status and patron information requests
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36605 Bug ID: 36605 Summary: TrackLastPatronActivity for SIP should track both patron status and patron information requests Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org OverDrive now uses the patron status request for verifying patrons. Previously they used the patron information request. This change has caused patrons last seen date to not be updated by OverDrive logins. To fix this, we should extend the functionality of TrackLastPatronActivity for SIP/ILSDI to include the status request -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 18

[Bug 38284] New: handle_patron_status dies if patron not found
by bugzilla-daemon＠bugs.koha-community.org 23 Jun '25

23 Jun '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38284 Bug ID: 38284 Summary: handle_patron_status dies if patron not found Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: SIP2 Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: kyle(a)bywatersolutions.com, nick(a)bywatersolutions.com Depends on: 36605 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36605 [Bug 36605] TrackLastPatronActivity for SIP should track both patron status and patron information requests -- You are receiving this mail because: You are watching all bug changes.

1 36