https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 --- Comment #1 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Hi, this looks like a configuration issue - "yes, no, inherit" could be options of a system preference or a setting on patron category level where in your case something outside this list is stored. I would start with checking your values in the patron categories. Bugzilla is not a good place to solve these type of issues - please try the Mattermost chat server or the mailing lists if the above is not helping you to resolve it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 Dr. Dilipkumar Vala <ddvala9@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ddvala9@gmail.com --- Comment #3 from Dr. Dilipkumar Vala <ddvala9@gmail.com> --- I'm also facing the same issue after the upgrade. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |40337 CC| |dcook@prosentient.com.au --- Comment #5 from David Cook <dcook@prosentient.com.au> --- (In reply to Katrin Fischer from comment #1)

Bugzilla is not a good place to solve these type of issues - please try the Mattermost chat server or the mailing lists if the above is not helping you to resolve it.

Usually I'd agree but it's starting to sound like a systemic problem and a legitimate bug. -- I think we'll need some server logs here to troubleshoot this. Looks like bug 40337 is probably the cause although it's not clear yet. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40337 [Bug 40337] checkprevcheckout must be defined as ENUM at DB level -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 --- Comment #6 from David Cook <dcook@prosentient.com.au> --- Ok I think I might have figured this one out. See https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40337#c21 People experiencing the problem will want to run the following SQL and report back on what they find: select distinct checkprevcheckout from borrowers; select distinct checkprevcheckout from categories; select distinct checkprevcheckout from deletedborrowers; -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 --- Comment #8 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I mostly meant that debugging would be easier in chat than here, because it seemed like a data issue more than a program one at first glance. But I think you are right, it looks like something might have gone wrong. The SQL would be a good start. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 Paul Derscheid <paul.derscheid@lmscloud.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |paul.derscheid@lmscloud.de --- Comment #10 from Paul Derscheid <paul.derscheid@lmscloud.de> --- So, the way to fix this until the next maintenance release is the following: 1. Ensure you have a database backup. 2. Update to v25.05.02-2. The database revision will not run again, so the next step is manual. 3. There's a file at installer/data/mysql/db_revs/250501001.pl. This file contains the fixed sql statements for the fixed update, but these will not run automatically. 4. The fastest way to fix this is to take those statements and run them in the database manually. Do not run the following statements all at once, do one after the other, the limits are denoted by the comments (-- Transaction for ...). You can wrap each statement in a transaction, like so: -- Transaction for borrowers table BEGIN; UPDATE borrowers SET checkprevcheckout = 'inherit' WHERE checkprevcheckout NOT IN ('yes','no','inherit'); ALTER TABLE borrowers MODIFY COLUMN \`checkprevcheckout\` enum('yes', 'no', 'inherit') NOT NULL DEFAULT 'inherit' COMMENT 'produce a warning for this patron if this item has previously been checked out to this patron if ''yes'', not if ''no'', defer to category setting if ''inherit''.'; COMMIT; -- Transaction for categories table BEGIN; UPDATE categories SET checkprevcheckout = 'inherit' WHERE checkprevcheckout NOT IN ('yes','no','inherit'); ALTER TABLE categories MODIFY COLUMN \`checkprevcheckout\` enum('yes', 'no', 'inherit') NOT NULL DEFAULT 'inherit' COMMENT 'produce a warning for this patron category if this item has previously been checked out to this patron if ''yes'', not if ''no'', defer to syspref setting if ''inherit''.'; COMMIT; -- Transaction for deletedborrowers table BEGIN; UPDATE deletedborrowers SET checkprevcheckout = 'inherit' WHERE checkprevcheckout NOT IN ('yes','no','inherit'); ALTER TABLE deletedborrowers MODIFY COLUMN \`checkprevcheckout\` enum('yes', 'no', 'inherit') NOT NULL DEFAULT 'inherit' COMMENT 'produce a warning for this patron if this item has previously been checked out to this patron if ''yes'', not if ''no'', defer to category setting if ''inherit''.'; COMMIT; To get a database shell, you can use koha-mysql <YOUR_INSTANCE_NAME>. 5. After that, the bug should be fixed. If not, leave a comment. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 --- Comment #11 from Isabel Pineda <isabel.pineda@ds.edu.sv> --- (In reply to Paul Derscheid from comment #10)

So, the way to fix this until the next maintenance release is the following: 1. Ensure you have a database backup.

2. Update to v25.05.02-2.

The database revision will not run again, so the next step is manual.

3. There's a file at installer/data/mysql/db_revs/250501001.pl.

This file contains the fixed sql statements for the fixed update, but these will not run automatically.

4. The fastest way to fix this is to take those statements and run them in the database manually.

Do not run the following statements all at once, do one after the other, the limits are denoted by the comments (-- Transaction for ...).

You can wrap each statement in a transaction, like so:

-- Transaction for borrowers table BEGIN; UPDATE borrowers SET checkprevcheckout = 'inherit' WHERE checkprevcheckout NOT IN ('yes','no','inherit');

ALTER TABLE borrowers MODIFY COLUMN \`checkprevcheckout\` enum('yes', 'no', 'inherit') NOT NULL DEFAULT 'inherit' COMMENT 'produce a warning for this patron if this item has previously been checked out to this patron if ''yes'', not if ''no'', defer to category setting if ''inherit''.'; COMMIT;

-- Transaction for categories table BEGIN; UPDATE categories SET checkprevcheckout = 'inherit' WHERE checkprevcheckout NOT IN ('yes','no','inherit');

ALTER TABLE categories MODIFY COLUMN \`checkprevcheckout\` enum('yes', 'no', 'inherit') NOT NULL DEFAULT 'inherit' COMMENT 'produce a warning for this patron category if this item has previously been checked out to this patron if ''yes'', not if ''no'', defer to syspref setting if ''inherit''.'; COMMIT;

-- Transaction for deletedborrowers table BEGIN; UPDATE deletedborrowers SET checkprevcheckout = 'inherit' WHERE checkprevcheckout NOT IN ('yes','no','inherit');

ALTER TABLE deletedborrowers MODIFY COLUMN \`checkprevcheckout\` enum('yes', 'no', 'inherit') NOT NULL DEFAULT 'inherit' COMMENT 'produce a warning for this patron if this item has previously been checked out to this patron if ''yes'', not if ''no'', defer to category setting if ''inherit''.'; COMMIT;

To get a database shell, you can use koha-mysql <YOUR_INSTANCE_NAME>.

5. After that, the bug should be fixed. If not, leave a comment.

Hi @Paul Derscheid. Is it possible to make this manual fix in version 25.05.02.000? I am looking out every day for version v25.05.02-2, but it has not become available for Ubuntu so far. I would like to try your fix, but I am not sure if this might cause damage if I am not using the right version. Thank you Isabel Pineda. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 --- Comment #13 from Isabel Pineda <isabel.pineda@ds.edu.sv> --- (In reply to Paul Derscheid from comment #12)

@Isabel Pineda, were you able to resolve the issue manually in the meantime?

Hi @Paul Derscheid. Yes, last week I could update to version 25.05.03, then I ran the SQL commands manually and it seems to work. Thank you. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 Paul Derscheid <paul.derscheid@lmscloud.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40528 Paul Derscheid <paul.derscheid@lmscloud.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|Needs Signoff |RESOLVED --- Comment #16 from Paul Derscheid <paul.derscheid@lmscloud.de> --- We think that it's probably not necessary to include another db_rev to fix this since the affected instances are probably aware of this bug. For reference, see this discussion: https://chat.koha-community.org/koha-community/pl/xkoquq3ombgk9ec51x34sgw5pa -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.