Hi, Thanks, but I'm perplexed. Even the latest &AddRenewal in Circulation.pm looks the same. At our end, yes, about 10% renewals have a different lastreneweddate than midnight, but even then it does not match the timestamp, while the returndate is exactly matching the timestamp. Why is there that ymd() in &AddRenewal? Ramprasad Joshi CS-IS Dept BITS, Pilani - K K Birla Goa Campus Zuarinagar, GOA INDIA 403726 Phone +91 832 2580 121 Fax +91 832 2557033 On 6 September 2014 00:24, Indranil Das Gupta <indradg@gmail.com> wrote:
Hi,
On Fri, Sep 5, 2014 at 11:37 AM, Ramprasad S. Joshi <rsj@goa.bits-pilani.ac.in> wrote:
We (at BITS, Pilani - Goa Campus, Goa INDIA) have a problem of reporting renewal date-times on koha 3.14.08.000. I suppose it is there with newer versions as well.
I tested on 3.14.09 instance, by renewing an issued (and overdue) item. I didn't encounter the error you mention. A screenshot for your reference http://pandora.burntomlette.in/screenshots/koha/3.14.09/koha-bits-goa1.jpg
cheers -indra
-- Indranil Das Gupta
Phone : +91-98300-20971 Blog : http://indradg.randomink.org/blog IRC : indradg on irc://irc.freenode.net Twitter : indradg
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=- Please exchange editable Office documents only in ODF Format. No other format is acceptable. Support Open Standards.
For a free editor supporting ODF, please visit LibreOffice - http://www.documentfoundation.org