Thanks for the help, I checked the database and there was a ceilingDueDate and a GlobalDueDate set in the systempreferences table. I deleted those rows from the database and verified that they're gone. We only have one circulation rule defined so I also deleted it and recreated it. The circulation rule does not have a hard due date defined and simply specifies a 21 day loan period. Unfortunately, we're still experiencing the same problem. When books are checked out, they're still assigned a due date of 5/17/2012. Any other suggestions? I verified that the server's system date is correct. Eric On Fri, Jun 1, 2012 at 12:35 PM, Chris Cormack <chrisc@catalyst.net.nz> wrote:
Ian Walls <koha.sekjal@gmail.com> wrote:
ceilingDueDate and globalDueDate shouldn't be in your 3.8 system; they were deleted as part of the database update that moved them to the circulation matrix (issuingrules table).
Yep but if for whatever reason this didn't run or failed the code still refers to at least one of them. That's a legit bug we need to tidy up.
Chris
You should be able to re-enter your rules in the Circulation and Fines rules area under the Administration. You'll have to do this for all your rules, which could be a pain. What might be easier is:
UPDATE issuingrules SET hardduedate = 'XXXX-YY-ZZ' WHERE hardduedate = '2012-05-17';
Where 'XXXX-YY-ZZ' is the new global due date you want to set for all materials. If you want finer grain control (only applying a global due date for certain item types, patrons or branches), you'll need to either use the Circulation and Fines editor in Admin, or add a series of additional WHERE clauses to the query.
Hope this helps,
-Ian
On Thu, May 31, 2012 at 5:14 PM, Chris Cormack <chrisc@catalyst.net.nz>wrote:
* jrhsigler (jrhsigler@gmail.com) wrote:
Thanks, I looked in 'local use' but didn't see any options for changing global due dates. I'm at Koha 3.8 now, but set the global due date when I had 3.4 running.
Do you have a sample sql statement that I can use to update the database directly?
Thank you!
Hi,
Sorry about the slow reply, timezones are a pain.
Ok the variable is called ceilingDueDate
So
DELETE FROM systempreferences WHERE variable ='ceilingDueDate';
Will kill that line completely.
There is also globalDueDate
DELETE FROM systempreferences WHERE variable ='globalDueDate';
To get rid of it
However if you wanted to file a bug also, because there must be code still referencing the old dead syspref, that we need to purge.
So bonus points if you go to bugs.koha-community.org and add a bug something like "Vestiges of code still refer to deprecated syspref globalDueDate"
Its in C4/Circulation.pm that the bad code is so you could at that, and then someone can write a patch to clean it up, extra super mega bonus points if you write the patch too :)
Chris
-- View this message in context:
http://koha.1045719.n5.nabble.com/how-to-undo-global-due-date-tp5714544p5714...
Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha