Bug 15433 - Self checkout software error on checkout
Summary: Self checkout software error on checkout
Status: RESOLVED DUPLICATE of bug 15429
Alias: None
Product: Koha
Classification: Unclassified
Component: Self checkout (show other bugs)
Version: Main
Hardware: All All
: P1 - high critical
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-29 04:26 UTC by Derryn
Modified: 2015-12-30 11:38 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Derryn 2015-12-29 04:26:16 UTC 
Upon upgrading from 3.20 to 3.22 we've noticed our Self checkout computer displays the following software error when checking out an item:

"The given date (01/01/2020 00:00) does not match the date format (sql) at /usr/share/koha/lib/Koha/DateUtils.pm line 153."

The date, I discovered, is actually the patron's account expiry. Thinking it's something to do with the date format, I tried changing the dateformat syspref to mm/dd/yyyy (we normally use dd/mm/yyyy) but that didn't help.
I've also observed that it actually does check the item out. The staff client has no problems checking in/out.
 
I've had to revert back to 3.20 so unfortunately I don't have the ability to test this anymore. I am happy to provide details of our installation if necessary though.
Comment 1 Katrin Fischer 2015-12-29 22:43:46 UTC 
Hi Derryn, this sounds somewhat similar to a behaviour in batch checkout that is resolved by bug 15429 - could you check if this also fixes your problem?
Comment 2 Derryn 2015-12-30 08:04:11 UTC 
You are correct, that patch fixed it! Thanks.
Comment 3 Katrin Fischer 2015-12-30 08:18:15 UTC 

*** This bug has been marked as a duplicate of bug 15429 ***
Comment 4 Jonathan Druart 2015-12-30 11:38:41 UTC 
(In reply to Derryn from comment #2)
> You are correct, that patch fixed it! Thanks.

Could you signoff the patch please?