Bug 23555 - checkouts are not getting updated when using SIP
Summary: checkouts are not getting updated when using SIP
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: 19.05
Hardware: All All
: P5 - low critical (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-06 09:25 UTC by ithelpdesk@edutech.com
Modified: 2020-06-04 20:32 UTC (History)
3 users (show)

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


Attachments
issue in checkout update (326.54 KB, image/jpeg)
2019-09-06 09:25 UTC, ithelpdesk@edutech.com
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ithelpdesk@edutech.com 2019-09-06 09:25:21 UTC
Created attachment 92617 [details]
issue in checkout update

hi,

when checkout items using SIP2, the same is not getting updated in to patron's account. it is just showing loading and not load at all. please find the attached screenshot and help me resolving this issue

i have tried updating system status to 'YES" in SIP config file and also tried the below steps also but negative result.

 Access your Koha server with shell.

- Locate the file 'checkouts' in your local Koha installation. It is in 'svc'
   subdirectory of the Koha home directory.
- Change your working directory to the directory containing 'checkouts'.
- Run this command:
   wget -O checkouts http://tinyurl.com/zg6ukte

   It retrieves a valid 'checkouts' program.


Nidheesh Madhavan
Comment 1 Katrin Fischer 2019-09-08 20:06:47 UTC
Hi,

this sounds more like a support request than a bug report - please check your item data an the data in the issues table. This is most likely due to some invalid data inserted via SIP2 (check home and holding branches have correct values etc.). You might also see a JavaScript/XHR request error in the browser for your not-loading checkouts table.

Please ask further questions on the mailing list if this doesn't help resolve the issue.